Community mailing list archives

community@mail.odoo.com

Re: The issue mountain on github

by
Andrei Levin
- 08/01/2015 05:44:24
There is a good practice to resolve this kind of problems: don't
accept new functionality until all bugs are fixed. This is the only
way to have a reliable code.

I can predict that when v.9 will be out the mountain of v8 related
issues remains where it is. Who will care about the old code?

Regards

Andrei

2015-07-31 20:09 GMT+02:00 David Arnold <dar@devco.co>:
> Third take. (Codetriage)
> Code Triage might be THE tool to advance towards the goals elaborated by the
> initial posting here on this list.
> Therefore tooling and guidance is necessary. Wording is crucial when
> educating users. So I created a pull request to include Code Triage with a
> first wording into the CONTRIBUTING.md (asuming that is where it would
> belong to).
> Please have a look, and if you like it, feel free to upvote to express your
> feelings.
> https://github.com/odoo/odoo/pull/7836
>
> I just did my first comment here: https://github.com/odoo/odoo/issues/6574
> If you feel, this might be a good thing, don't wait, just DO join!
> Best Regards, David
>
> El vie., 31 jul. 2015 a las 12:36, David Arnold (<dar@devco.co>) escribió:
>>
>> Hi there, a short follow up for your convenience:
>>
>> There has been actually some work done in this direction, which you can
>> find here:
>> https://github.com/joshrendek/github-postcommit-shinies
>>
>> As it is build on top of the sinatra framework, which handles some
>> plumbing, the relevant file to look is:
>> https://github.com/joshrendek/github-postcommit-shinies/blob/master/gh.rb
>> 77 Lines of Code.
>>
>> Could be reused with two parsers added (configfile and issue comments),
>> and we would be all set.
>>
>> Best Regards, David
>>
>> El vie., 31 jul. 2015 a las 11:44, David Arnold (<dar@devco.co>) escribió:
>>>
>>> To more involved parties:
>>>
>>> How others do (workflow patterns):
>>>
>>> http://www.ianbicking.org/blog/2014/03/use-github-issues-to-organize-a-project.html
>>>
>>> Probably, that's a motivating visualization to take further steps:
>>> https://waffle.io/odoo/odoo
>>>
>>> Where issues meta discussion could take place, to keep the repo itself
>>> clean(er):
>>> https://gitter.im/odoo/odoo
>>> (and NO, lagacy and NOT seemlessly integrated chat systems are no
>>> alternative)
>>>
>>> Something for Odoo-Folks (GitHub-Collaborators), to help them with the
>>> more advanced triage (assuming they can apply best practice approches here
>>> and are not bound to inhouse solutions):
>>> https://overv.io
>>>
>>> For those community-folks, who are desperately willing to help out with
>>> triage, but on a sustainable workload level (only as a multitude we can
>>> master it):
>>> http://www.codetriage.com/odoo/odoo
>>>
>>> I reiterate (ceterum censeo) towards Odoo SA the most important point:
>>> Make some script connected with webhooks (or as a last resort,
>>> periodically scanning the repo), which pareses issue and comment text, and
>>> looks for special well documented tags. (Think about "{tag}" ) The
>>> suggestion for implementation details follows, if you're not intrested jump
>>> over this parragraf:
>>>
>>> - .contributortag file in the root of the repository
>>> - consisting of 2 parts
>>> - tag definition
>>> - authorized contributors (can apply by pull requesting on this file)
>>> - special purpose github user which serves as author proxy (is an
>>> acceptable shortcoming)
>>> - (optionally) kind of different authorization levels mapping contributor
>>> classificacion to tag classification
>>> - (optionally) provide similar logic for community milstones, so
>>> community can better organize it's actual coding efforts. A implementation
>>> suggestion would be the following milestones maintained by selected
>>> (benevolent dictatorial) oca-contributors:
>>> "oca-main", "oca-next", "oca-bluesky"
>>>
>>> I hope, reader, you found this useful, and will be willing to undertake
>>> directed action which helps getting this setup soon. Please, if that sounds
>>> and adequate request to you, abstain from all too general purpose feedback.
>>>
>>> Martin Trigaux, you have shown, with you're status report on translation
>>> to everyone the tacit benefits of transparency. I hope I can, based on a
>>> common understanding about the power of transparency in the organization of
>>> multitudes, convince you to buy in on this idea and help to provide internal
>>> guidance to make this idea happen ;-)
>>>
>>> Best Regards
>>>
>>> David Arnold
>>>
>>> Ermin Trevisan <trevi@twanda.com> schrieb am Do., 30. Juli 2015 um 23:47:
>>>>
>>>> +1
>>>>
>>>>
>>>> On 30.07.2015 11:17, Alan Bell wrote:
>>>> >
>>>> > what I am after is not Odoo fixing all the issues, I am after some
>>>> > kind of triage, or discussion, some comment saying "yeah, that seems
>>>> > valid, go ahead and fix it" or "you are wrong, it works fine" or "you
>>>> > are thinking about it all wrong, you should be doing this instead" or
>>>> > "fix it in your own instance if you want, it isn't inline with the
>>>> > project goals".
>>>> >
>>>> > Alan.
>>>> >
>>>> >
>>>>
>>>> --
>>>> twanda AG
>>>> Ermin Trevisan
>>>> Artherstrasse 19
>>>> CH-6318 Walchwil
>>>> T    +41 41 758 1515
>>>> M    +41 79 208 7373
>>>> E    trevi@twanda.com
>>>>
>>>> www.twanda.ch
>>>> www.ipadweinkarte.twanda.ch
>>>>
>>>> _______________________________________________
>>>> Mailing-List: https://www.odoo.com/groups/community-59
>>>> Post to: mailto:community@mail.odoo.com
>>>> Unsubscribe: https://www.odoo.com/groups?unsubscribe
>
> _______________________________________________
> Mailing-List: https://www.odoo.com/groups/community-59
> Post to: mailto:community@mail.odoo.com
> Unsubscribe: https://www.odoo.com/groups?unsubscribe



-- 
Didotech Srl

Via T.Aspetti, 248
35133 Padova (PD)

Tel 049 8592286
Cell.: 347-2426694
www.didotech.com