Re: Documenting Plone 3.3 PLIPs -- assignments and further work (moved from plone-docs)
JoAnna Springsteen <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Would those who have tickets assigned for documenting PLIPs (http://tinyurl.com/b4kj4a) Please put an update in the comments of the ticket so we know what your progress has been? The Framework team has graciously included us very early on in the development process. We absolutely can not let them down with this work. These need to be documented by the time 3.3 comes out or very shortly after (read: a week after is shortly after). If you need help, don't have the time, don't have the knowledge, etc, please let me know asap. I will help you find the resources to figure out the ticket. Updating documents in a timely matter according to releases is a part of our doc team roadmap. This is a bit of a new process to us. If you have any questions at all, please let me know. This is something we need to work into our routine of being doc team members. If you'd like to volunteer for any of these items (or others) email me or the list in general. I know we can do this! There are only a handful of PLIPs that need documenting! go team docs!! J. On Sun, Jan 25, 2009 at 3:15 PM, Israel Saeta Pérez <[email protected]> wrote: > I've already assigned all the tickets to current editors using my own > criteria. Please check the list and reassign them if needed. To work on them > I suggest following this process: > > Make a list of documents affected. This list may include only documents > which are selected to go to the official documentation area. > Make a copy of them and find someone to document the changes. > Ask the implementer of each PLIP to review the introduced documentation > changes. > After the 3.3 release, copy the contents of the copied articles back to the > live ones, and delete the copies. > > I wouldn't like us to fail at this point because I feel that, if we fail > documenting 3.3 PLIPs, we will disappoint the whole framework team and they > won't trust us going to do this anymore. > > Go, editors, go! > > -- israel > > > On Thu, Jan 22, 2009 at 3:33 PM, Israel Saeta Pérez <[email protected]> > wrote: >> >> On Thu, Jan 22, 2009 at 1:36 PM, Wichert Akkerman <[email protected]> >> wrote: >>> >>> Previously Israel Saeta Pérez wrote: >>> > On Thu, Dec 25, 2008 at 5:29 PM, Israel Saeta Pérez >>> > <[email protected]>wrote: >>> > >>> > > I've filed some bugs in Trac on the documentation component regarding >>> > > Plone 3.3 accepted PLIPs >>> > > documentation<https://dev.plone.org/plone/query?status=new&status=assigned&status=reopened&component=Documentation&milestone=3.3&order=priority> >>> > > . >>> > > >>> > >>> > I've already seen some 3.3 PLIPs implementation announcements in the >>> > framework-team mailing list describing what documentation changes would >>> > be >>> > needed. Should we assign the related documentation tickets to avoid >>> > leaving >>> > this task undone? >>> >>> Is this making any progress? >> >> I've added some documentation info from the framework-team list messages >> to each ticket. >> >>> >>> I'ld suggest to just go ahead and assign tickets to people. >> >> >> I've already assigned some of them, but I'd prefer our editors to have a >> look at the tickets and accept the ones belonging to their sections. >> >> >> -- israel >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Plone-docs mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/plone-docs > > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com