Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: New Business Requirement repository [ex-Re: Gap analysis modules]

Elico Corp, Eric Caudal

- 03/06/2016 06:39:33

Hi everybody,
Getting there: all PR have been pushed to the repo (8 in total). You can find them here: https://github.com/OCA/business-requirement/pulls

We are finishing a small refactoring about price handling, so 6 of them are still WIP (probably until Monday).
2 are operational and can be tested and reviewed (https://github.com/OCA/business-requirement/pull/2 and https://github.com/OCA/business-requirement/pull/3).

BTW: I do not have the proper labels in the repo (WIP/needs review): somebody can help me with the set up? (could not find it...)
BTW2: we have strange errors in pylint complaining about rst format while standard editors (and github) do not. Help is welcome on the topic.

Thanks for the feedback and review!

--
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/02/2016 09:08 AM, Nhomar Hernandez wrote:

On Wed, Jun 1, 2016 at 7:37 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Later ideally we should freeze the current version in v8 and start migration to v9. For this part we need help, mostly on reviewing, testing, debugging, etc (usual community work).
Another topic for help is currently we use an experimental docx reporting engine for BR report. It works but has limitations (mostly in handling html code) and it is not that beautiful. We need to plan a clean qweb version.

We did already a qweb-excel convertor here:

https://github.com/Vauxoo/addons-vauxoo/tree/8.0/controller_report_xls

then I think we can use a similar approach for docx (but BT, I prefer stay into good PDF reporting with some kind of rst/md support) than use MS office jeje. (we can discuss afterwards that).

This is only part of the roadmap which includes for longer term:
* change request management

I supose the flow right?

* integration with earned value reporting

I need more context, what are you planning here?

* BI report (we have one but needs cleansing)

I can help once I start use it when my DB is migrated to v9.0 (Now I am full and We have pretty stable v8.0 but for sure I am planning migrate manually our User History tool to a better approach, the it will be a mix of New Odoo's + Ours + Yours for sure).

* Complex parenting (parent/child/depends on/mandatory/options/etc)

I need check it... No too much info here

* integration with etherpad (which provide some version control)

Did you check the document page approach under OCA? I think we need extend that in order to have a manual management mixed with ISO's ones, I think that should be the proper approach.

Nhomar Hernandez

CEO Vauxoo.

Site: http://vauxoo.com

Twitter: @nhomar

Blog: http://nhomar.com

Github User: https://github.com/nhomar

Odoo Gold Partner

Skype: nhomar00 (Envia mail previo no lo superviso siempre).

HangOut: nhomar@vauxoo.com

Móvil Venezuela:
+58 4144110269

Móvil México:
+52 1 4773933942

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