jaskiratsingh2000 / google-season-of-docs Goto Github PK

• Week 2 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

• Week 5 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

• Week 7 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

While I was applying to the GSoD under CHAOSS back in the month of May, I had made a fair research around the metric system on the CHAOSS community. I was always curious to know that how one can propose the metric and follow the path for its approval.
Taking that into consideration, I planned to write the "Processes for getting approved to be visible on the website" along with the "CHAOSS Metric Committee", and "Useful Resources"

• Week 9 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

• Week 6 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

Terminology would help describe the terms and respective belongings that are used frequently within the CHAOSS community. I will also be including the Terminology usage guidelines like Capitalization, Abbreviations, and Words to Avoid with reasons.

• Read some articles for understanding how to define Terminology
• Explored the website
• Discussion with community members

After making a fair research about the Terminology section. I planned to write the following things within the Community Handbook:

• CHAOSS Specific Terms
  • Open Source Community Health
  • Code Review
  • Open Source Software Metric
  • Metric Release
  • Focus Area
  • CHAOSScon
  • CHAOSScast
  • CHAOSSblog
  • CHAOSStube
  • CHAOSSweekly
  • Charter
• CHAOSS Committees
  • CHAOSS Project
  • Contributor
  • Organization
  • Community
  • Community members
  • Core Contributors
  • Maintainers
  • Working Groups
  • Governance Board
  • Event Attendee
  • CHAOSScon Organizing Committee Member
  • CHAOSS Metric Release Collaborator
  • Mailing List Moderator
  • CoC Enforcement Team Member
  • Twitter Manager
• CHAOSS Community Working Groups Terminology
  • Common Metric
  • Diversity & Inclusion
  • Evolution
  • Risk
  • Value
  • Grimoirelab
  • Augur
  • Cregit
  • Application Ecosystem
  • Diversity&Inclusion Badging
• CHAOSS Community Mentorship Terminology
  • Organization Administrators
  • Mentors
  • Mentee/Student
  • CHAOSS Mentorship Alumni

• Week 13 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

• Week 1 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

After making fair research on the "Design Workflow" I wrote the following things under this specific page:

• Our Process - which follows general query system that one use to overcome any design problem
• Ways of Achieving
  • Added a design(made by me)
  • Explaned the different steps

Design is very important for every community as it helps us to know the basic design principle and the workflow of the community.
In order to write this specific page, I tried researching out the following things:

• Explored the CHAOSS community website
• Read articles online that defines design principles
• Understanding the other community design pages

Outreach plays a vital role for any open source community/project. Keeping this thing into consideration I planned to write the Outreach Guidelines inside the community-handbook.
I wrote different ways to get involved with the outreach contribution:

• Writing Blog Post
• Social Media
• Merchandise
• Organize Conferences and Meetups

• Week 4 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

• Week 8 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

• Exploring the already existing community handbook on the GitHub and understood the various insights into it
• Talk with the CHAOSS community members and discussing on what "Values" being lived out within the community
• Asked for the references supporting any values that being lived out.

I planned to write the Google Summer of Code section for the CHAOSS community as CHAOSS has been participating for many years. So there should be the way for newcomers and existing contributors to understand the CHAOSS's participation in the Google Summer of Code program

• Explored the Google Summer of Code website
• Explored the CHAOSS previous years project
• Explored the governance of the CHAOSS on the Github which contains the directory of GSoC
• Discussion with the community members

After doing fair research around the CHAOSS community guidelines, I drafted them on the GitBook platform and the Google Docs.
These are the following things I wrote as headlines:

• Be welcoming and open-minded
• be honest
• Be respectful
• be collaborative
• be inclusive
• Be focused
• Be mindful and stay on topic
• Share the love
• What is not allowed?
• What happens if someone breaks the rule?

Link to GitBook
Link to Google Doc( which is being used for feedback and improvements)

Working Groups are the group of people leaving various groups under the community whose goal is to refine the metrics and to work with software implementations. The workgroups are built around the four categories of metrics that CHAOSS has identified.
Following things required:

• Exploring the website and understood the various insights about the Working Group
• Exploring the Github repositories of Working groups
• Talk with the CHAOSS community members and discussing the requirements to be written for community handbook under the working group's sections
• Asking for the references supporting the context

I planned to write the Design Workflow for the CHAOSS community. After making a bit of research I tried to understand the workflows aim.

• Explore the website
• Read Articles
• Understand the other community's flows

