> GH> Project map about what projects? > > Project: PHPDOC > Subprojects: PHPDOC TOOLS, LIVEDOCS, DOCWEB, USERNOTES > > Project: PEAR > Subprojects: PEARDOC, PEARDOC TOOLS, PEARWEB, PEAR AUTOMATION > > Project: PHP.NET > Subprojects: DEV-MASTER-WEB, DEV-BUGTRACK, SYSTEMS-MIRRORS, SYSTEMS-CVS, > SYSTEMS-ML, PHP-WEB, PHP-NEWS, PHP-NET-AUTOMATION or PHP-NET-TOOLS > > Project: PHP > Subprojects: PHP4, PHP5, PHP6, PHP-EXTENSIONS-CORE, PHP-EMBED, > PHP-ISAPI or PHP-INTEGRATION
> 1. Developers are not enough motivated not true. Developers work on what we WANT to work on, WHEN we want, unless someone is paying them to work on something specific. My instant livedocs, for example, has not evolved, primarily because: lack of expressed interest from anyone but me and Goba, I haven't received much feedback, I got hung up on a bug (http://bugs.php.net/bug.php?id=33608), and: > 2. Developers don't have enough time That's the big one. I'm tasked at 100% right now, with working, working [sic], raising a kid, and having a new house that needs care. A roadmap won't help, here. We'll just miss deadlines, and become MORE discouraged. Unless, of course, you've got a few hundred thousand dollars to start a foundation and hire people to be your roadmap-deadline-meeting minions. If that's the case, by all means, start it up, and recruit developers! (the foundation scenario is why roadmaps work for projects like Mozilla) One thing I HAVE noticed, however, is the project-momentum phenomenon. DocWeb is a perfect example. We go through commit-sprees -- someone commits some changes, and then within a few days we see dozens of commits.. a week later, the list is dead. The best way to lead, here, is to step up, do some work, and rally the troops, socially. If people are motivated, and they have time, they'll jump on the project and contribute. S
