IM Discussion Process Discussion Call 20180521 Discussion Points
- Slides: 8
IM Discussion Process Discussion Call 20180521
Discussion Points • Workflow Clarification • Papyrus Model Maintenance Team • Papyrus Model Maintenance Repo and Related Issues 2
IM Discussion Process – Current Workflow contribution weekly call weekly basis thread level Wiki Workspace submitted Merged/ abandoned input agenda Subgroup calls discussed backlog closed work in progress discussion Subcommittee calls group call rough consensus after approval clean request for approval subcommittee last call on-demand subcommittee level (1~2 weeks) after model freeze Documentati on 1. Model freeze 2. (Readthedoc) Model publication release level 3. Wiki Workspace as the main discussion platform Including UML class, datatype, relation definition in the contribution and wiki discussion Readthedoc for final documentation 3
IM Discussion Process – Papyrus Tooling Additions wiki Discussion Phase papyrus Input provide input Discussion reach consensus Clean model freeze reflected in papyrus Papyrus model freeze Publication Phase Model Freeze RST doc Approval for publication Model Final Papyrus Tooling Guidelines: • use wiki as basic tool, papyrus as supporting tool • all discussion/Documentation MUST have a wiki page format, while its corresponding papyrus models are nice to have and OPTIONAL • Whenever papyrus gendoc is used for a wiki page, the corresponding source files be provided as a reference link Discussion Phase: • proposals go through input -> discussion -> clean -> approval phase • NOTE: when to move to the papyrus is left for discussion • Preferred but not required: track clean version progress in papyrus in parallel • Encouraged but not required: track group discussion progress in papyrus in parallel Publication Phase: • Minimal: include papyrus documentation after model freeze • use wiki, RST document, papyrus to publish final model • need to ensure the consistency among the three • Preferred but not required: use papyrus gen doc to generate RST form papyrus Note: after the model freeze • MAY update the model during review • need subcommittee's approval for final publication 4
Discussion Points • Workflow Clarification • Papyrus Model Maintenance Team • Papyrus Model Maintenance Repo and Related Issues 5
Model Editors • Assumption: agreement on the overall hierarchy and organization of common model constructs and divisions of sub-models. • Editor required on tracking current working threads (TBA) - VNFD: Xu Yang(yangxu 5@huawei. com) - NSD: Any volunteers? - WAND: Chuyi Guo (guochuyi@chinamobile. com) - Service: Lin Meng (menglin@chinamobile. com) 6
Discussion Points • Workflow Clarification • Papyrus Model Maintenance Team • Papyrus Model Repo Creation and Related Issues 7
Papyrus Model Repo Creation and Related Issues • Create a folder (Papyrus) under modelspec repo in modeling project - Owner: Hui Deng • Create sub-folders for sub-models - Owner: sub-model editor • Overseeing Committers - Merge only model editor’s commits to each sub-model folder 8