* Sawyer X <xsawyerx@gmail.com> [2014-09-07T04:55:17] > So, let me rephrase my question. Instead of "Is there a vision?" I'll ask > "Is the vision to just keep it doing what it does with no real changes?" I already said that *I* don't have "a vision" for the future, and that I think it would be pointless to try to declare one. As to whether I think the project should merely keep running without any useful new changes, I think v5.20 should make my answer pretty clear. 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. "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. > 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? > 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. -- rjbsThread Previous | Thread Next