# Participation Guide
## TEAM PARTICIPATION STEPS
### 1. Join your team on slack
### 2. Introduce Yourself
* Your GADS Track, Your Strengths, Preferred stack
### 3. Team Meeting 01
The team lead will set up your first meeting on google meet
**Meeting Agenda**
:white\_check\_mark: Ideate/Brainstorm on what you will work on (Project Name & Details)
:white\_check\_mark: Create a roadmap of tasks on Github projects, Indicate;
* Tasks
* Timelines
* Individuals responsible
**Share details on your project here -** [**bit.ly/GADSCommunityproject**](http://bit.ly/GADSCommunityproject)
## **Tools, Environments & Setup**
### **Collaboration**
Make use of the following for collaboration with your colleagues
:blue\_circle: **Community Space**
Will be used as the main means of communication, go ahead and introduce yourself to your teammates.
:blue\_circle: **Technical Team Lead (TTL)**
Your team has been assigned a TTL, collaborate to formulate a project and give it a name. That name will also be the name of your repo**.**
:blue\_circle: **Project Development**
Collaborate with your teammates to break down your project’s development into roles. Like you have a TTL, what roles will the others play E.g UI/UX?
:blue\_circle: **Project Features**
Collaborate with your teammates to break down your project’s features into 4 milestones then divide it into 2-week-long sprints. You will have 30 days to work on the project hence 2 sprints.
## Project Management walk-through
Team projects are managed with a roadmap on [GitHub Projects](https://github.com/features/project-management/) which automates workflow and moves assigned tasks from the project’s TODO list all the way to DONE as the team works. DONE tasks are features, bug fixes or chores that have been tested, reviewed ready for production
:asterisk\_symbol: **Open an Issue**
:record\_button: 
\
Issues are created for each feature, bug fix or chore needed to deliver the product roadmap. Open issues move into the TODO
:asterisk\_symbol: **Move it To Do**
:record\_button: 
:asterisk\_symbol: **In Progress**
:record\_button: 
:asterisk\_symbol: **Done**
:record\_button: 
### Delivery Management
:heavy\_check\_mark: Using Git & Github, work is done on feature branches which are created from the develop branch, not the master branch.
:heavy\_check\_mark: Commit messages must be semantic and adhere to the [**conventional commits**](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) spec.
:heavy\_check\_mark: A minimum of 3 reviewers (2 team members + the TTL) are required to review & approve a PR before it can be merged back into the develop branch.
:heavy\_check\_mark: Only the TTL can merge code from feature branches into the develop, and from develop to master branches.
:heavy\_check\_mark: This is the [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) process and forms the base of streamlined delivery
:heavy\_check\_mark: The develop branch represents a work-in-progress view of the product and is deployed to a staging server for end-of-sprint demos and engagement. **E.g wakandacart.staging.app.**
:heavy\_check\_mark: The master branch represents a bug-free, working version of the product, deployed to a production environment at specific checkpoints of the roadmap, i.e mid-way into and at the end of the innovation stage. **E.g wakandacart.app.**
## **Product Delivery & Reporting**
:eight\_spoked\_asterisk: **Ideation : WEEK 1 (1ST OCT - 7TH OCT)**
* Use the first meeting to brainstorm and ideate your product
* Share details on your project here: [**bit.ly/GADSCommunityproject**](http://bit.ly/GADSCommunityproject)
:eight\_spoked\_asterisk: **Progress Reporting : WEEK 2 (8TH OCT - 15TH OCT)**
* Weekly Check-in - Your Team lead will schedule a weekly check-in with your mentor for progress reporting.
* Share your Week 2 progress here: [**bit.ly/Communityprojectreport**](http://bit.ly/Communityprojectreport)
:eight\_spoked\_asterisk: **Progress Reporting : WEEK 3 (16TH OCT - 23RD OCT)**
* Weekly Check-in, Your Team lead will schedule a weekly check-in with your mentor for progress reporting.
* Share your Week 3 progress here**:** [**bit.ly/Communityprojectreport**](http://bit.ly/Communityprojectreport)
:eight\_spoked\_asterisk: **Final Reporting : WEEK 4 (24TH OCT - 30TH OCT)**
* Weekly Check-in, Your Team lead will schedule a weekly check-in with your final product.
* Share your Final progress here **-** [**http://bit.ly/GADSCommunityfinalreport**](http://bit.ly/GADSCommunityfinalreport)
## **Individual Participation**
:asterisk\_symbol: **All of the above listed items apply to individual participants**
* An individual participant will take ownership of their project and report on their progress.
:asterisk\_symbol: **Mentorship**
* You will be assigned a team on mentors and Program Assistants who will be readily available to support you on slack.
\
\
\
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://alcwithgoogle.gitbook.io/gads-2022/community-projects/participation-guide.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.