Stefane Fermigier

Top 10 reasons for open source success - How does Nuxeo stack up?

| Comments

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

We do: https://github.com/nuxeo/nuxeo/blob/master/README.md

2. You don't include tests, specs, features, examples

Tests (unit tests, integration tests, functional tests, performance tests, you name them) are all over the place in the Nuxeo source code. You can check their status on our Hudson Jenkins CI server.

Features are described on nuxeo.com.

For samples, you can try here first: http://doc.nuxeo.com/display/NXDOC/Customization+and+Development.

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

http://www.nuxeo.org/.

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

nuxeo.com and nuxeo.org.

6. You don't have a Twitter Account

We have: @nuxeo for general news and @nuxeodev to track development activity.

We also have:

7. Your licensing is unclear

We're LGPL. See:

http://hg.nuxeo.org/nuxeo/file/c266ac435a55/licenses/README.txt

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.

Conclusion

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).

Comments