Re: Plone-docs Digest, Vol 31, Issue 22

3 messages Options
Embed this post
Permalink
Sam Knox () Re: Plone-docs Digest, Vol 31, Issue 22
Reply Threaded More More options
Print post
Permalink
Steve McMahon wrote:

" Also, for any how-to / tutorial content moving to manuals, we need to
contact the principal authors to make sure they're going to be
amenable to signing something similar to the Plone committer's
agreement and dedicating their work to the Plone Foundation."

Is there any language available for us to use in such an email? I want
to be sure that I'm framing messages in the correct way. Do you think
it's enough to simply link to the Plone Contributor Agreement?

Also - When we've identified how-tos / tutorials that need to be merged
into Manuals, how should we record that information. Open Plans? Email
you?

Thanks!

Sam Knox |  Support Manager
ONE/Northwest

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]]
Sent: Wednesday, December 31, 2008 8:56 AM
To: [hidden email]
Subject: Plone-docs Digest, Vol 31, Issue 22

Send Plone-docs mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/plone-docs
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Plone-docs digest..."


Today's Topics:

   1. Re: Documentation rating / feedback (Jon Stahl)
   2. Re: Needed: upgrade instructions for Plone 3.2 (Steve McMahon)
   3. Re: Updating plone.org/help (Graham Perrin)
   4. Re: [Plone.org] #664: Plone Documentation lacks a link to
      tutorials (Plone.org)
   5. plone.org has been upgraded! - next steps ( Israel Saeta P?rez )
   6. Re: plone.org has been upgraded! - next steps (Steve McMahon)


----------------------------------------------------------------------

Message: 1
Date: Fri, 26 Dec 2008 16:38:22 -0500
From: Jon Stahl <[hidden email]>
Subject: Re: [Plone-docs] Documentation rating / feedback
To: Ricardo Newbery <[hidden email]>
Cc: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Ricardo Newbery wrote:

> On Dec 10, 2008, at 2:33 PM, Alexander Limi wrote:
>
>  
>> On Tue, 09 Dec 2008 14:09:31 -0800, Israel Saeta P?rez
>> <[hidden email]> wrote:
>>
>>    
>>> I guess you mean Content Ratings
>>> <http://plone.org/products/contentratings>.
>>> "This package's default configuration provides two rating  
>>> categories. One
>>> for user ratings, and one for editorial ratings." Looks  
>>> promising. :-)
>>>      
>> It's what we will be using for PloneSoftwareCenter, so it's in some  
>> ways
>> becoming the standard rating mechanism. If you want to look into  
>> ratings,
>> that would be the best product to investigate. :)
>>
>> --
>> Alexander Limi ? http://limi.net
>>    
>
>
>
> Maybe off-topic but I wish the PSC had a community promotion feature  
> like Amazon's Listmania lists.  That would be so cool.  :-)
>  

That would be cool indeed... sort of like ohloh's "stacks" feature where

you can list what products you use.

You could probably whip this up as a standalone product (hint hint). :-)

:jon



------------------------------

Message: 2
Date: Fri, 26 Dec 2008 21:18:51 -0800
From: "Steve McMahon" <[hidden email]>
Subject: Re: [Plone-docs] Needed: upgrade instructions for Plone 3.2
To: "David Glick" <[hidden email]>
Cc: [hidden email]
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1

Already fixed! Thanks for the careful reading.

Steve

On Fri, Dec 26, 2008 at 10:14 AM, David Glick <[hidden email]>
wrote:

