Follow Slashdot stories on Twitter


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Ask Slashdot: Should You Invest On Documentation Or UX? 1

fpodoo writes: We are going to launch a new version of Odoo, the open source business apps suite. Once a year we release a new version and all documentations have to be rewritten as the software evolves a lot. It's a huge effort (~1000 pages, 250 apps) and it feels like we are building on quicksands.

I am wondering if it would not be better to invest all our efforts in R&D on improving the user experience and building tools in the product to better help the user. Do you know any complex software that succeeded to avoid a documentation by having improved significantly the usability? As a customer, how would you feel with a very simple product (much simpler than the competition but still a bit complex) that has no documentation?

Comment Engage with your community earlier (Score 1) 57

At Odoo, the Open Source ERP, we work with around 1000 partners and/or customers that have a dedicated IT department developing Odoo modules/apps. From my past experience working with them, I would say that it's less about contribution than collaboration.

Some companies think that it's good to contribute to open source (for different reasons) and they just do that. It's usually a big failure as nobody uses their code and they get nothing from having published their development. The main reason is that something that has been developed for your own need rarely fit others needs (in terms of quality, feature, collaborative platform, ...).

If you think about it in terms of collaboration (working on github since the beginning, blogging about what you do, answer on issues, tweets, ...) you can get benefit from your open source contributions. Those benefit are mostly about small contributions (bug reports, translations, new features) or visibility. The key is to make it easy to on board new users/developers: work on the platform they already use (github), use transifex for translations, ...

I think it's a bad idea to start your repository private at the beginning. People are always afraid to "show to the world" an unfinished development but it's not a real issue if you are transparent about the status of the project. If you want people to feel engaged in your project, you have to on board them since the beginning. And contributions are more valuable if they come earlier in the development process. We noticed we get a much better engagement with our communities when we engage them in the very early stage of the project, at the analysis phase.

Protecting your IP is quite easy: choose the right licence and set a Contributor License Agreement. Merge Pull Requests only if they agreed on your CLA.

Comment Go for an open source ERP (Score 1) 209

With today's open source ERP, you don't need to choose between "do it yourself" or use a proprietary software. Check Odoo, the #1 Open Source ERP. You can reuse existing apps according to your own needs (it has 4000+ modules) but you can also control it and host/maintain it yourself. It's not 100% thrid party vendor or 100% in-house. You can do in-house what you want and benefit from external applications and, even external services if needed (upgrades, support, ...). With an open source solution like Odoo, you put the bar where you want.

Slashdot Top Deals

In the realm of scientific observation, luck is granted only to those who are prepared. - Louis Pasteur