Community mailing list archives
Re: New Odoo programmer and his blog / Helloby
I don't think there is much point in debating which approach is better, because a strong community needs both.
Much of my experience for the past few years was in Django community, which has very good, very complete documentation AND a whole slew of other resources - independent blogs, podcasts, books, etc. To leave out one or another would be a mistake. It's important for people to be able to hear personal voices of other people working with the technology.
I feel it is currently much easier for me to write a blog post than to contribute to the documentation. Blog posts can be more personal, opinionated and at the same time less complete - I can just describe the solution I came up with anyway and dump it on the blog. I also feel less conscious about my language mistakes when it's my personal space. My blog is also peculiar, because it reflects a perspective of a total beginner.
At the same time I feel it's likely I'll start contributing to the official docs in the future, as I become more comfortable with Odoo over time. I really appreciate the encouragements to contribute - it's good to know that outside contributions are welcomed.
On Tue Oct 28 2014 at 11:47:59 AM Pedro Manuel Baeza Romero <firstname.lastname@example.org> wrote:
The mistake is to think that the paths suggested by Fabien, Lionel or others are "their documentation", or that they want to get advantage of it. It's not. It's OUR documentation (of all), put in a proper way, with a common rules to assure homogeneity, and in a good platform. If you don't want to collaborate, it's your decission, and you can get also advantage reading other's work, but don't give the false impression that it's best to go as the lonely ranger, because you're losing the best we have in an open source community: the power of the group.
Regards.2014-10-28 11:27 GMT+01:00 Lionel Sausin <email@example.com>:Le 28/10/2014 10:53, Kurt Haselwimmer a écrit : > If odoo is going to transition from a platform for 'those in the know' > who have been with the platform since it ran on a ZX spectrum to one > that can be embraced by the wider programming community, then they > need to start listening to voices like yours and listen less to the > existing partners who have built-in NIHS. May we all be spared from this sin! But yes, we do want to get our hands on Ludwik Trammer's talent and work. We're eager to feed the community that feeds us. Still, everyone is welcome to do open new routes: we're just suggesting existing ones to make sure newcomer make informed choices and their energy is not wasted. Lionel.