+1,  favorable to a Git for ONAP IM in Papyrus.

ONAP modeling subcommittee can be responsible for this with committers based on 
commit operation in papyrus.
Use GenDoc to document the model.
Approach it in Beijing release, learn from the experience and  be more 
effective in Casablanca release.

BR
Michela

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Brian Hedstrom
Sent: den 2 februari 2018 16:12
To: denghui (L) <denghu...@huawei.com>
Cc: jessie jewitt <jessie.jew...@oamtechnologies.com>; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org P <onap-...@lists.onap.org>
Subject: Re: [onap-discuss] [modeling] Whether How and when we should move to 
Github for modeling spec update process

Hi Deng,
I'm in favor of using Git for model development.
Do we want to add a Poll page to the wiki to track participant voting on this 
topic?

Thanks
Brian

On Wed, Jan 31, 2018 at 7:31 PM, denghui (L) 
<denghu...@huawei.com<mailto:denghu...@huawei.com>> wrote:
Hello modeling subcommittee,

Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

DENG Hui



--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology<http://oam.technology>
brian.hedst...@oamtechnologies.com<mailto:brian.hedst...@oamtechnologies.com>
720-470-7091
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to