Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Commonalities repository structure #35

Closed
T-sm opened this issue May 2, 2022 · 2 comments
Closed

Commonalities repository structure #35

T-sm opened this issue May 2, 2022 · 2 comments
Assignees
Milestone

Comments

@T-sm
Copy link
Contributor

T-sm commented May 2, 2022

As proposed for Camara Governance in camaraproject/Governance#47:

We should have 4 subfolders (contributions, working, deliverables, supporting documents) and describe the process in the ProjectStructureAndRoles file:

  • All contributions have to be made only in the contributions subfolder
  • Work in progress has to be done only in the working subfolder
  • If decided by the maintainers that a new release can be published then the files can be moved to the subfolder deliverables
  • documents from outside which are needed for the work have to be saved in the supporting documents subfolder
@T-sm T-sm changed the title Project structure and Roles, handling of repositories #47 Commonalities repository structure May 2, 2022
@T-sm T-sm self-assigned this May 2, 2022
@T-sm T-sm added this to the milestone #2 milestone May 2, 2022
@T-sm
Copy link
Contributor Author

T-sm commented Jun 1, 2022

UPDATE - please note:
Steering Committee voted to use branches instead of different sub directories. New section will be added to ProjectStructureAndRoles.md in Governance's repo with a description how branches shall be used to reflect the status of an artefact.
The Commonalities (and other workgroups) will then follow this guidance.

@T-sm
Copy link
Contributor Author

T-sm commented Jul 12, 2022

Created new branches as requested in the WorkingGroups repo.
Published a draft branching how-to tutorial under the WIP branch.

@T-sm T-sm closed this as completed Jul 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant