[pmwiki-users] Any hope for 2.2.0 stable release?
radu at monicsoft.net
Thu Jan 15 17:16:14 CST 2009
On Thu, Jan 15, 2009 at 1:25 PM, Henrik Bechmann <
henrik.bechmann at sympatico.ca> wrote:
> Did I call them committees? Can you give references? <grin>
Any group that works together on making decisions is a committee... Bah,
semantics... New problems arise: who's going to make the final decision on
everything? Who does what and when? Why didn't they do it, if they said they
will? The way it works now, is that if there are goal differences in
implementing a feature, each dev (or group sharing the same goals) works on
a different recipe.
> I think more in terms of teams, and yes I think that discussion and design
> are worth the effort, ie they save time in the long run.
How's that? If you have followed this list for a while, you can see that
pretty much every member has a different goal, different needs, different
types of user bases. So they would make decisions based on what their own
> Doing random things on a complex codebase "if you have five minutes" is
> nuts. I presume you're not serious.
No, I'm not. Seriousness is overrated :) And in determined people, it leads
to ulcers :) I like to have fun programming. Which is why I don't work for a
> Sounds like you're a developer (as am I). Glad you like it as is. So do I.
> But I think there are lots of areas for improvement, particularly WRT
> usability. And if we're going to do it as a group we better get organized
> about it, or do you really promote the idea of random people doing random
> things to the core codebase if they have five minutes?!?
Yes. That's what I do with my pmwiki farms. That's what many other pmwiki
devs do on theirs. But we're not imposing our solutions on others. The core
is PM's to do what he needs with. He usually takes good suggestions and
explains why he rejects other ones. A couple of times what I needed (and
thought was ok with respect with PM's Philosophy statements), did not meet
with his approval, and he had his reasons. Remember, the project is his, and
he chooses what to do. We're only along for the ride. If I disagree with
some choice of his, I fix it in my cookbook folder, not in the core. When
the core changes radically, sometimes I have to change my recipes. Luckily,
not very often at all.
> IAC you're certainly entitled to your opinion. But if you're really happy
> with it as it is, then take a copy, and step aside. This discussion isn't
> relevant to you.
I thought you were asking for opinions from Pmwiki users :)
I am happy with the development as it goes now. The core belongs to PM and
until he decides he doesn't want to deal with it anymore, I trust his
coordinating vision (One man, one vision; a group brings dissension, even if
only potentially). On recipes, we all have free range. BUT. If you want to
OOP pmwiki, it will be something else altogether, and all recipes will have
to be rewritten too. Brrr!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pmwiki-users