Plone › Documentation Team

plone.org has been upgraded! - next steps

12 messages

Israel Saeta Pérez () plone.org has been upgraded! - next steps

Reply Threaded

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

Israel Saeta Pérez

Steve McMahon () Re: plone.org has been upgraded! - next steps

Reply Threaded

> 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

vedaw () Re: plone.org has been upgraded! - next steps

Reply Threaded

Steve, let me know what you need from me. My notes from the Seattle
migration discussion, with thoughts on scripts that might be needed are
here:

http://www.openplans.org/projects/plone-documentation/here/

I'd also like to state that for sections that are behind in their
assessments, we should at least do a quick pass thru them to find out which
ones can be dumped out to the knowledgebase area. The deeper assessment can
probably happen separately from this.

Joanna, how are we on the areas that are straggling? Do we have people
assigned to do the work? If not, can we identify specific people we can pull
in? Maybe Joel?

Thanks,

- Veda

On 12/31/08 8:55 AM, "Steve McMahon" <[hidden email]> wrote:

>> 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
>>
>>
>
>

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

JoAnna Springsteen () Re: plone.org has been upgraded! - next steps

Reply Threaded

> Joanna, how are we on the areas that are straggling? Do we have people
> assigned to do the work? If not, can we identify specific people we can pull
> in? Maybe Joel?

As of right now we only have one assessment that isn't done and it is
being worked on. So we are ok! Gustavo stepped in this week and did a
ton of work. We owe him a huge thanks. (we've also extended him an
invitation to become and editor)

We will need to review some of these assessments and see which ones
will go into manuals and which will be kb materials but that will be
made easier with the assessments done.

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

Steve McMahon () Re: plone.org has been upgraded! - next steps

Reply Threaded

In reply to this post by vedaw

Just to clarify, my intention is to script the movement of
*everything* in how-to and tutorial to the knowledgebase, *except*:

1) Documents that are not published or have no sections specified.

2) Content identified for inclusion in an already-existing manual.
That will be turned into a manual section.

I may see if we can repurpose new.plone.org (now that the Plone 3
switch is done) to test and check the scripted part of the
reorganization.

Steve

On Wed, Dec 31, 2008 at 1:06 PM, Veda Williams <[hidden email]> wrote:

> Steve, let me know what you need from me. My notes from the Seattle
> migration discussion, with thoughts on scripts that might be needed are
> here:
>
> http://www.openplans.org/projects/plone-documentation/here/
>
> I'd also like to state that for sections that are behind in their
> assessments, we should at least do a quick pass thru them to find out which
> ones can be dumped out to the knowledgebase area. The deeper assessment can
> probably happen separately from this.
>
> Joanna, how are we on the areas that are straggling? Do we have people
> assigned to do the work? If not, can we identify specific people we can pull
> in? Maybe Joel?
>
> Thanks,
>
> - Veda
>
>
> On 12/31/08 8:55 AM, "Steve McMahon" <[hidden email]> wrote:
>
>>> 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
>>>
>>>
>>
>>
>
>

vedaw () Re: plone.org has been upgraded! - next steps

Reply Threaded

You're going to sniff out docs that have more than one section specified so
that we can deselect sections that aren't relevant, right?

On 12/31/08 2:01 PM, "Steve McMahon" <[hidden email]> wrote:

> Just to clarify, my intention is to script the movement of
> *everything* in how-to and tutorial to the knowledgebase, *except*:
>
> 1) Documents that are not published or have no sections specified.
>
> 2) Content identified for inclusion in an already-existing manual.
> That will be turned into a manual section.
>
> I may see if we can repurpose new.plone.org (now that the Plone 3
> switch is done) to test and check the scripted part of the
> reorganization.
>
> Steve
>
>
> On Wed, Dec 31, 2008 at 1:06 PM, Veda Williams <[hidden email]> wrote:
>> Steve, let me know what you need from me. My notes from the Seattle
>> migration discussion, with thoughts on scripts that might be needed are
>> here:
>>
>> http://www.openplans.org/projects/plone-documentation/here/
>>
>> I'd also like to state that for sections that are behind in their
>> assessments, we should at least do a quick pass thru them to find out which
>> ones can be dumped out to the knowledgebase area. The deeper assessment can
>> probably happen separately from this.
>>
>> Joanna, how are we on the areas that are straggling? Do we have people
>> assigned to do the work? If not, can we identify specific people we can pull
>> in? Maybe Joel?
>>
>> Thanks,
>>
>> - Veda
>>
>>
>> On 12/31/08 8:55 AM, "Steve McMahon" <[hidden email]> wrote:
>>
>>>> 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>

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

Israel Saeta Pérez () Re: plone.org has been upgraded! - next steps

Reply Threaded

In reply to this post by Steve McMahon

On Wed, Dec 31, 2008 at 11:01 PM, Steve McMahon wrote:

Just to clarify, my intention is to script the movement of
*everything* in how-to and tutorial to the knowledgebase, *except*:

1) Documents that are not published or have no sections specified.

2) Content identified for inclusion in an already-existing manual.
That will be turned into a manual section.

I may see if we can repurpose new.plone.org (now that the Plone 3
switch is done) to test and check the scripted part of the
reorganization.

In the case of the development section, there are a lot of documents which could be merged with existing manuals or serve as a base for new ones, but they need integration work and can't become part of a manual without adapting them.

Does that mean these documents will go to the knowledgebase first and we will pick and integrate them in manuals later?

-- israel

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

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

Israel Saeta Pérez

Steve McMahon () Re: plone.org has been upgraded! - next steps

Reply Threaded

