Top 10 reasons for open source success - How does Nuxeo stack up?
In a somewhat subtle self-promoting exercise thechangelog.com has an
interesting post called "Top ten reasons why I won't use your open source
project" and while it somewhat applies to smaller, younger projects, we
thought (as our friends of the Glassfish project recently did) we'd benchmark the
Nuxeo project on those reasons.
1. You don't have a friggin Readme
2. You don't include tests, specs, features, examples
Features are described on nuxeo.com.
For samples, you can try here first: http://doc.nuxeo.com/display/NXDOC/Customizing+Nuxeo.
We don't have big requirement documents, but we manage our development process in a transparent way on our issue/task tracker.
3. You have no project home page
4. You need design help
Our websites, as well as our applications, are designed by a small team of web designers who are also experienced as interaction specialists.
5. You don't have a domain name
6. You don't have a Twitter Account
We also have:
http://doc.nuxeo.com/: the reference source for documentation about the Nuxeo products, from user and installation guides to advanced programming reference.
http://forum.nuxeo.com/: the user forum, where thousands of Nuxeo users gather to ask and answer questions, as well as share information and tips.
http://blogs.nuxeo.com: our blogs, where we post news, implementation and R&D reports, new releases announcement, etc.
7. Your licensing is unclear
We're LGPL. See:
8. You don't reach out to me
Besides Twitter (@nuxeo), we also encourage you to join the Nuxeo User group on LinkedIn, watch videos and screencasts on Nuxeo.TV, look at our slide deck collection on SlideShare or subscribe to our RSS feed.
9. You don't speak about your project at conferences and meetups
See our events pages.
We even organize conferences to keep our community updated and reach out to new users.
10. You didn't submit it to The Changelog
OK, we didn't do (because we had no idea they existed). We'll try to fix this ASAP.
I think we didn't fare too bad on that test. The alternative would have surprised me, given we've been doing this for the last 10 years and have been pionneering this model, in the context of Enterprise Content Management.
So, what do you think? Is there any way we should improve the way the Nuxeo project is managed to get more people on board?
Please use the comments to make your opinion count (or contact me at sf(at)nuxeo.com).
Category: Product & Development