On Tue, Sep 2, 2014 at 11:57 PM, Jarkko Hietaniemi <jhi@iki.fi> wrote: > On Tuesday-201409-02, 15:23, Kent Fredric wrote: > >> I'd imagine some of the things on this page have also been attempted in >> part, and may be lying around incomplete on a branch somewhere ( I count >> 439 branches, and I have no idea which of those are still relevant, or >> pertain to work in progress things on this list. ) >> > > But regarding "roadmap" (yes, I guess I'm one of those people allergic to > that word) I think it comes down to two things: > > (1) having an itch > (2) having the resources (time, people) to scratch > I don't think a roadmap should interfere with this course of development. People usually work on their itch. That's not a bad thing and that doesn't contradict knowing where you want the project to go. You maintain a list of "if we had @these, we would be able to get $there". People can then choose to work on any of @these or simply their itch instead. No one can tell you what to work on, and no one would appreciate your work and contribution any less. These are quite a few people who would be interested in knowing what @these were, and contributing directly to that, in order to push the project forward. I mean, isn't that some of the purpose of the TODO list? Point people at things they could work on, if they're open to picking up possible important tasks that aren't already their itch? The roadmap should not be telling people "this is now what you work on". That would be silly. :)Thread Previous | Thread Next