> The sample buildout has the line:
> extends = http://dist.plone.org/release/3.versions.cfg
>
> but that file doesn't exist...
>
> I think it should be http://dist.plone.org/release/3.2/versions.cfg
>
> David
>
> On Dec 26, 2008, at 1:06 PM, Steve McMahon wrote:
>
>> I've added some background/explanatory text, and expanded some
>> warnings. I'd appreciate it if one of you would check/edit my prose.
>> After that, I think it's ready to go live.
>>
>> Steve
>>
>> On Fri, Dec 26, 2008 at 8:26 AM, Israel Saeta P?rez
<[hidden email]>
>> wrote:
>>>
>>> On Thu, Dec 25, 2008 at 3:52 PM, Israel Saeta P?rez
<[hidden email]>
>>> wrote:
>>>>
>>>> On Thu, Dec 25, 2008 at 3:06 PM, JoAnna Springsteen wrote:
>>>>>
>>>>> Israel and I are looking at it right now. We'll definitely have
>>>>> something for you this weekend.
>>>>
>>>> I'm not sure if these instructions should belong to the migration
manual
>>>> and/or some other installation docs, but I've started this based on
a
>>>> Wichert's post to the plone-announcement list.
>>>
>>> Matthew has reviewed and updated that doc. SteveM, Wichert, is it ok
and
>>> clear enough?
>>>
>>> Thanks.
>>>
>>>
>>>
------------------------------------------------------------------------
------

>>>
>>> _______________________________________________
>>> Plone-docs mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>>>
>>>
>>
>>
>>
>> --
>>
>> Steve McMahon
>> Reid-McMahon, LLC
>> [hidden email]
>> [hidden email]
>>
>>
>>
------------------------------------------------------------------------
------

>> _______________________________________________
>> Plone-docs mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>
> David Glick
> Web Developer
> ONE/Northwest
>
> New tools and strategies for engaging people in protecting the
environment

>
> http://www.onenw.org
> [hidden email]
> work: (206) 286-1235 x32
> mobile: (206) 679-3833
>
> Subscribe to ONEList, our email newsletter!
> Practical advice for effective online engagement
> http://www.onenw.org/full_signup
>
>
>
>
>



--

Steve McMahon
Reid-McMahon, LLC
[hidden email]
[hidden email]



------------------------------

Message: 3
Date: Tue, 30 Dec 2008 20:47:12 -0800 (PST)
From: Graham Perrin <[hidden email]>
Subject: Re: [Plone-docs] Updating plone.org/help
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=UTF-8



Christian Schneider-10 wrote:
>
> I agree totally, the quirkiness is inappropriate...
>

Coinciding with plone.org upgrade, a round of minor updates to various
objects allowed me a little time to work on
<http://plone.org/documentation/how-to/ask-for-help>. Work in progress,
not
finalised (naturally interrupted during upgrade routines), the page
remains
quirky and broadly speaking it:

* still assumes that the user is suffering problems and frustration
(negative)

* may not recognise that some writers are simply newcomers, seeking
advice/direction (positive).

I know that <http://plone.org/documentation/how-to/asking-for-help>
exists,
I'll do a little more tidying of my work in progress then compare the
two.
An early thought is that we might have:

* one how-to: 'Asking for help'
* another how-to, closely associated, equally visible: 'Dealing with
problems and errors' ??words along those lines.

Regards
Graham
--
View this message in context:
http://n2.nabble.com/Updating-plone.org-help-tp359729p2095051.html
Sent from the Documentation Team mailing list archive at Nabble.com.




------------------------------

Message: 4
Date: Wed, 31 Dec 2008 05:06:33 -0000
From: "Plone.org" <[hidden email]>
Subject: Re: [Plone-docs] [Plone.org] #664: Plone Documentation lacks
        a link to tutorials
Cc: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

#664: Plone Documentation lacks a link to tutorials
---------------------------------+--------------------------------------
----
  Reporter:  grahamperrin        |       Owner:
[hidden email]
      Type:  feature suggestion  |      Status:  new

  Priority:  minor               |   Component:  documentation

Resolution:                      |    Keywords:

---------------------------------+--------------------------------------
----
Changes (by jonstahl):

  * owner:  [hidden email] => plone-
            [hidden email]
  * priority:  major => minor
  * component:  website => documentation
  * type:  bug => feature suggestion

