Op dinsdag 2 mei 2006 10:27, schreef Dries Buytaert:
(ii) code that has yet to be written.
I tried a raodmap once. In the handbooks. It did not work, because (i) some people did not want it to work and (ii) people were not bothered about it, while (iii) it was too far hidden away to be of any real value. However, I learned one thing. The fact that I had some nice tasks on there brought in people whom might otherwise have been 'lost'. They mailed me in person, because my name was behind a certain item in that map. They needed that same goal/item done. Hence we had a team. So we can also see a roadmap as something to show peolpe the shortcut-roads to effective developement! Instead of hacking up i18n, or start i10n, or so, that developer can now see that there is an active team with clear goals and tasks, working on getting certain i18n features out there. He might just as well join, instead of the long route (mailinglists, IRC and more stuff that half of the developers don't have time for) on his own. Yes. groups.drupal.org will fullfill this purpose, I guess. If only we can summarise the activity on groups.drupal.org on a prominent page, then *we have a roadmap!* -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com | Heeft het gebruik van Sympal gevolgen voor de eigendomsrechten van het gepubliceerde materiaal?: http://help.sympal.nl/heeft_het_gebruik_van_sympal_gevolgen_voor_de_eigendom...