On "managing developers" -- that's kinda what I mean. Me and everyone else involved is volunteering time, so being told what to do doesn't make any sense (that's what I think of when I think of "managing"). Perhaps my use of the word overzealous was overzealous.
Letting people know what you're working on or what you're interested in working on is a good idea and I definitely agree with what RC said. --Philip On 5/21/07, Far McKon <[EMAIL PROTECTED]> wrote: > > Good idea, but let's not be too overzealous with this side of stuff. > > This may be a tough topic to talk about, because I think your > 'overzealous' is somewhere in other people 'normal project needs' > range. And perhaps Adam's 'minimum work' is somewhere in someone > else's overzealous range. > > IMHO, communication has been a bit poor at times, since different > folks have different expectations. This project is slowly > accumulating some contributors, and since Phillip is keen on coding, > not on managing developers, I think we should find a way to offload > that onto someone who would be interested in that end of things. > > Naturally, Scott comes to mind. He seems good at organizing, > documenting, etc. If Scott is interested, does anyone object to making > him the informal developer community organizer? > > -Far > > On 5/21/07, Philip Neustrom <[EMAIL PROTECTED]> wrote: > > Good idea, but let's not be too overzealous with this side of stuff. > > > > --philip > > > > On 5/20/07, Adam Dewitz <[EMAIL PROTECTED]> wrote: > > > > > > Regarding http://www.projectsycamore.org/Sapling/Roadmap > > > > > > Philip asked: > > > > > > "Can we keep features in their own branches so they can be rejected > > > or accepted more appropriately? In the past we've had monolithic > > > branches, like wikis, etc, but I think we should shy away from that > > > as much as possible as time goes on. (Meaning we just move these over > > > to the Sycamore version roadmap page, rather than have versions for > > > the "unstable trunk" [sapling]?" > > > > > > > > > I think this is a good time to discuss the future of Sycamore > > > roadmaps, release schedules, and all the other project management > > > tasks associated with (open source) software development. > > > > > > > > > > > > AD > > > > > > > > > _______________________________________________ > > > Sycamore-Dev mailing list > > > [EMAIL PROTECTED] > > > http://www.projectsycamore.org/ > > > https://tools.cernio.com/mailman/listinfo/sycamore-dev > > > > > _______________________________________________ > > Sycamore-Dev mailing list > > [EMAIL PROTECTED] > > http://www.projectsycamore.org/ > > https://tools.cernio.com/mailman/listinfo/sycamore-dev > > > _______________________________________________ > Sycamore-Dev mailing list > [EMAIL PROTECTED] > http://www.projectsycamore.org/ > https://tools.cernio.com/mailman/listinfo/sycamore-dev > _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