Comment:

 In general, we are moving away from classifying things by "type"
towards
 classifying by topic.

 Also, note that this is really a documentation team issue.

--
Ticket URL: <https://dev.plone.org/plone.org/ticket/664#comment:2>
Plone.org <http://plone.org>
Plone.org services maintenance

------------------------------

Message: 5
Date: Wed, 31 Dec 2008 17:37:38 +0100
From: " Israel Saeta P?rez " <[hidden email]>
Subject: [Plone-docs] plone.org has been upgraded! - next steps
To: "Plone Docs List" <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="iso-8859-1"

Now that plone.org has been upgraded I think we should decide how will
we
manage some stuff:

   1. Migration to official docs & knowledge base.
   2. Getting rid of classification by content-type in favour of
   classification by topic.
   3. Merging official docs contents into a bunch of manuals, by topic.
   4. Alert to the editors mailing list when a new document arrives to
the
   review queue.
   5. Managing PLIP's changes reflection into documentation.
   6. ...

Veda, Steve, I guess you can give us an update on that, right?

-- israel
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 6
Date: Wed, 31 Dec 2008 08:55:23 -0800
From: "Steve McMahon" <[hidden email]>
Subject: Re: [Plone-docs] plone.org has been upgraded! - next steps
To: " Israel Saeta P?rez " <[hidden email]>
Cc: Plone Docs List <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1

> Veda, Steve, I guess you can give us an update on that, right?

The technical parts of this reorganization are my project for the
week. Limi's working on templates.

IMHO, the most critical thing the doc team / editors can be doing
right now is identifying any existing content in the how-to / tutorial
sections that needs to move into manuals. I can script those moves,
but will need ids for the sources and targets.

Also, for any how-to / tutorial content moving to manuals, we need to
contact the principal authors to make sure they're going to be
amenable to signing something similar to the Plone committer's
agreement and dedicating their work to the Plone Foundation.

Steve

On Wed, Dec 31, 2008 at 8:37 AM, Israel Saeta P?rez <[hidden email]>
wrote:
> Now that plone.org has been upgraded I think we should decide how will
we
> manage some stuff:
>
> Migration to official docs & knowledge base.
> Getting rid of classification by content-type in favour of
classification by
> topic.
> Merging official docs contents into a bunch of manuals, by topic.
> Alert to the editors mailing list when a new document arrives to the
review

> queue.
> Managing PLIP's changes reflection into documentation.
> ...
>
> Veda, Steve, I guess you can give us an update on that, right?
>
> -- israel
>
>
>
------------------------------------------------------------------------
------
>
> _______________________________________________
> Plone-docs mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>
>



--

Steve McMahon
Reid-McMahon, LLC
[hidden email]
[hidden email]



------------------------------

------------------------------------------------------------------------
------


------------------------------

_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs


End of Plone-docs Digest, Vol 31, Issue 22
******************************************

------------------------------------------------------------------------------
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs
Steve McMahon () Re: Plone-docs Digest, Vol 31, Issue 22
Reply Threaded More More options
Print post
Permalink
> Also - When we've identified how-tos / tutorials that need to be merged
> into Manuals, how should we record that information. Open Plans? Email
> you?

OpenPlans would be great, though I'll also try to keep track of any
e-mail on the editor's list.

Thanks! Steve

On Wed, Dec 31, 2008 at 9:14 AM, Sam Knox <[hidden email]> wrote:

