On 2/28/12 7:22 PM, Juha Manninen wrote: > 2012/2/28 Rich Saunders <[email protected] > <mailto:[email protected]>> > > Another idea is for someone to summarize a lengthy exchange in a > mailing list. The summary would be something along the lines of: > "The idea of X has been brought up and discussed at length. There > appear to be 3 options for moving forward. A would be least > disruptive. B would take the most work but would produce the ideal > result. C would be an alternative to B but would take the project > in a whole new direction. The core team would like to pursue B but > needs Y or Z to be done first. Anyone who wants to pursue C should > know their efforts will be difficult to integrate in the future. > See the following wiki page for our current plans in this area." > > A summary like to would certainly help me understand where we are > on the documentation issues that have been discussed in the past > week or so. > > The value of it is in helping everyone understand that the core > team is paying attention to the issues that are brought up and > that steady progress is being made (even if it only discussing an > issue and placing it properly in the context of the developmental > plan). > > > Rich, who would make that summary? I hope you don't mean the core > developers would have to make it, in addition of using all their > available time creating code and documentation. Of course, the core developers would not be expected to do it unless they chose to. I see it as a project management task. > A right attitude from you would be to offer yourself to make such summary. I'm considering it. If productive exchanges like this project management thread continue I might just start doing it. We'll see how it goes.
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
