Community mailing list archives
Re: OCA Organizationby
And third input:
Some reviewer's "gateway attitude" on PRs without adequate levels of comprehension and guidance is probably the one thing that most impacts the OCA experience.
Any of the kind of "I do it for free in my spare time so shut up" attitude is not a favour to the OCA's goals.
OCA always will be a "soft authority", and constitution of "soft authorities" work quite a bit different.
Look at the docker example, they do many things very well.David Arnold <email@example.com> schrieb am Do., 15. Okt. 2015 um 12:53:Next best (or even better) alternative:
Standardise, so at least I only need to learn something once and keep my focusing on being productive. :-)
- Markdown (used by GitHub, known by everyone who used it)
- Read The Docs as best practice for the output question.
- Numbpy auto doc Docstring, for nice and incentivised inline documentation.David Arnold <firstname.lastname@example.org> schrieb am Do., 15. Okt. 2015 um 12:47:Another input:
It should be dead simple to apport/improve documentation (specs or docs). I experienced one case, where the outlook to have to learn 1000 things (like rst, pylint, etc) before being able to improve a simple doc file made me give up because it is just not efficient to push my knowledge into the public repo. Opportunity costs are too high...David Arnold <email@example.com> schrieb am Do., 15. Okt. 2015 um 12:44:Great News, I'm one of those feeling left alone in the OCA process jungle ;-)Jay Vora <firstname.lastname@example.org> schrieb am Do., 15. Okt. 2015 um 03:27:Joel,Thanks, we are sure many people will add to the benefit of community and we can keep the spirit of opensource alive!Thanks.On Thu, Oct 15, 2015 at 1:13 PM, Joël Grand-Guillaume <email@example.com> wrote:That is really something that matter to me and all the board. Here is a first page to explain better about our organization:Dear community,Those past months were spent to define more about the OCA organization and their related PCS (Project Steering Committee). It appears that some of you wants to contribute to the OCA but don't know how, or have difficulties to understand how the OCA works.
https://odoo-community.org/page/organizationYou can also access now to a PCS Guide that explain what is expected from a PCS and his OCA representative:
https://odoo-community.org/page/oca-project-steering-committee-guideIf you're interested to join any of our PCS, please write us, explaining your contributions, to firstname.lastname@example.orgIf you're new to the OCA and Odoo Community world you can start contributing (no need to be PCC's member nor association's member). First thing to do would be to subscribe to the email@example.com and read the Contribute page.We'll work more on improving the way people understand how OCA works and how to contribute, making our members and contributors more involved in the OCA way in the coming months. More news soon.Best regards,Joël
----The Splendid journey of 2 years in Numbers---
<img src="cid:firstname.lastname@example.org" style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
Serpent Consulting Services Pvt. Ltd.
Web : http://www.serpentcs.com
Mobile : 91 - 9879354457Twitter: jaynvora
Blog : http://jayvora.blogspot.com