> Steve McMahon wrote:
>
> " Also, for any how-to / tutorial content moving to manuals, we need to
> contact the principal authors to make sure they're going to be
> amenable to signing something similar to the Plone committer's
> agreement and dedicating their work to the Plone Foundation."
>
> Is there any language available for us to use in such an email? I want
> to be sure that I'm framing messages in the correct way. Do you think
> it's enough to simply link to the Plone Contributor Agreement?
>
> Also - When we've identified how-tos / tutorials that need to be merged
> into Manuals, how should we record that information. Open Plans? Email
> you?
>
> Thanks!
>
> Sam Knox |  Support Manager
> ONE/Northwest
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]]
> Sent: Wednesday, December 31, 2008 8:56 AM
> To: [hidden email]
> Subject: Plone-docs Digest, Vol 31, Issue 22
>
> Send Plone-docs mailing list submissions to
>        [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/plone-docs
> or, via email, send a message with subject or body 'help' to
>        [hidden email]
>
> You can reach the person managing the list at
>        [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Plone-docs digest..."
>
>
> Today's Topics:
>
>   1. Re: Documentation rating / feedback (Jon Stahl)
>   2. Re: Needed: upgrade instructions for Plone 3.2 (Steve McMahon)
>   3. Re: Updating plone.org/help (Graham Perrin)
>   4. Re: [Plone.org] #664: Plone Documentation lacks a link    to
>      tutorials (Plone.org)
>   5. plone.org has been upgraded! - next steps ( Israel Saeta P?rez )
>   6. Re: plone.org has been upgraded! - next steps (Steve McMahon)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Dec 2008 16:38:22 -0500
> From: Jon Stahl <[hidden email]>
> Subject: Re: [Plone-docs] Documentation rating / feedback
> To: Ricardo Newbery <[hidden email]>
> Cc: [hidden email]
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Ricardo Newbery wrote:
>> On Dec 10, 2008, at 2:33 PM, Alexander Limi wrote:
>>
>>
>>> On Tue, 09 Dec 2008 14:09:31 -0800, Israel Saeta P?rez
>>> <[hidden email]> wrote:
>>>
>>>
>>>> I guess you mean Content Ratings
>>>> <http://plone.org/products/contentratings>.
>>>> "This package's default configuration provides two rating
>>>> categories. One
>>>> for user ratings, and one for editorial ratings." Looks
>>>> promising. :-)
>>>>
>>> It's what we will be using for PloneSoftwareCenter, so it's in some
>>> ways
>>> becoming the standard rating mechanism. If you want to look into
>>> ratings,
>>> that would be the best product to investigate. :)
>>>
>>> --
>>> Alexander Limi ? http://limi.net
>>>
>>
>>
>>
>> Maybe off-topic but I wish the PSC had a community promotion feature
>> like Amazon's Listmania lists.  That would be so cool.  :-)
>>
>
> That would be cool indeed... sort of like ohloh's "stacks" feature where
>
> you can list what products you use.
>
> You could probably whip this up as a standalone product (hint hint). :-)
>
> :jon
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 26 Dec 2008 21:18:51 -0800
> From: "Steve McMahon" <[hidden email]>
> Subject: Re: [Plone-docs] Needed: upgrade instructions for Plone 3.2
> To: "David Glick" <[hidden email]>
> Cc: [hidden email]
> Message-ID:
>        <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Already fixed! Thanks for the careful reading.
>
> Steve
>
> On Fri, Dec 26, 2008 at 10:14 AM, David Glick <[hidden email]>
> wrote:
>> The sample buildout has the line:
>> extends = http://dist.plone.org/release/3.versions.cfg
>>
>> but that file doesn't exist...
>>
>> I think it should be http://dist.plone.org/release/3.2/versions.cfg
>>
>> David
>>
>> On Dec 26, 2008, at 1:06 PM, Steve McMahon wrote:
>>
>>> I've added some background/explanatory text, and expanded some
>>> warnings. I'd appreciate it if one of you would check/edit my prose.
>>> After that, I think it's ready to go live.
>>>
>>> Steve
>>>
>>> On Fri, Dec 26, 2008 at 8:26 AM, Israel Saeta P?rez
> <[hidden email]>
>>> wrote:
>>>>
>>>> On Thu, Dec 25, 2008 at 3:52 PM, Israel Saeta P?rez
> <[hidden email]>
>>>> wrote:
>>>>>
>>>>> On Thu, Dec 25, 2008 at 3:06 PM, JoAnna Springsteen wrote:
>>>>>>
>>>>>> Israel and I are looking at it right now. We'll definitely have
>>>>>> something for you this weekend.
>>>>>
>>>>> I'm not sure if these instructions should belong to the migration
> manual
>>>>> and/or some other installation docs, but I've started this based on
> a
>>>>> Wichert's post to the plone-announcement list.
>>>>
>>>> Matthew has reviewed and updated that doc. SteveM, Wichert, is it ok
> and
>>>> clear enough?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
> ------------------------------------------------------------------------
> ------
>>>>
>>>> _______________________________________________
>>>> Plone-docs mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Steve McMahon
>>> Reid-McMahon, LLC
>>> [hidden email]
>>> [hidden email]
>>>
>>>
>>>
> ------------------------------------------------------------------------
> ------
>>> _______________________________________________
>>> Plone-docs mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>>
>> David Glick
>> Web Developer
>> ONE/Northwest
>>
>> New tools and strategies for engaging people in protecting the
> environment
>>
>> http://www.onenw.org
>> [hidden email]
>> work: (206) 286-1235 x32
>> mobile: (206) 679-3833
>>
>> Subscribe to ONEList, our email newsletter!
>> Practical advice for effective online engagement
>> http://www.onenw.org/full_signup
>>
>>
>>
>>
>>
>
>
>
> --
>
> Steve McMahon
> Reid-McMahon, LLC
> [hidden email]
> [hidden email]
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 30 Dec 2008 20:47:12 -0800 (PST)
> From: Graham Perrin <[hidden email]>
> Subject: Re: [Plone-docs] Updating plone.org/help
> To: [hidden email]
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=UTF-8
>
>
>
> Christian Schneider-10 wrote:
>>
>> I agree totally, the quirkiness is inappropriate...
>>
>
> Coinciding with plone.org upgrade, a round of minor updates to various
> objects allowed me a little time to work on
> <http://plone.org/documentation/how-to/ask-for-help>. Work in progress,
> not
> finalised (naturally interrupted during upgrade routines), the page
> remains
> quirky and broadly speaking it:
>
> * still assumes that the user is suffering problems and frustration
> (negative)
>
> * may not recognise that some writers are simply newcomers, seeking
> advice/direction (positive).
>
> I know that <http://plone.org/documentation/how-to/asking-for-help>
> exists,
> I'll do a little more tidying of my work in progress then compare the
> two.
> An early thought is that we might have:
>
> * one how-to: 'Asking for help'
> * another how-to, closely associated, equally visible: 'Dealing with
> problems and errors' ??words along those lines.
>
> Regards
> Graham
> --
> View this message in context:
> http://n2.nabble.com/Updating-plone.org-help-tp359729p2095051.html
> Sent from the Documentation Team mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 31 Dec 2008 05:06:33 -0000
> From: "Plone.org" <[hidden email]>
> Subject: Re: [Plone-docs] [Plone.org] #664: Plone Documentation lacks
>        a link  to tutorials
> Cc: [hidden email]
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> #664: Plone Documentation lacks a link to tutorials
> ---------------------------------+--------------------------------------
> ----
>  Reporter:  grahamperrin        |       Owner:
> [hidden email]
>      Type:  feature suggestion  |      Status:  new
>
>  Priority:  minor               |   Component:  documentation
>
> Resolution:                      |    Keywords:
>
> ---------------------------------+--------------------------------------
> ----
> Changes (by jonstahl):
>
>  * owner:  [hidden email] => plone-
>            [hidden email]
>  * priority:  major => minor
>  * component:  website => documentation
>  * type:  bug => feature suggestion
>
> Comment:
>
>  In general, we are moving away from classifying things by "type"
> towards
>  classifying by topic.
>
>  Also, note that this is really a documentation team issue.
>
> --
> Ticket URL: <https://dev.plone.org/plone.org/ticket/664#comment:2>
> Plone.org <http://plone.org>
> Plone.org services maintenance
>
> ------------------------------
>
> Message: 5
> Date: Wed, 31 Dec 2008 17:37:38 +0100
> From: " Israel Saeta P?rez " <[hidden email]>
> Subject: [Plone-docs] plone.org has been upgraded! - next steps
> To: "Plone Docs List" <[hidden email]>
> Message-ID:
>        <[hidden email]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Now that plone.org has been upgraded I think we should decide how will
> we
> manage some stuff:
>
>   1. Migration to official docs & knowledge base.
>   2. Getting rid of classification by content-type in favour of
>   classification by topic.
>   3. Merging official docs contents into a bunch of manuals, by topic.
>   4. Alert to the editors mailing list when a new document arrives to
> the
>   review queue.
>   5. Managing PLIP's changes reflection into documentation.
>   6. ...
>
> Veda, Steve, I guess you can give us an update on that, right?
>
> -- israel
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 6
> Date: Wed, 31 Dec 2008 08:55:23 -0800
> From: "Steve McMahon" <[hidden email]>
> Subject: Re: [Plone-docs] plone.org has been upgraded! - next steps
> To: " Israel Saeta P?rez " <[hidden email]>
> Cc: Plone Docs List <[hidden email]>
> Message-ID:
>        <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
>> Veda, Steve, I guess you can give us an update on that, right?
>
> The technical parts of this reorganization are my project for the
> week. Limi's working on templates.
>
> IMHO, the most critical thing the doc team / editors can be doing
> right now is identifying any existing content in the how-to / tutorial
> sections that needs to move into manuals. I can script those moves,
> but will need ids for the sources and targets.
>
> Also, for any how-to / tutorial content moving to manuals, we need to
> contact the principal authors to make sure they're going to be
> amenable to signing something similar to the Plone committer's
> agreement and dedicating their work to the Plone Foundation.
>
> Steve
>
> On Wed, Dec 31, 2008 at 8:37 AM, Israel Saeta P?rez <[hidden email]>
> wrote:
>> Now that plone.org has been upgraded I think we should decide how will
> we
>> manage some stuff:
>>
>> Migration to official docs & knowledge base.
>> Getting rid of classification by content-type in favour of
> classification by
>> topic.
>> Merging official docs contents into a bunch of manuals, by topic.
>> Alert to the editors mailing list when a new document arrives to the
> review
>> queue.
>> Managing PLIP's changes reflection into documentation.
>> ...
>>
>> Veda, Steve, I guess you can give us an update on that, right?
>>
>> -- israel
>>
>>
>>
> ------------------------------------------------------------------------
> ------
>>
>> _______________________________________________
>> Plone-docs mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>>
>>
>
>
>
> --
>
> Steve McMahon
> Reid-McMahon, LLC
> [hidden email]
> [hidden email]
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------
> ------
>
>
> ------------------------------
>
> _______________________________________________
> Plone-docs mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>
>
> End of Plone-docs Digest, Vol 31, Issue 22
> ******************************************
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-docs mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>



--

Steve McMahon
Reid-McMahon, LLC
[hidden email]
[hidden email]

------------------------------------------------------------------------------
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs
JoAnna Springsteen () Re: Plone-docs Digest, Vol 31, Issue 22
Reply Threaded More More options
Print post
Permalink
In reply to this post by Sam Knox
> Also - When we've identified how-tos / tutorials that need to be merged
> into Manuals, how should we record that information. Open Plans? Email
> you?

Open Plans- Add a column to the assessment to indicate where it is being moved.

Email the list before merging anything. We need to keep track of this stuff!

------------------------------------------------------------------------------
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs