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
namespace anybody
inkdroid on 2003-09-02T23:15:57
Perhaps:
- a catchy yet descriptive CPAN namespace
- a test suite with good coverage
- an article on perl.com
- thousands, no millions of fans worldwide
- flame wars on slashdot
License choice
Dom2 on 2003-09-03T10:06:17
Personally, I prefer BSD license, but it's your choice.
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
SourceForge alternative
IlyaM on 2003-09-08T09:24:32
Try
Savannah. I've been considering moving there my SF projects myself. Last time SF is extremely buggy - I hadly can recall when mailing list archives were working correctly last time.
