Re: [Framework-Team] Documenting the process
Hanno Schlichting wrote: Hi. 2010/3/24 Israel Saeta Pérez dukeb...@gmail.com: http://plone.org/documentation/manual/plone-core-developer-reference is the place for this kind of documentation. I'd prefer to keep all documentation in the same place instead of spreading it over plone.org and the Trac wiki. I talked briefly to Eric and Israel about this. I'll start working on this over the weekend / next week and we'll move everything into the Trac wiki to have all development of Plone information in one place. Any progress here? It would be very, very helpful for GSoC... :) -- israel ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Documenting the process
2010/4/26 Israel Saeta Pérez dukeb...@gmail.com: Any progress here? It would be very, very helpful for GSoC... :) Not much. I started by copying over the bits from various sources into one place, so all we had written down somewhere is now at http://dev.plone.org/plone/wiki/Development. The core developer manual from plone.org is gone as well. The next step is to reorganize the information into one structure and then update it. I'll continue to work on that :) Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Documenting the process
2010/4/26 Hanno Schlichting ha...@hannosch.eu 2010/4/26 Israel Saeta Pérez dukeb...@gmail.com: Any progress here? It would be very, very helpful for GSoC... :) Not much. I started by copying over the bits from various sources into one place, so all we had written down somewhere is now at http://dev.plone.org/plone/wiki/Development. The core developer manual from plone.org is gone as well. The next step is to reorganize the information into one structure and then update it. I'll continue to work on that :) Not much?! This is already a lot! Thank you very much for taking care of this, and of course don't hesitate to ask for help where you need it. :) One thing we can do to decide the structure is think about what info would we want to find when contributing to an external project. Imagine you want to contribute to Drupal or similar. Example: - I think I've found a bug. Where should I report it? (add-on products, documentation, plone-core, plone.org, translations...) - How do I set up a development instance? - I've found a bug in the code and have a proposed patch. How should I apply it? Do I have to request review and how? - I've written an add-on product and think it's so useful that it (or a slightly modified version) should be included with Plone. What's the process to ask for inclusion of a new feature? - I want to translate a product (either add-on or Plone itself). How do I do that? - I know how to do something and would like to write documentation about it. Where should I place the docs? - ... -- israel ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Documenting the process
On Tue, Mar 23, 2010 at 2:37 AM, Eric Steele ems...@psu.edu wrote: I'm finding that I'm consistently wrong about how I think whole Plone thing works. Every assumption I had coming into this job has been met with some sort of No, we have a process. It's just not documented. Let's fix that. Yeah! The process has changed over time and has been documented as part of mailing list discussion, IRC meetings and real life meetings, like the Strategic Planning Summit or the framework team meeting at the Plone conference in Washington D.C. The only two websites I can find that have any information are: http://dev.plone.org/plone/wiki/FrameworkTeam http://plone.org/documentation/manual/plone-core-developer-reference/overview/release-process Both of which contain some valuable and some outdated information. The information should probably be linked from: http://dev.plone.org/plone/wiki/Development I'm looking for some help in actually writing down the process of how a major release of Plone comes together. Rough list of necessary parts would be: * Choosing a FWT * Choosing a release manager * The role of the FWT * The role of the Release Manager * PLIP review process * By what standards is a PLIP judged? * By what standards is a PLIP implementation judged? * Creating the release Suggestions for missing sections? Anyone willing to help me write this? I can help. There's a good deal of our processes that emerge naturally or that are driven by interested and influential community members, like for example the whole general major roadmap planning. But it'll probably help to make it clear where mysterious things happen and where we have formalized processes that are actually followed. Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
