Any product, from an ERP system to a CRM system to an accounting package, will require some set of UI and logic features to fully take advantage of being baselined. In particular, users of the product will need to know the difference between a baselined and non-baselined record. Users should be either alerted when about to change a baselined record or prevented from doing it without admin permissions. A baselined product, therefore, will need a param like "isBaselined" or other and a "cookbook" to instruct on ways to utilize the parameter.
Some systems like SAP and MSFT Dynamics are highly configurable. That is why VARs have been able to create "baselined" projects without these core platforms altering their core product. But imagine a product like Quickbooks. If and when such a product wants to participate in baselined Workflows, it will need...a cookbook.
Activity: Brainstorm on what a product cookbook could look look like and what its initial "recipes" ought to be.
Impact on the Baseline Community
A healthy open source community is one that makes it easy and attractive to utilize the technology. We want to see lots of products in 2021 and 2022 starting to announce that they are "baselined". Assertion: The better the cookbook, the more products will become baselined, and the sooner they will do it.
Acceptance criteria and must have scope
For the Summit, a high level cookbook chapter list, an introduction, and a three "recipes" that instruct a product in things like locking records or initiating a baseline step would be ideal.
Timeline
2021 will need the cookbook.
Background on Epics, Issues, Checkboxes (aka, Epics, Stories, Tasks)
After you start breaking this master epic up into a set of Issues (sub-epics, stories, tasks, etc), you might consider creating a Project in Github to make it easy for your group to have a single Kanban board for just this work. The Github projects tab in any given repo will allow only Issues from that repo, but if you create one here, you will be able to set up a project that can compose Issues from any of the baseline repos, including the core /baseline repo and the planning /baseline-roadmap repo.
Project Description
Any product, from an ERP system to a CRM system to an accounting package, will require some set of UI and logic features to fully take advantage of being baselined. In particular, users of the product will need to know the difference between a baselined and non-baselined record. Users should be either alerted when about to change a baselined record or prevented from doing it without admin permissions. A baselined product, therefore, will need a param like "isBaselined" or other and a "cookbook" to instruct on ways to utilize the parameter.
Some systems like SAP and MSFT Dynamics are highly configurable. That is why VARs have been able to create "baselined" projects without these core platforms altering their core product. But imagine a product like Quickbooks. If and when such a product wants to participate in baselined Workflows, it will need...a cookbook.
Activity: Brainstorm on what a product cookbook could look look like and what its initial "recipes" ought to be.
Impact on the Baseline Community
A healthy open source community is one that makes it easy and attractive to utilize the technology. We want to see lots of products in 2021 and 2022 starting to announce that they are "baselined". Assertion: The better the cookbook, the more products will become baselined, and the sooner they will do it.
Acceptance criteria and must have scope
For the Summit, a high level cookbook chapter list, an introduction, and a three "recipes" that instruct a product in things like locking records or initiating a baseline step would be ideal.
Timeline
2021 will need the cookbook.
Background on Epics, Issues, Checkboxes (aka, Epics, Stories, Tasks)
After you start breaking this master epic up into a set of Issues (sub-epics, stories, tasks, etc), you might consider creating a Project in Github to make it easy for your group to have a single Kanban board for just this work. The Github projects tab in any given repo will allow only Issues from that repo, but if you create one here, you will be able to set up a project that can compose Issues from any of the baseline repos, including the core /baseline repo and the planning /baseline-roadmap repo.