Re^3: Run your own perlmonks!

[Aristotle]

In my experience, getting people to do work is more work than doing the work yourself around 90% of the time.

Then you obviously dont know how to delegate. The only way I can see this being true in your life is if you like to micromanage people doing work for you. Its obviously not generally true otherwise organizations and businesses would not be able to function, having a situation like that that would just mean that financial collapse is on the way.

You overlooked a minor detail. It's the implication of the word "voluntary" in chromatic's sentence. Most businesses pay the people that do their work for them. So I'm not concerned about financial collapse, just yet.

While I appreciate your sentiment, I think you're reading chromatic's post much too negatively.

I do believe that he has a good point when he says we're not likely to attract a lot of volunteers by opening the code base. After all, getting adopted into pmdev is not very difficult (heck, I made it in just because I inquired a few minor details about the site from tye to write my newest nodes interface). That fact could, maybe, be advertised more, of course.

But as tye has explained time and again, and which is something only implied in chromatic's post, the lack of gods is a problem because patches have to be tested - both by themselves as well as in their interaction with the rest of the codebase. Obviously, it's easy for a god to do that for their own code on the "shadow" PerlMonks devel setup they have. Since that one runs on a backup of the live PM database, I can understand that they don't want to open that. (Or do you want all your /msg's out there for everyone to read?) So you have a situation where a small handful of people (with limited time on their hands to boot) have to validate all foreign code passed in from outside.

I think the biggest problem we face is what perrin has often complained about: that the code is stored in the database. Were it completely separate, it would be much easier to make the code available, and hand out a mock up database to test it with, without any of the security and privacy issues of the current setup.

Before that changes, contributing to PM development is always going to be a cantankerous matter.

[demerphq]

because patches have to be tested

Indeed. In fact I mentioned it twice in this thread already. :-)

Don't tell anyone, but that issue is currently in hand, and with a bit of effort and luck will be a done deal in a few weeks, if not sooner.

While I appreciate your sentiment, I think you're reading chromatic's post much too negatively.

I may have. I think I did him a disservice in my original reply that I apologised for. I think that if one point this thread makes clear is that its real easy to mistake the underlying intentions of people who are passionate about what they believe (in), especially is such an inpersonal forum.

cheers