Speaking as a sysadmin, not a developer, making the damn thing easy to
install is a great way to broaden your user base. So follow CPAN best
practices, don't reinvent the wheel, or write your own version of
"make", etc.
On 23/05/2008, at 10:36 PM, Nigel Hamilton wrote:
Hi Lyle,
> Experience, suggestions, dos and don'ts welcome.
I'm certainly no expert and I've still got lots to learn. But
here are some of the things I think make a good project:
* they scratch an itch - ideally the project lead has the problem
the software/project is solving
* there is a changelog
* an easy learning curve for new users
* easy path to contribution etc.
* an active *positive* community supporting it
* a commercially positive IP licence - not something that has an
agenda (e.g., GPLv3)
Nige
2008/5/23 Lyle <[EMAIL PROTECTED]>:
Hi All,
I've been planning an open source project for years, and I'm hoping
to
finally start it in the next few weeks. I'm wondering what's the best
way to start these things?
Grab a .org, open a Sourceforge account???
It'll be my first open source project, I want to try and get it right.
Experience, suggestions, dos and don'ts welcome.
Lyle
_______________________________________________
BristolBathPM mailing list
[email protected]
http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
_______________________________________________
BristolBathPM mailing list
[email protected]
http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
--
Jon Wilson, Sydney, Australia
Email: <[EMAIL PROTECTED]>
Mob: +61 4 0549 9490
Yahoo: phuq_eu, Skype: jonwilson
_______________________________________________
BristolBathPM mailing list
[email protected]
http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