> Does that mean these documents will go to the knowledgebase first and we
> will pick and integrate them in manuals later?

What if the script *copies* (rather than *moving*) the contents of
identified how-tos into manual sections, setting the destination "in
progress"?

Then, the how-to can be removed after manual integration. We'll need
to make sure to set a redirect from the source to the destination upon
the completed integration.

On Thu, Jan 1, 2009 at 12:06 PM, Israel Saeta Pérez <[hidden email]> wrote:

> On Wed, Dec 31, 2008 at 11:01 PM, Steve McMahon wrote:
>>
>> Just to clarify, my intention is to script the movement of
>> *everything* in how-to and tutorial to the knowledgebase, *except*:
>>
>> 1) Documents that are not published or have no sections specified.
>>
>> 2) Content identified for inclusion in an already-existing manual.
>> That will be turned into a manual section.
>>
>> I may see if we can repurpose new.plone.org (now that the Plone 3
>> switch is done) to test and check the scripted part of the
>> reorganization.
>
> In the case of the development section, there are a lot of documents which
> could be merged with existing manuals or serve as a base for new ones, but
> they need integration work and can't become part of a manual without
> adapting them.
>
> Does that mean these documents will go to the knowledgebase first and we
> will pick and integrate them in manuals later?
>
> -- israel

Alexander Limi () Re: plone.org has been upgraded! - next steps

Reply Threaded

On Thu, 01 Jan 2009 13:10:19 -0800, Steve McMahon
<[hidden email]> wrote:

> What if the script *copies* (rather than *moving*) the contents of
> identified how-tos into manual sections, setting the destination "in
> progress"?

I think this is a great idea.

> Then, the how-to can be removed after manual integration. We'll need
> to make sure to set a redirect from the source to the destination upon
> the completed integration.

Sounds like a good way to move forward.

--
Alexander Limi · http://limi.net

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

Alexander Limi · http://limi.net

Israel Saeta Pérez () Re: plone.org has been upgraded! - next steps

Reply Threaded

On Fri, Jan 2, 2009 at 3:22 AM, Alexander Limi wrote:

On Thu, 01 Jan 2009 13:10:19 -0800, Steve McMahon
<[hidden email]> wrote:

> What if the script *copies* (rather than *moving*) the contents of
> identified how-tos into manual sections, setting the destination "in
> progress"?

I think this is a great idea.

> Then, the how-to can be removed after manual integration. We'll need
> to make sure to set a redirect from the source to the destination upon
> the completed integration.

Sounds like a good way to move forward.

I'm ok with that process too. I guess "in progress" means invisible to users not in the doc team, right?

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

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

Israel Saeta Pérez

vedaw () Re: plone.org has been upgraded! - next steps

Reply Threaded

In reply to this post by Israel Saeta Pérez

Some javascript/style in this post has been disabled (why?)

Re: [Plone-docs] plone.org has been upgraded! - next steps If they will eventually go into the manual, we keep them as part of the “official” documentation for now. There will be a transition period, but we’ll get thing pared down.

On 1/1/09 12:06 PM, "Israel Saeta Pérez" <[hidden email]> wrote:

On Wed, Dec 31, 2008 at 11:01 PM, Steve McMahon wrote:

Just to clarify, my intention is to script the movement of
*everything* in how-to and tutorial to the knowledgebase, *except*:

1) Documents that are not published or have no sections specified.

2) Content identified for inclusion in an already-existing manual.
That will be turned into a manual section.

I may see if we can repurpose new.plone.org <http://new.plone.org> (now that the Plone 3
switch is done) to test and check the scripted part of the
reorganization.

In the case of the development section <http://www.openplans.org/projects/plone-documentation/developing-for-plone-section-assessment> , there are a lot of documents which could be merged with existing manuals or serve as a base for new ones, but they need integration work and can't become part of a manual without adapting them.

Does that mean these documents will go to the knowledgebase first and we will pick and integrate them in manuals later?

-- israel

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

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

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

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

vedaw () Re: plone.org has been upgraded! - next steps

Reply Threaded

In reply to this post by Steve McMahon

No harm in that.

On 1/1/09 1:10 PM, "Steve McMahon" <[hidden email]> wrote:

>> Does that mean these documents will go to the knowledgebase first and we
>> will pick and integrate them in manuals later?
>
> What if the script *copies* (rather than *moving*) the contents of
> identified how-tos into manual sections, setting the destination "in
> progress"?
>
> Then, the how-to can be removed after manual integration. We'll need
> to make sure to set a redirect from the source to the destination upon
> the completed integration.
>
> On Thu, Jan 1, 2009 at 12:06 PM, Israel Saeta Pérez <[hidden email]>
> wrote:
>> On Wed, Dec 31, 2008 at 11:01 PM, Steve McMahon wrote:
>>>
>>> Just to clarify, my intention is to script the movement of
>>> *everything* in how-to and tutorial to the knowledgebase, *except*:
>>>
>>> 1) Documents that are not published or have no sections specified.
>>>
>>> 2) Content identified for inclusion in an already-existing manual.
>>> That will be turned into a manual section.
>>>
>>> I may see if we can repurpose new.plone.org (now that the Plone 3
>>> switch is done) to test and check the scripted part of the
>>> reorganization.
>>
>> In the case of the development section, there are a lot of documents which
>> could be merged with existing manuals or serve as a base for new ones, but
>> they need integration work and can't become part of a manual without
>> adapting them.
>>
>> Does that mean these documents will go to the knowledgebase first and we
>> will pick and integrate them in manuals later?
>>
>> -- israel
>
>