1. Mailing Lists
  2. Contributors
  3. Re: Odoo Scrummer - run your projects by Scrum in Odoo

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Odoo Scrummer - run your projects by Scrum in Odoo

Re: Odoo Scrummer - run your projects by Scrum in Odoo

Avatar

Re: Odoo Scrummer - run your projects by Scrum in Odoo

by
Vauxoo, Nhomar Hernández
- 25/10/2017 23:48:06


Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

On Wed, Oct 25, 2017 at 9:17 AM, Igor Jovanovic <igor.jovanovic@modoolar.com> wrote:

Dear community,


First of all, thanks to all of you who have answered to our email - for your support, concrete responses and expressed readiness to contribute to this project. We are very happy to see that there is a real need for a tool such as Scrummer.


The situation is much clearer to us now after we`ve got the answers, so let me sum it up quickly:

  • It will be free with LGPLv3 license in use

  • There is a room for a separate repo under OCA umbrella

  • We have to sign the CLA (I believe entity CLA version)

  • We will be steering and maintaining the further project development


We did have an internal discussion based on all of your answers, where a couple of new questions and ambiguities have arisen and we would appreciate your guidance on this as well:

  1. We are still discussing @Daniel proposal of renaming the project to project-agile (practical pros and cons). Was this name proposal your idea to help us keep the brand Scrummer for ourselves? You said that every module under OCA should be unbranded, what exactly does this mean? Also, could this repo/project be called oca/odoo-agile, or just oca/agile instead of oca/project-agile?
  2. We understand that we would steer and maintain the project, but we are not sure about the exact duties and rights we would have. Given that the project is new and initiated by us, we assume that we would form the initial PSC for the project. Is that right? 
  3. Regarding your proposal that some of the project modules (ie. project-workflow) end up in the different repo (ie. oca/project), what happens if a module from OCA/project gets changed in the way that breaks the compatibility with the Scrummer? How is that regulated then? Basically, that is the only problem I see in this proposal which makes sense to me fully from the overall code organization perspective.

Regarding this, you can custom-do (we can help once it is merged) to ttrigger some automated checks, if everything is done properly with unittest, it is fairly easy (that's not a 1 sprint work, the maturity itself will help).

 

Thanks a lot to everyone. We would like this first step to be done properly, so we apologize for being a pain in the neck. :)


Cheers




On Thu, Oct 19, 2017 at 12:02 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

+1 for the name

--
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 APAC 2014 and 2016
On 10/19/2017 05:32 PM, Daniel Reis wrote:
<blockquote type="cite" cite="mid:20171019101935.Horde.R3klOLK7yB5_q2r8NYrkqx-@mail.sapo.pt">I suggest OCA/project-agile.

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


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


Reference