techinc-coc-commitee/CoC_Commitee_Documentation
5
1
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity

improve spelling

Browse source
This commit is contained in:
Li0n 2023-06-30 01:02:43 +02:00
parent bd3d4fb15b
commit 1df1203bcb
1 changed files with 29 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

57
meeting-notes/meeting notes 2023-06-28.md
View file

@ -1,4 +1,4 @@
# Meeting 28 June - Conduct Commiteee
# Meeting 28 June 2023 - Conduct Committee
Attendees:
@ -16,9 +16,9 @@ Agenda:
# Onboarding to Git
* Registration - Code.techinc.nl -Onboarding CoC Commitee [X]
* Registration - Code.techinc.nl -Onboarding CoC Committee [X]
* Ensure Everyone Present is able to login
* Create CoC repository and ensure its public [X]
* Create CoC repository and ensure it's public [X]
* Onboard Kai []
* Define a Structure
@ -26,50 +26,50 @@ Agenda:
# Git Structure
## Repositories:
* CoC: used for all drafts and the released COC
* CoC Commitee Documentation
* CoC: used for all drafts and the released CoC
* CoC Committee Documentation
## CoC:
### Branches
- Main: Used for the production, reviewed and ALV voted version of the C0C
- Main: Used for the production, reviewed and ALV voted version of the CoC
- Revision: Drafts that have been voted by all members of the CoC Commitee (we think it's ready for board review)
- Draft
- Per Member of Commitee An Editorial Branch eg coc-mattronix-drafts
- Per Member of Committee an Editorial Branch eg coc-mattronix-drafts
### Pull Requests
#### Commitee members
- From member Branch to Drafts (approved by majority)
- From Draft to Revision (approved by majority)
- From Revisions to Main (after approval at ALV)
#### Non-Commitee Members
- Pull Request or emails to conduct@techinc.nl
- Pull Request or email to conduct@techinc.nl
## CoC Commitee Documentation
### Branches
- Main
- For notes and usful documents
- For notes and useful documents
- Folder for meeting notes
### Pull Requests
- per change merge by self always merged before or at meeting
- per change merge by self. always merged before or at meeting
#### Commitee members
- From member Branch to Drafts (approved by majority)
- From Draft to Revision (approved by majority)
- From Revsions to Main (after approval at ALV)
# Action Points from Workgroup
* Review the Existing CoC and analyse it for anything that may be useful to the goals of the CoC committee.
* Analyse why the existing CoC is not widely used, known or adopted.
* Draft the new CoC
* establish a process to submit edits and changes
* Review the Existing dispute Commitee processes
* Draft new process for Dispute Commitee
* Review the Existing dispute Committee processes
* Draft new process for Dispute Committee
## Review the Existing CoC and analyse it for anything that may be useful to the goals of the CoC committee
Consenses 3/4 no CoC defined or in draft, we have searched the wiki, we have asked the board. The best we could find is a dispute commitee.
Consensus by 3/4 present members: no CoC defined or in draft, we have searched the wiki, we have asked the board. The best we could find is a dispute procedure.
[19:56] <T_I_M> Justa! vraagje, we hebben gezocht naar de huidige C.O.C maar geen van ons is het gelukt om deze te vinden. Heb jij een link naar de huidige C.O.C?
[19:57] <justa> ja
@ -88,14 +88,14 @@ Consenses 3/4 no CoC defined or in draft, we have searched the wiki, we have ask
Because it does not exist.
## Draft the new CoC
* Interview Drew on issues he had and possible improvements on CoC and where the current problems (Vote at next meeting)
* Establish outline of CoC Document, in this case i think we should review other CoC's from other orginizations and hackerspaces pick one we all each like and review them all for simulatires and usful ideas.
* Interview Drew on what the issues are that he ran into involving the CoC and dispute process (Vote at next meeting)
* Establish outline of CoC Document, in this case I think we should review other CoC's from other orginizations and hackerspaces pick one we all each like and review them all for similarities and useful ideas.
* All information reviewed and used should be shared on the documentation repository ahead of future meetings and referenced in draft phase.
### Process
1. Review Existing CoC's from other organizations and our own drafts (store and share existing CoC's on documentation wiki)
2. Establish outline of CoC
3. Weekly/Biweekly Drafting of section or sections by each member of the CoC Comitee
3. Weekly/Biweekly Drafting of section or sections by each member of the CoC Committee
4. review of existing CoC's Sections
5. review of sections and edits
6. Vote and Merge of sections and edits
@ -104,28 +104,28 @@ Because it does not exist.
## establish a process to submit edits and changes
### Four Phase Philosophy:
* Editiorial Phase: each member of the commitee reviews external information, information from other orginzations, and creates drafts they think fit each section or outline for comparison
* Draft Phase: Group meeting to review edits from the editorial phase, the goal is to vote in a mix of all the edits this may take multiple meetings per section.
* Techinc Member Draft Phase: Members of techinc review drafts at any time they please and submit changes or pull requests for review and vote by the CoC Commitee.
* Editiorial Phase: each member of the committee reviews external information, information from other organizations, and creates drafts they think fit each section or outline for comparison.
* Draft Phase: Group meeting to review edits from the editorial phase, the goal is to vote in a mix of all the edits. This may take multiple meetings per section.
* Techinc Member Draft Phase: Members of Techinc review drafts at any time they please and submit changes or pull requests for review and vote by the CoC Commitee.
* Revision Phase: After majority vote of the CoC Commitee we submit our request for the next ALV to vote in the live CoC Document, we notify everyone of the review and allow extension of the Member Draft Phase until 1 week before the ALV.
#### Editorial Phase to Draft
- From CoC Committe member Branch to Drafts (approved by majority of the CoC Commitee)
- From CoC Committee member Branch to Drafts (approved by majority of the CoC Commitee)
### Draft Phase && Techinc Member Draft Phase
- Accept input from Techinc members
- Accept voted edits from Techinc members
- From Draft to Revision (approved by majority)
-
#### Revision Phase
- From Revsions to Main (after approval at ALV)
## Review the Existing dispute Commitee processes
to review in the future focus is CoC at this time
## Review the Existing dispute Committee processes
to review in the future. the focus is CoC at this time.
## Draft new process for Dispute Commitee
to review in the future focus is CoC at this time
to review in the future. the focus is CoC at this time.
# Designation of Roles
* CoC Committee Member (Member of TechInc who is not part of the board): Li0n, Tim, Arjan, Kei, Mattronix
@ -135,7 +135,7 @@ to review in the future focus is CoC at this time
# Action Points Next Meeting
1. Vote on: Interview Drew on issues he had and possible improvements on CoC and where the current problems (Vote at next meeting) []
1. Vote on: Interview Drew on what the issues are that he ran into involving the CoC and dispute process (Vote at next meeting) []
2. Homework: Review the following CoC's before next meeting
* https://www.tog.ie/code-of-conduct/
@ -146,3 +146,4 @@ to review in the future focus is CoC at this time
3. Homework: Find other CoC's you think are interesting
# Next Meeting Date July 12th @ 19:00
https://wiki.techinc.nl/CoC_Committee_Meeting_2023-07-12