Re^2: Open sourcing perlmonks

Yes, people could submit patches. In my experience however, there aren't great masses of people lining up to submit patches to most open source projects.

True, but putting any barrier in front of the source is going to make it less likely. I know I've been tempted to write some patches for perlmonk on occasion, but have been too lazy to jump through the necessary hoops to get at the source.

Comment on Re^2: Open sourcing perlmonks

Replies are listed 'Best First'.
Re^3: Open sourcing perlmonks by demerphq (Chancellor) on May 28, 2005 at 11:24 UTC
The hoops involved are asking one of gods for membership and then activating several pmdev specific nodelets. And possibly reminding Corion or myself to give you access to the test server. Once this has been done reviewing the code is fairly easy and IMO mostly intuitive. --- $world=~s/war/peace/g	[reply]
Re^4: Open sourcing perlmonks by adrianh (Chancellor) on May 29, 2005 at 10:05 UTC
The hoops involved are asking one of gods for membership and then activating several pmdev specific nodelets. And possibly reminding Corion or myself to give you access to the test server. Once this has been done reviewing the code is fairly easy and IMO mostly intuitive You missed the biggest hoop of all - finding out what the hoops are :-) Maybe add your list to the description of pmdev?	[reply]