NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
samtregar (2699)
Tuesday September 02, 2003
05:26 PM
An Open Source Checklist
I've got that old familiar feeling... For the n'th time I'll be packaging a large chunk of internal code for an open source release. So, let's see, what will I need?
- Better Documentation - particularly of the introductory sort that you don't need when everyone's already onboard.
- A New Installation System - preferably one that doesn't require you to run Redhat 7.3 on i686!
- A Webpage - let's make it orange!
- Mailing Lists - is there something free and better than SourceForge?
- Change Tracking - sigh, time to start duping important commit messages into Changes.pod.
- A License - BSD is easy to sell to the lawyers, but wouldn't GPL be smarter?
So, what did I miss this time?
-sam
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
namespace anybody (Score:3, Insightful)
Reply to This
License choice (Score:3, Insightful)
I'd just like to say that if you do go for the BSD license, please choose the mordern 3-clause one, not the ancient 4-clause one. Thanks,
-Dom
Reply to This
SourceForge alternative (Score:2)
Ilya Martynov (http://martynov.org/ [martynov.org])