Joerg Sievers wrote: > Hi Mathias, > > Mathias Bauer wrote: >> Possibly we can establish a process that allows for more "asynchronous" >> work or creates the documentation in a "Q&A" style (QA or documentation >> ask for the information they need instead of forcing the developers to >> provide everything upfront). > > As some of us have desribed in a presentation [1] (slide 12+ is the > i-Team work described -> How to write a specification) held on OOoCon > [2] the i-Team should work together on the specification because they > are the stakeholder for the document.
As mentioned in this thread several times it is not possible to expect that contributions from community developers will have an iTeam. We should be able to integrate work done by community developers "to scratch their own itch". In this case the work is done in the way "problem seen - problem fixed - please integrate". I think we should follow this perception by avoiding the "iTeam" term where it isn't mandatory. I understood Michaels idea (that I - und now you - have quoted) in the way that he thinks that in this case where the development is done already when a community developers asks for QA we should think about ways to allow a less formal and Q&A oriented communication between developer and QA or documentation. I think this is a valid request that deserves some thoughts. Please let me repeat the restriction I made in my summary: this should apply to new developers only. If developers would like to continue contributing we should try to get them used to our a little(!) bit more formal working style over time. Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
