jaskiratsingh2000 / google-season-of-docs Goto Github PK
View Code? Open in Web Editor NEWProject Tracker for Google Season of Docs 2020: Creating a @chaoss Community-wide handbook
License: MIT License
Project Tracker for Google Season of Docs 2020: Creating a @chaoss Community-wide handbook
License: MIT License
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"
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.
After making a fair research about the Terminology section. I planned to write the following things within the Community Handbook:
After making fair research on the "Design Workflow" I wrote the following things under this specific page:
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:
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:
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
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:
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:
I planned to write the Design Workflow for the CHAOSS community. After making a bit of research I tried to understand the workflows aim.
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:
After reading the articles, I started writing the following things:
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)
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
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
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:
Link to GitBook page
Link to Google Doc(for improvements and feedback)
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
After receiving inputs from the CHAOSS community members through the mailing list. I drafted the following things in the GitBook platform:
Link to GitBook
Link to Google Doc( which is being used for feedback and improvements)
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
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:
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:
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.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.