1. Mailing Lists
  2. Contributors
  3. Re: Collaborative feature design

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Collaborative feature design

Avatar

Re: Collaborative feature design

by
ForgeFlow, S.L., Jordi Ballester Alomar
- 07/06/2016 08:06:03
What if each repo had, in the beta branch, a 'Blueprints' folder that contained the various blueprints proposed? 

A user goes to the repo, selects the branch, opens the folder 'Blueprint' and creates a new file. Writes the specifications and creates a PR. The PR is merged quickly. All this can be done only with Github, so it's easy for people to use. Then others can comment using issues and referencing to the blueprint, or can propose new PR's.

Regards,
Jordi.

 

On Tue, Jun 7, 2016 at 2:23 AM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Agree: having a document (blueprint.md or whatever) is the way to go (easy to contribute).

This is complementary to the beta repo actually. During the business requirements developments, it was very helpful for us to share the pre-beta version to the community and share the ideas with contributors.

This is why I agree on the beta repo/branch idea: it unveils hidden initiatives that would not show.

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 06/07/2016 06:08 AM, Daniel Reis wrote:
<blockquote cite="mid:20160606225850.Horde.m-GsNvqEbTnngSoVEZ1Rn-1@mail.sapo.pt" type="cite"> 
 From Maxime:

> The process I would like to experiment is:
>  * Document new features and new contributions in Github issues
>
> I would like to encourage every new and current contributors to  
> contact the PSC on the mailing list or with a GH issue to announce  
> their intention to work on something. Figuring out things on a PR is  
> too late and increases the chance to get contributions refused,  
> frustrating the contributor and the PSC

This is also a very interesting discussion.
Since it is quite different from the workflow topic from, allow me to  
open a a separate thread for it.

I agree that feature designs should be shared as early as possible.
As Maxime said, this allows us to validate our idea and to get  
suggested solution we didn't think of.
Sometime we will be told "it's been done" or "there is a better way",  
saving us a lot of work.


I have tried sharing early designs through GitHub issues.
Having the early feedback on them is good.
Answering to objections makes the design better and stronger.

But I miss the ability to comment inline, like we do in PRs.
Next time I propose design specs I will try a PR: a new directory with  
the name of the future module, containing a "Blueprint.md" file with  
the specs. People should be able to start discussion around specific  
portions of the text, and even propose changes through GitHub GUI.


Regards
Daniel

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--
Jordi Ballester Alomar
CEO & Founder | Eficent

Reference