On Sun, Sep 7, 2014 at 1:38 PM, Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote: > [...] > It makes sense for people who are going to contribute changes to have a > vision > of that change, and to proclaim it loudly. "I imagine that we can invert > the > parser so that..." is a very useful vision to present. I have said that > from > the beginning. > Agreed. > > "This is where I, project manager, see the entire project in five years," I > said, is not, because my task here is to review, approve, or veto; not to > personally cause code to be written. > Fair enough. > > > Except for a few problems: > > 1. Work will not begin for newbies (or new-comers, or beginners, or > random > > contributors) if they don't know what the project would like to have. > > "The project" doesn't have a will. Alternately: if you had asked me to > make a > list of the top 20 things I thought we should have, in 2012, subroutine > signatures would not have been on them. What would that have meant, if a > clearly-stated vision of the future didn't include the feature that's > probably > the one people are most excited about from v5.20? > If there was a list created by various people, subroutine signatures would have been there for a long while. > > > 2. Lacking a direction means that any suggestion is just as justifiably > > shot down as any other. > > I don't think I find this compelling. It's seemingly equivalent to: > > Lacking a stated project plan, it means all suggestions must be discussed > with equal consideration. > Yes, it is equivalent. But I don't think it matters. Many people don't see p5p as a place to discuss ideas, but to have them shot down, and then to not raise them. Existence of a plan helps with that.Thread Previous | Thread Next