🚀 Welcome to the home of the Hoodie Editorial Team! 🚀
What is Hoodie?
Hoodie is a global, inclusive community built around supporting the open source software development effort of enabling (and empowering) folks to be able to build applications for the web. It accomplishes this by serving as a complete backend for your apps; it works immediately “out-of-the-box”: develop your frontend code, plug it into Hoodie’s frontend-friendly API and your app is ready.
Hoodie can refer to both the software development project, and the broader community. For more information about both, visit hood.ie. 🐶
Open source software (commonly abbreviated as OSS) is computer software with its source code made available with a license in which the copyright holder provides the rights to study, change, and distribute the software to anyone and for any purpose. Open source software may be developed in a collaborative public manner, for example, by hosting code on GitHub and collaborative discussion on Slack and IRC.
Click here for more information on open source and open source culture, and here’s a helpful list of frequently asked questions.
Hoodie is an open source project and community “beyond software.” Our team strongly believes that open source, an integral component of modern technology, is changing the way people collaborate and create, and that extends far beyond the source code.
Hoodie is built by an amazing and dedicated community consisting of developers and non-coding experts. It relies on strong values like diversity, empowerment and decentralisation. At its core Hoodie exists to empower people and make web development easier and more accessible to a wide range of people.
We require all participation within the Hoodie project and community to act according to a Code of Conduct. We ask you to follow these guidelines which help steer our interactions and strive to keep Hoodie a positive, growing project and community and help us provide and ensure a safe environment for everyone.
The Editorial Team is one of many talented teams that contributes to Hoodie’s success. Our primary focus is Hoodies’ communication with the wider community. We want to keep community members up to date with what we are doing but also showcase it to everyone who has used/is using/wants to use Hoodie for their project. We want to make Hoodie as open as possible with their process and act as a source of inspiration to the larger Open Source community.
Read our official Mission Statement here.
- Plan and write blog posts on or around Hoodie, Hoodie releases, side projects, TGIF, community member profiles, conference and meetup recaps, etc. 📝
- Solicit and curate contributions to our blog from the larger community. 🔎
- Plan and manage our Twitter account, announce new content, help funnel support requests to the engineering team.
- Add pictures of animals in clothing to our Tumblr 🐶 👕.
- General ideas and suggestions for other ways to support Hoodie!
If you already have an idea of what you would like to do please visit the Issues section of this repository. The Issues section is where we keep track of potential editorial contributions, requests for help, and general suggestions.
Here are some of the issues we are working on 👉 
When claiming a task please do the following:
- Find a task with the green
help wantedlabel - Claim this issue (
comment on the issue or assign yourself) - Remove
readylabel, addin progresslabel - If possible, give an indication of the timeline
☺️
If you are brand new to Hoodie check out our contribution guide. We’re looking for people of all sorts, so don’t be afraid to get involved. If you’re passionate about contributing to a great community, we want you! 💎
If you are brand new to open source (including GitHub) first, welcome! 🎉 If you haven’t checked it out yet, opensource.com has some very helpful introductory resources that will give you a good understanding of the premise of open source and its ecosystem.
To be a Hoodie contributor, you will need a GitHub account (which is free for open source), sign up here. To get familar with GitHub as an online tool, they have created several tutorials which you can find via GitHub Guides.
You will also need to know Markdown, a text-to-HTML conversion tool for web writers. GitHub provides a Markdown tutorial, and Daring Fireball has a particular thorough resource on Markdown Syntax.
Please be assured you will not have to have any prior knowledge of code or development to be a Hoodie contributor, especially within the Editorial team.
The way in which the Editorial team uses GitHub is a bit different from other areas on the Hoodie team.
This repository (or collection) serves as the source of truth for the Editorial team. We use the repository in two ways:
- Documentation of processes and resources (such as our style guide, or templates for types of reoccuring writing contributions)
- Idea capturing of all editorial contributions through the Issues section of this repository
We do not publish anything live to the externally facing websites from this repository. This is a safe place to learn, ask questions, and make mistakes. So breathe easy.
Some GitHub basics
- Contributing to Open Source on GitHub
- Mastering Markdown
- Mastering Issues
- Understanding the GitHub Flow
If you enjoyed contributing a first time to Hoodie, we’d love to have you onboard. 🐶 See the Contribution Guide for the overall project at hood.ie/contribute. Another great way to determine if you’d like to continue on the project is to see the Hoodie project goals and also review the project initiatives, which are areas of the project supported across the entire team.
Once you have made a contribution via GitHub (completing an issue, mergine a PR (pull request), etc.) we would like to invite you to be a collaborator on the Hoodie GitHub repository. Please note, this is not an automated process, and requires one of the core maintainers to invite you – so if you are reading this and have not yet been invited, please get ahold of one of the folks mentioned below.
Becoming a collaborator simply means that you gain push access to projects across the repository. We ask that until you have become a regular collaborator, that you still follow a common review process typically referred to as using pull requests.
The review process is begun by submitting a pull request back to the original version (branch) of a repository. Many, many, many amazing tutorials have been created about the pull request process so I won’t recap that here, but instead point you to the GitHub tutorial.
For Hoodie, pull requests need to be approved by two other contributors, before being merged into the project.
You’ve have made your first contribution to the Hoodie project! 🎉
You’ve been added as a collaborator! 😎
Now, what’s next?
This grey area of onboarding is one our team is looking to improve across the project so first – please give as much feedback about this as possible (you can email Jenn right here) but know that it’s an area we want to make better.
There is a Next steps label in the Issues section for editorial contributions considered to be a little more involved than what we’d ask first time contributors to take on. Check those out to see if anything resonates.
If not, please feel free, empowered, and highly valued to make suggestions for contributions you’d like to see on the project. Your brand new and completely unique perspective is incredibly important to shaping this project.
Please join the Hoodie project Slack chat, because a lot of our discussion and reviewing happens in that place. It’s also a great place to ask questions, meet other contributors, and find out the latest goings on within the project. There’s a specific #editorial channel there you’ll want to join.
Our wiki is an ongoing effort to build resources making it easier for folks to contribute. Some resources you can find there include our mission statement, a glossary of common terms, and our language style guide.
Check out our schedule of blog posts for the coming month (find the appropriate month tab at the bottom of the screen) to see what posts are coming up, and what ongoing contributions (i.e., weekly blog posts) are available to be claimed.
It cannot be stressed enough that our community is based on mutual respect, tolerance, and encouragement. So please read the Code of Conduct and familarize yourself with the dos and don’ts.
A lot of our conversations happen here on GitHub in the issue tracker, or in the #editorial channel in Slack.
If there’s something you’d like to talk about that you don’t think fits in either of those places, or you’d just like to have a more private conversation; please feel free to contact the following people:
- 😎 Jenn Turner - GitHub, Twitter, mailto:[email protected]
- 🐶 Jan Lehnardt - GitHub, Twitter, mailto:[email protected]
- 💻 Charlotte Spencer - GitHub, Twitter, mailto:[email protected]