Organize meetings with the core community member in order to understand their background with CHAOSS and CHAOSS history.

Georg provided me the suggestion to mention the goals for each week so that it is easy to compare my progress.

Wrote the Terminology Section within the Gitbook.
Link: https://chaoss-project.gitbook.io/community-handbook/terminology-usage

After making good research for this page. I figured out the following things to mention on the page:

• CHAOSS Logo
• What is CHAOSS design?
• What are we trying to achieve?
• How you can contribute?

Link to GitBook

After reading the articles, I started writing the following things:

• What leadership means to the CHAOSS community?
• Why it is important for us?

After making me the fair knowledge on the Roadmap, I wrote about that within the gitbook https://handbook.chaoss.community/community-handbook/about/roadmap

After making a fair research about the "Documentation Guidelines" I wrote the basic understanding/requirements for contributing in documentation under CHAOSS. The page can be found here(https://handbook.chaoss.community/community-handbook/documentation).

I also tried to explain the basic workflow to follow by taking GitHub into consideration. The link to the page can be found here(https://handbook.chaoss.community/community-handbook/documentation#getting-started)

• Exploring the website and understood the various insights about the ethics being followed in the CHAOSS community
• Talk with the CHAOSS community members and discussing on what "Guidelines" to draft
• Asked for the references supporting any values for the guidlines that being lived out.

Wrote about the General FAQ which usually people come across inside the CHAOSS community. All the content can be found on this page https://handbook.chaoss.community/community-handbook/about/general-faq

• Week 3 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter and LinkedIn

I planned to write the Outreachy section for the CHAOSS community as CHAOSS has been participating for many years. So there should be the way for newcomers and existing contributors to understand the CHAOSS's participation in the Outreachy program

• Explored the Outreachy website
• Explored the CHAOSS previous years project
• Explored the governance of the CHAOSS on the Github which contains the directory of Outreachy
• Discussion with the community members

after making fair research and understanding the Working Groups, I drafted them into the GitBook and the Google Doc
Following are the headlines I used and prepared a context for them:

• What is the Working Group?
• Types of CHAOSS Working Groups
• Who all can participate?
• How to define any new focus area of metrics inside any working group?
• What is the workflow and culture inside the working groups?

Link to GitBook page
Link to Google Doc(for improvements and feedback)

• Week 11 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

I planned to write the Google Season of Docs section for the CHAOSS community as CHAOSS has been participating for many years. So there should be the way for newcomers and existing contributors to understand the CHAOSS's participation in the Google Season of Docs program

• Explored the Google Season of Docs website
• Explored the CHAOSS previous years project
• Explored the governance of the CHAOSS on the Github which contains the directory of GSoD
• Discussion with the community members

• Set up the GSoD Project Tracker
• Set up blogs for posting a weekly blog posts
• Discuss and schedule the meeting timings
• Set up the technical writing platform

After receiving inputs from the CHAOSS community members through the mailing list. I drafted the following things in the GitBook platform:

• Sustainability
• Openness
• Transparency
• Diversity, Inclusion & Belonging
• Consistency
• Merit
• Trust
• Utility

Link to GitBook
Link to Google Doc( which is being used for feedback and improvements)

• Week 12 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

• Read some articles
• Explored the website
• Discussing with community memebers

https://handbook.chaoss.community/community-handbook/contributing/design/design-contribution

As mentioned by Georg, I have synced up the repository of the previous community handbook with the new on the gitbook. I have to announce the new link on the mailing list of the CHAOSS

• Week 10 Blog Post
• Scrum Documentation
• jaskiratsingh2000/Google-Season-of-Docs repository updation
• Sharing about progress on Twitter

For any open source community, it is very important to outline the contribution guidelines required for a different field. So here by I have drafted the contribution guidelines for the design.
I have tried to explain the following things:

• Things you need to follow
• Different Design Contribution
• Getting Started

Link to gitbook

This section will give an overview of how one can get involved with the CHAOSS community as a developer.
I planned to explore the following things in order to figure out what to write:

• CHAOSS website defining projects
• GrimoireLab project guidelines
• Augur project guidelines
• Cregit project guidelines
• reading the CONTRIBUTING.md

Roadmap is important for the CHAOSS project as they are working on many aspects. I would be writing the specific targets and goals of the CHAOSS Community in the Roadmap Section of the gitbook.

• Read some articles for understanding how to define Terminology
• Explored the website
• Discussion with community members