Conduct. Create a CONDUCT.md file. Use the Contributor Covenant Code
of Conduct template and modify the places that need updating (e.g., who to contact). Add to it
language to address:
● Decisions (How will they be made? Majority, consensus, other?)
● Attendance (What are your expectations for the frequency and type of attendance?;
What are legitimate reasons for missing? What do missing members have to do to make
up for missed meetings)
● Assignments (How will assignments be made? How will the group deal with members
who do not complete (or poorly complete assignments?)
● Participation (How will you communicate and share information; How will you ensure full
participation of everyone? How will you honor member strengths and interests)?
● Meeting Times and Locations/Mediums (How will you decide on locations and times that
suit all members)?
● Agenda and Minutes /Notes (Who will take them how will they be shared?)
● Promptness (What do you expect and how will you handle lateness?)
● Conversational Courtesies (How will the team encourage and reinforce active listening,
sharing of the airtime, tangents, respectful dialogue, etc )
● Enforcement/ Feedback (How will the team enforce its own rules? How do individuals
prefer to give and receive feedback?)
Have every group member upload an image of their written signature to the src folder and use
Github Markdown language to embed the signature at the end of the CONDUCT.md file. You
must commit your own signature to the file (i.e. show in the commit history).
Place your team’s CONTDUCT.md file at the top level of your repo. Add markdown to your
team’s README.md file with the Contributor Covenant label.
Conduct. Create a CONDUCT.md file. Use the Contributor Covenant Code of Conduct template and modify the places that need updating (e.g., who to contact). Add to it language to address: ● Decisions (How will they be made? Majority, consensus, other?) ● Attendance (What are your expectations for the frequency and type of attendance?; What are legitimate reasons for missing? What do missing members have to do to make up for missed meetings) ● Assignments (How will assignments be made? How will the group deal with members who do not complete (or poorly complete assignments?) ● Participation (How will you communicate and share information; How will you ensure full participation of everyone? How will you honor member strengths and interests)? ● Meeting Times and Locations/Mediums (How will you decide on locations and times that suit all members)? ● Agenda and Minutes /Notes (Who will take them how will they be shared?)
● Promptness (What do you expect and how will you handle lateness?) ● Conversational Courtesies (How will the team encourage and reinforce active listening, sharing of the airtime, tangents, respectful dialogue, etc ) ● Enforcement/ Feedback (How will the team enforce its own rules? How do individuals prefer to give and receive feedback?) Have every group member upload an image of their written signature to the src folder and use Github Markdown language to embed the signature at the end of the CONDUCT.md file. You must commit your own signature to the file (i.e. show in the commit history). Place your team’s CONTDUCT.md file at the top level of your repo. Add markdown to your team’s README.md file with the Contributor Covenant label.