Part of hoodiehq/hood.ie#234

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

In preparation for the Camp Release we are trying to update the hood.ie site. This specific writing task involves adding content to the Hoodie “get help” page to flesh out the ways folks can get assistance or encouragement as they run into blockers or issues when contributing to the project.

• Claim this issue (@rubymorillo)
• Contact @gr2m or @janl and conduct a brief interview for context and process pointers.
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

I can't remember if I saw discussion on this in Slack or not, but have we determined criteria for closing issues and pull requests?

I know there's a method for contributing to the Hoodie project outlined in the CONTRIBUTING doc here for the primary Hoodie repo so I'm proposing that we use that to start.

Barring any objection in the next 72 hours, which I recall being an appropriate amount of time for issues to breath ☺️, I'm going to begin working through the repo.

Hoodie couldn't exist without a lot of amazing projects & people out there. I'd love to start a series where we introduce a project we rely on, or simply love, and not introduce the project and how we use it at Hoodie, but especially the people behind it.

Here’s a list of projects that come to mind, I'll keep them updated.

• API Blueprint / Apiary
• browserify
• CouchDB
• Ember.js
• Github
• greenkeeper.io
• hapi
• JSON API
• JSConf
• npm
• PouchDB
• semantic-release
• tap / tape / nyc / istanbul / coveralls
• Travis
• Your First PR

If people agree that this is an idea worth exploring, I'm happy to take ownership of this one and figure out how to make it work, without being a writer myself :D

The Proposal

Let's write a blog post on our editorial team, to share the good news that we now exist! Officially started on the 21st of November with an awesome Google Hangout full of people. Talk about what our goal is, how we're going to start the process (documentation, meetings, slack) and what areas we are going to cover. Talk about how we want more people and ask for one-off ideas?

In the process of welcoming contributors / maintainers / core team and whatnot, we should make sure to follow these people on twitter with @hoodiehq AND tweet to welcome them!

@gr2m should write up his experiences with running two Your First PR / Hoodie hands-on workshops in New York.

@gr2m: I know you don’t consider yourself a strong writer and I’m more than happy to help, maybe you can start with an outline, and a few paraphrased bullet points per paragraph and I turn it into prose?

Hi @espy 😃 👋

We'd like to feature you in our "Meet the Hoodies" series. We're working on this series to get the editorial process right and to introduce/ re-introduce the amazing people behind Hoodie. Kindly respond to the questions below and submit a quirky photo to go with the final blog post:

1. What's your favorite animal?
2. What's your role / what have you contributed to Hoodie?
3. What's your favorite use of Hoodie in the wild?
4. What in your opinion makes the Hoodie project unique and interesting?
5. What advice do you have for aspiring Hoodie contributors?

Issue #14

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

Instead of having the TGIF post be a huge compilation of interesting/fun links to read and Hoodie news, we're going to split up the two posts so that we're posting more regularly to the blog and giving each equally important updates their due.

The person responsible for this task will work with @gr2m to create a template to be used on a recurring basis. We'd appreciate you being involved for a few of the posts, but if you'd just like to try your hand at the first one that works too. ☺️

• Claim this issue (assign yourself to this issue or comment below)
• Review TGIF 73 and TGIF 74 to familiarize yourself with the types of Hoodieverse news we want to call out for these weekly posts.
• Contact @gr2m to collaborate on a draft.
• Submit to @renrutnnej @gr2m or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Hello Editorialites ✨

I would like to suggest that we make the contribution process a tad clearer and more accessible for folks to jump in on.

Right now as it stands, the process to get something on the blog from suggestion to publication looks like this:

• Suggest blog post topic in hoodiehq/editorial issues
• Upon approval author creates text in their preferred format
• Text is formatted into markdown file that goes to hoodiehq/editorial/blog-posts
• Markdown file gets copied into `hoodiehq/hood.ie/_drafts
• Markdown file gets reviewed and converted to hoodiehq/hood.ie_/posts
• Markdown file gets pushed to master and published live 🎉

I would like to suggest that we eliminate the double work of having a hoodiehq/editorial/blog-posts file in this repo and make follow this process:

• Suggest blog post topic in hoodiehq/editorial issues
• After person claims issue they follow the process outlined in hoodiehq/hood.ie README: https://github.com/hoodiehq/hood.ie#blog

I know there are plans to create an in-depth "How to" guide and I am not suggesting we skip that, I encourage that effort as a means to make the process clearer.

I do think we should streamline the process in general.

Hi everyone!

I wrote a post about some of the tech behind minutes.io, one of our company's projects built on hoodie. We'd like to get that referenced in the offline first-newsletter that we do, which, somewhat problematically, goes out on Wednesday morning. So there's not a lot of time for a long review process, that said, I've already had two people take a look, so some eyes have already been over it.

Anyway, here it is: hoodiehq/hood.ie#213

Thanks so much!
A

What is your blog post about? Describe it in about one paragraph.

This series will celebrate the Hoodies, our fantastic community of contributors. Each episode will feature one contributor and will involve them answering the below questions and submitting a quirky photo to go with the post:

1. What's your favorite animal?
2. What's your role / what have you contributed to Hoodie?
3. What's your favorite use of Hoodie in the wild?
4. What in your opinion makes the Hoodie project unique and interesting?
5. What advice do you have for aspiring Hoodie contributors?

Approximately how long do you think the post will be?

Each post will be a maximum of 1000 words depending on how verbose the contributor is 😄

Approximately how long do you think it will take you to write this post?

2 days for each contributor

Do you think your post could make use of any illustrations or photographs?

Yes! Photographs of the featured Hoodie and an animal muse would be cool 😁

Do you have any links to previous writing?

No.

Where else can we find you on the internet? (e.g. your blog, Tumblr, Medium, Twitter, etc.)

https://twitter.com/schisepo

Anything else you want to tell us?

This will be a fantastic series 🚀

I updated the team-roles.md file with descriptions in #23. In addition to adding the descriptions, I think we need to define a formal process in which contributors are added to the Editorials team.

Having this early on makes the transition from one (or few) contributor to many slide through with much less friction than when it is developed later.

Tasks for getting this done:

• Separate file or put in team-roles.md?
• Different path to contributor for each of the defined roles in team-roles.md or a unified path?
• Define what active and contribution mean.
• Link to CoC, CONTRIBUTING.md, and anything else?
• {{other points?}}

The Issue

TGIF (Thank God Its Friday) is a weekly (on.. Friday) blog post that goes out where we show whats been happening with Hoodie (events, speaking etc.) with a focus on cool stuff we like from outside the community. Not everyone knows how to write a TGIF which means we could end up not having one if someone gets sick/tired/doesn't want to do it that week. Never have all the responsibility on one person!

The Solution

Standardise and document the TGIF process so anyone on the Editorial Team can write a TGIF post should they want to.

Examples of what you could teach people to do in the guide:

• What is TGIF
• How should it be structured
• How do I submit it to the website
• Where to find inspiration
• Where to find links
• Links to previous TGIF's

When the issue is considered complete

There is a file (.md, markdown) in this repository on how to write a TGIF post.

As the interest in Hoodie and its editorial grows, I'm sure there'll be a lot of people who'll want to write something for the Hoodie blog. We talked a lot about recurring posts (e.g. TGIF, Meet the Hoodie, cute animal pics), but we should definitely also talk about handling one-offs. I think it's possible that if we leave it open enough, we could have a steady stream of interesting one-off pieces, and it might become sort of a series. (i.e. every X day of the week, a "guest" one-off post is published)

Here are my thoughts on how the process could go:

1. Getting the pitch - I think it makes sense that we keep pitches as open as possible, since we'd all want to give feedback on them. I think the easiest way to do this would be through GitHub issues on a repo (either this one, or a separate one).To make it easier for both the writer pitching an idea, and us as a team reviewing, we could offer a template for pitches. They'd just copy/paste the markdown into an issue, and fill in things like the gist of the article (~1 paragraph), the approximate length, their best guess on how long it would take to write, and anything else the writer wants to add. (To be clear, the writer can be anyone, whether already involved with our editorial team, or a complete newbie.)

2. Reviewing - After the writer has submitted their pitch, members of the editorial team should review it, and offer feedback. The feedback shouldn't necessarily be a yes/no (unless the writer submitted something wildly off-topic. we should document what sort of content we want), but just feedback for the writer to make an even stronger pitch. This feedback/review period should last a few days, to let as many of us as possible give feedback.

3. Approving - Once the feedback period is up, we then have to make the big decision: Do we want this article? As long as the feedback period went well, and the writer is still on board, I'd say that we would want it. To coordinate who does what, I think we can do a pretty simple system: If you feel strongly about the article, you can volunteer for a role for that article. I think the roles could be laid out as the writer, an editor (or multiple editors, depending on the article length/time availability), and "managers." The managers would be responsible for doing things such as:

   • figuring out when the article needs to be done by/when to publish
   • coordinating the social media posts for the article (likely writing them)
   • working with anyone on the technical side to get the post on hood.ie
   • organizing any additional volunteers, such as illustrators, photographers, etc.

   The reason I suggest multiple managers is that there are a lot of tasks there. If someone is able to put in the time commitment for all of the tasks, then they could volunteer themselves for that, but since we don't want someone to burn out, we should encourage people just to manage one portion.

4. Writing - Finally, writing! We should leave this up to the writer as much as possible, but we should encourage them to share openly in their process. Writing in a Google Doc would be nice, since we can see progress whenever, and help edit as they write, but as long as they at least share some a draft or two, I'd say that's good. During the writing process, the manager in charge of scheduling should check in with the writer to make sure they're doing well. We should encourage writers to join our Slack, for easy check-ins.

5. Editing - Once the writer has completed their final draft, they should post it to the issue (or just share a Google Doc, or whatever they prefer), so that the editor(s) can start making suggestions. If the editor is comfortable with it, the editor could convert the post to markdown as well, so we can start getting ready to post it on hood.ie. If not, the manager involved with the "technical" aspects should do it, or work with someone who can. Also, this is when we should start adding any illustrations or photographs to the article. Illustrators/photographers, or the manager in charge, should post their pictures on the issue. During this time, everyone helping with editorial can give feedback as well, even if they aren't an "editor."

6. Posting - The big event! At this point, the final copy should be done, and we should have a PR ready for the hood.ie site. The scheduling manager should have chosen a time to post the article, which is when the PR is merged. From there, we send out the social media posts, and let the writer bask in their new post. 😄 We should give major thanks to the writer, and encourage them to contribute again, whether it be another article, or any other role.

I think this structure works well, since we're delegating specific tasks to people, so they don't have to spending too much time on posts, and won't get burnt out. It also lets a lot of people be a part of an article, which gives us all something to do. The role that probably would have the biggest time commitment would be the scheduling manager, since they would have to work with multiple people to make sure everything is ready for the release of the article. However, with the help of the other managers, it shouldn't be too bad. Ultimately, it's something that'd have to be experimented with, and something we'd get better at the more we do it. I think we can adapt this process for our recurring series as well, mostly for the reviewing and managing parts.

... whew! That was a lot of words. These are, of course, just my ideas, so I'm very open to any feedback. Everything's better when we work on it together! 🎉

Part of hoodiehq/hood.ie#234

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

In preparation for the Camp Release we are trying to update the hood.ie site. This specific writing task involves adding content to the Hoodie community page to update our current contributors list. 🐻

• Claim this issue (@jo-porter)
• Investigate/interview and then write a one-sentence bio for the following folks:
  • Charlotte Spencer @Charlotteis
  • Christoph Witzko @christophwitzko
  • Nick Herr @HipsterBrown
  • Jenn Turner @renrutnnej
  • Julia Simplicio @jsimplicio
  • Patricia Garcia @patriciagarcia
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

We have no documentation on how to submit animals to the tumblr. We should add that. :)

This issues is the first follow-up from the first call we had on November 21st.

The group decided to tackle one small project first to figure out the rest of the process.

The project is: Meet The Hoodies.

Here is the rough idea:

Meet The Hoodies (sing a long to the melody 🎶 of Wheel of Fortune) is a blog series that in each episode celebrates one of the Hoodie community members. Each edition has a somewhat fixed format with maybe three to five questions that everybody gets, along with a photo or any other desired imagery for the person.

The Issue

Right now, there is no plan to run the Meet the Hoodies series. We’d like to change that.

The Solution

Here’s a rough outline of which tasks are needed.

1. Document Meet the Hoodies format, including questions to ask and everything.
2. Divide the production of one episode of Meet the Hoodies into sub-tasks (these are just suggestions, feel free to make your own list):
   • finding a person
   • defining the interview questions
   • coordinating with the interviewee to get answers and a photo or other image
   • review the questions and answers for content and style
   • copy-editing the questions and answers
   • formatting the answers to look like a blog post post
   • creating a pull request to the blog
   • publish the post
   • send tweets about the new post in three or four time-zones around the globe
3. Put the sub-tasks on a schedule.
4. Have people assign themselves to the sub-tasks.
5. Ship! 🚢

Some of this isn’t well-defined yet, and we’ll all work together to figure it out. For example: where do we write down the schedule? I don’t know, maybe this issue, maybe in the wiki. Where do we track the sub-tasks? I’d say we use GitHub issues here for this, but maybe you have a better idea.

When is the issue considered complete

When there is at least one Meet the Hoodies post on the blog and when we have documented the process on how we got there.

Bonus points for having one more more in the pipeline by then.

The Issue

Language is a powerful tool, and it is very easy to wield it badly. In order to be the best Hoodies we can be, lets outline from the start the language we should and shouldn't be using.

The Solution

Create a README or Wiki (thanks @renrutnnej) that acts as a 'Language Styleguide' where we list all the Dos and Don'ts. Topics like pronouns, the attitude and discourse of "Hoodie", how to talk about folk with disabilities (i.e not "The Disabled", but "people with disabilities").

When the issue is considered complete

This will be an ongoing process, so lets consider this complete when we have the Wiki set up and our first draft of guidelines?

This is a starter issue.

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

How to add/edit entries for Wikipedia, as noted here Your first article and Article development.

🐞 The Issue

There's no Wikipedia entry for Hoodie.

🎯 The goal

Create an entry for Hoodie! 🐶

📋 Step by Step

• claim this issue
  comment below. Once claimed we add you as contributor to this repository, so we can assign you to the ticket and you can start checking off the checkboxes below as you progress. We will also replace the ready label with in progress.
• Familiarize yourself with the Wikipedia publication process.
• Write a draft of an article for Hoodie
• Get feedback on the article from the editorial team
• Submit to Wikipedia
• Done 👍 Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Part of hoodiehq/hood.ie#234

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

In preparation for the Camp Release we are trying to update the hood.ie site. This specific writing task involves adding content to the Hoodie Animals page to give readers a better idea of our revolving cast of animal characters. 🐶

• Claim this issue (@annaboodle)
• Write a bio between 200-400 words long.
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

What is your blog post about? Describe it in about one paragraph

The only way to play with the new Hoodie version is to setup https://github.com/hoodiehq/hoodie-app-tracker. But there are no real instructions on how to build your own app with the new Hoodie, and I think it would be nice to have a place where we can send people to who want to play with the latest Hoodie version. A blog post might be a great resource for that. Once it’s outdated, we can update it

Approximately how long do you think the post will be?

I guess it will be a step-by-step kind of blog post like this one on Starter Issues

Approximately how long do you think it will take you to write this post?

1-2h

Do you think your post could make use of any illustrations or photographs?

Yeah something camp related would be nice :) I guess I could reuse the tent from our birthday newsletter

Do you have any links to previous writing?

http://hood.ie/blog/starter-issues.html

Where else can we find you on the internet? (e.g. your blog, Tumblr, Medium, Twitter, etc.)

https://twitter.com/gr2m/

Anything else you want to tell us?

I’m happy to work with someone else on this :)

UPDATE: APRIL 5: @gr2m will try to write the blog post next week and I'm (@rubymorillo) going to help with editing once he's done with his first draft (using Google Docs).

Jan recently wrote about Hoodie’s The (Larger) Hoodie Roadmap

tl;dr The larger milestones (from the code perspective) are targeting:

1. Contributors
2. Developers (Full Stack)
3. UX Developers (Frontend)

I would love to put our heads together and think about how we can improve as the Hoodie community to become more friendly towards new and existing contributors.

The motivation is this: from the code side of Hoodie, we worked very hard in the past year to lower the barrier as much as possible to become a new code contributor. The way we did it is to split up the code into a lot of separate modules, which are all well tested & documented, and interested people can pick issues for one of these modules and work on them, without the necessity to understand how all of Hoodie works. For example, https://github.com/hoodiehq/hoodie-client-log is a little library for easy logging to the browser console. You can use it by itself, it’s self-contained, it just happens to be used by the Hoodie client. And because it’s only a few files with a few lines of code, it’s easy to grasp and to contribute to. And all bugs fixed and features added to it – Hoodie benefits from it automagically.

So.

Hoodie is in a great state to scale in terms of code contributors (and other contributors of course!). Maybe the editorial team has some good ideas how we could use writing / twitter / you name it to try achive the same goal: finding new contributors and become more friendly for contributors in general?

For example, we could write a post for first-time open source contributors, explaining things like git, Github, forking, pull requests, Node etc, that would be helpful for many (JavaScript) open source projects out there, and we could link to the blog post from our starter issues.

Maybe we could show the starter issues right on the http://hood.ie landing page? I’m sure we come up with more ideas once we thing more about it.

Hope this all makes sense :) I’m curious to hear what you think

see #28 (comment)

Hi @Charlotteis 😃 👋

We'd like to feature you in our "Meet the Hoodies" series. We're working on this series to get the editorial process right and to introduce/ re-introduce the amazing people behind Hoodie. Kindly respond to the questions below and submit a quirky photo to go with the final blog post:

1. What's your favorite animal?
2. What's your role / what have you contributed to Hoodie?
3. What's your favorite use of Hoodie in the wild?
4. What in your opinion makes the Hoodie project unique and interesting?
5. What advice do you have for aspiring Hoodie contributors?

Issue #14

@skeskali @remixz @bnb @renrutnnej would any of you be available to test drive the blog process guided by this doc 👉 Our blog process and this document 👉 Submitting a PR to the Hood.ie blog WIP

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

We’ve started a series of brief interviews with some of the Hoodie core contributors. You can see examples of these here:

• Alex Feyerke
• Charlotte Spencer
• Jenn Turner

I’m requesting that someone write up a new interview with Julia Simplicio (@jsimplicio). To claim this task do the following:

• Claim this issue (@pawan92)
• Review the previous posts above.
• Find the Meet the Hoodies sample doc in this repo.
• Contact @jsimplicio to collaborate on a draft.
• Submit to @renrutnnej @gr2m or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

We’ve started a series of brief interviews with some of the Hoodie core contributors. You can see examples of these here:

• Alex Feyerke
• Charlotte Spencer
• Jenn Turner

I’m requesting that someone write up a new interview with Nick Hehr (@HipsterBrown). To claim this task do the following:

• Claim this issue (@pawan92)
• Review the previous posts above.
• Find the Meet the Hoodies sample doc in this repo.
• Contact @HipsterBrown to collaborate on a draft.
• Submit to @renrutnnej @gr2m or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Hello again, everybody.

I just wanted to see what the status of this project was, and where it is going to go from here. It seems to have majorly died down in the past month with lots of open-ended Issues and PRs. Are we still going to actively develop the editorial side of Hoodie? If so, who is going to continue contributing from now on, after the original publicity has faded?

Part of hoodiehq/hood.ie#234

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

In preparation for the Camp Release we are trying to update the hood.ie site. This specific writing task involves adding content to the Hoodie Animals page to give readers a better idea of our revolving cast of animal characters. 🐶

• Claim this issue (@matsieftw)
• Ping us on Twitter or in our Hoodie Chat so we can share an image of our alpaca with you :)
• Write a bio between 200-400 words long.
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

On Tuesday March 15, @janl and @renrutnnej will be on a popular Open Source podcast called FLOSS Weekly to talk about Hoodie! 🎉 🐶

We need a contributor to write a brief synopsis after the show to post on the blog with the link to the podcast with maybe an epic quote from the show or something. ☺️

Or especially if there are links mentioned in the show, it would be great to have a recap post with that information readily available.

To take on this blog post:

• Claim this issue (@sjnorth)
• Review the FLOSS Weekly program at the link above.
• Find the instructions for posting a blog post to the Hoodie blog in the hoodiehq/hood.ie repo here.
• Submit a pull request (PR) as part of the end of the blog process.
• You are done 👏 comment below that your PR is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

The Issue

Since we'll (hopefully!) have many people submitting work for the Hoodie website, we need to determine who owns the content they submit, and how it should be licensed. This needs to apply to written work, as well as any illustrations, photographs, or any other original work submitted for inclusion the Hoodie website.

The Solution

Create a document on content ownership and licensing. My suggestion is that the author of the content owns the work, so they can post it on their own websites, but we ask it be licensed under CC-BY-SA 4.0. This fosters the sense of openness in the community, and that by building upon others' work, we can create something even better.

When the issue is considered complete

When we have documented in this repository who owns submitted content of any kind, and under what license we either recommend, or require, depending on the content.

Check out the TGIF doc here.

We need contributors to help curate this weekly blog post of a fun roundup of interesting weekend reads for our Hoodie blog friends.

The time commitment is very minimal and I could see a single contributor doing this once a week (after reviewing the initial template I bet someone could do the whole thing in an hour and I could ensure it gets queued up for publish), or a team of rotating contributors rotating posts could work!

This issue is reserved for participants of Welcome to Open Source, Atlanta.
If it’s still available after April 2nd, it’s all yours :)

✏️ The Task

We’ve started a series of brief interviews with some of the Hoodie core contributors. You can see examples of these here:

• Alex Feyerke
• Charlotte Spencer
• Jenn Turner

I’m requesting that someone write up a new interview with Gregor Martynus (@gr2m). To claim this task do the following:

• Claim this issue (@kmcrayton7)
• Review the previous posts above.
• Find the Meet the Hoodies sample doc in this repo.
• Contact @gr2m to collaborate on a draft.
• Submit to @renrutnnej @gr2m or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

What is your blog post about? Describe it in about one paragraph.

Our first 4 "Meet the Hoodies" events in NYC, Berlin and Frankfurt:
https://ti.to/hoodie/

Approximately how long do you think the post will be?

2000 characters?

Approximately how long do you think it will take you to write this post?

I have a draft already:
https://docs.google.com/a/martynus.net/document/d/16h0c2NDfPn_PFZc_UoXgoHk8ZZkhcC7N2lzuqucp93w/edit?usp=sharing – please edit away <3

Do you think your post could make use of any illustrations or photographs?

Yes, I uploaded them to flickr:
https://www.flickr.com/photos/116240988@N08/sets/72157664073558051

Do you have any links to previous writing?

not really :(

Where else can we find you on the internet? (e.g. your blog, Tumblr, Medium, Twitter, etc.)

• https://twitter.com/gr2m/
• https://github.com/gr2m/

Anything else you want to tell us?

💐 to all the wonderful Hoodie editorial humans

Please feel free to put my draft upside down, I’m looking forward to learn from your changes :)

The Problem

We have no file to read to show us how to do a Meet the Hoodies interview.

The Solution

Write a document in this repo, telling team members how they can do a 'Meet the Hoodies' blog post like #40. Covering the picking, the writing, the reviewing, the publishing.

Interview questions are:

1. What's your favorite animal?

2. What's your role / what have you contributed to Hoodie?

3. What's your favorite use of Hoodie in the wild?

4. What in your opinion makes the Hoodie project unique and interesting?

5. What advice do you have for aspiring Hoodie contributors?

As per https://github.com/hoodiehq/editorial/blob/master/documents/blog-post-types/meet-the-hoodies.md

I’m nominating @renrutnnej :)

Here are your questions!

1. What's your favorite animal?
2. What's your role / what have you contributed to Hoodie?
3. What's your favorite use of Hoodie in the wild?
4. What in your opinion makes the Hoodie project unique and interesting?
5. What advice do you have for aspiring Hoodie contributors?

The Issue

Those not used to checking their GitHub notifications may miss a lot of what happens on GitHub until its too late. And many may miss the suggested 72-hour window for commenting on new process suggestions before they are accepted.

The Solution

Add a GitHub integration to the editorial Slack channel linked to the editorial repository.

When the issue is considered complete

Everyone in the editorial channel can see when a new Issue is created, when a new PR is created. Maybe when a new comment is made too but perhaps that will make the channel too busy?

The Issue

Blog Posts are submitted by making a PR against the gh-pages branch of Hood.ie. It would be erroneous to assume that everyone knows how to use GitHub, or how to make a PR.

The Solution

Create a guide on each step of the process on submitting a blogpost.
My thoughts are:

• TL;DR version for those who know how to use GitHub
• Step by Step guide for those who can/want to use the command line
• Step by Step guide for those who want to do it purely using the GitHub website.

When the issue is considered complete

There is a file (.md, markdown) in this repository on how to submit a blog post to the Hood.ie repository.

Overall Hoodie messaging overhaul

I looked into Hoodie a good while ago, and was confused as to what the product actually does. The homepage didn't really give a descriptor of that.

Fast forward to today, and the website has gotten better, but there's still not a succinct point of what Hoodie is.

The first real, non-rhetorical copy on the page says it's first a tool for front-end developers who want to build their own applications, and it's second a platform that developers can build on.

There are two problems here: the way in which Hoodie creates applications isn't defined, and developers are put as second-class citizens.

With the first problem, there needs to be a defining element that conveys what the product does in terms the reader knows and can understand. Is it a static site generator? A back-end API for content hosting? A fast 0-60 CMS? There needs to be definition from the very beginning so people can know what they're getting into.

With the second problem, I would say all users should be first-class - we shouldn't alienate developers by saying "this playground is for east side kids, but you west side kids can play here too, I guess." It doesn't create a super welcoming environment for developers.

Finally, I know this is a bit outside the scope of the editorial team. However, I think that since this team will be handling social media and content that's put out other than blog posts, we need to be able to audit the website as well - if you disagree with this or feel president needs to be set/discussed, we should open another issue.

we shortly discussed this in Hoodie Chat and agreed it would be a good idea, so let’s do this :)

We would love to ask first time Hoodie contributors a few questions. A common situation for that would be if a starter issue like this gets merged: hoodiehq/hoodie-account-server#98

I suggest a few questions here and am looking forward to your input, in terms of what questions to leave out, to add, change of order, etc :)

1. How can we call you?
2. What pronouns do you use?
3. Could you tell as a little bit about you?
4. Was your contribution to Hoodie your first contribution to Open Source?
5. How did you find out about Hoodie
6. What is your motivation to contribute to Hoodie?
7. Would you like to continue contributing to Hoodie?
8. Is there anything we could have done better to help you with your first contribution to Hoodie?
9. Are you on Twitter? If yes, what is your Twitter handle?
10. Would it be okay for us to invite you to Hoodie’s contributors team on GitHub?
11. Would it be okay for us to tweet about your contribution?

The Issue

No-one knows much about the team or this repository yet, so we should update our README to inform the awesome people who come across us.

The Solution

Update the README to explain who we are! https://github.com/hoodiehq/editorial/blob/master/README.md

In the #editorial Slack channel (which you should join, if you haven't already!), @Charlotteis brought up the point of making sure we hear from everybody in the community who has interest in this project.

charlotteis [11:53 UTC-8]
Question: how many people should review submission of processes before we merge them?

charlotteis ​[11:54 UTC-8]
I want to make sure the majority of happy with process before we commit them to stone (merge a PR)

charlotteis ​[11:55 UTC-8]
Not a criticism of the good work that has been happening whilst Ive been unable to help, but more of a query!

charlotteis ​[11:56 UTC-8]
And what do we do if there are fundamental disagreements in processes that are merged without group consensus.

zach [11:57 UTC-8]
@charlotteis: we should have at least a couple people give a 👍, but for at least how i see it, i don't think merging a process means it's set in stone. processes should always evolve as a project goes on, so i personally feel we shouldn't be too cautious to merge quickly, and then iterate over time

charlotteis [11:57 UTC-8]
Again NOT a criticism. Ive just spent a long day of thinking about processes and I am trying to pre empt events that will eventually happen in the future.

charlotteis ​[11:58 UTC-8]
So in my ezperience, particularly with underrepresented folk, they might not feel comfortable/capable of challenging a process.

charlotteis ​[11:58 UTC-8]
Just thinking out loud :)

I want to start with @Charlotteis' point of making sure we get enough feedback on our processes. I think that as developers, we have a bit of an itch to merge pull requests as soon as possible. 😆 For this kind of project, I think that leaving pull requests for process documentation open for a little while is fine. In the Slack channel, a 72 hour time period for has been suggested. I'm 👍 on this. The few pull requests that have been merged quickly so far are good, since it's given us a base to work off of. We're now able to at least get things started for publishing a post, as seen on GH-14.

Next, on the point of disagreements: They'll happen! We should be prepared for them. Not only that, we should welcome them. Being able to be candid is important for the best ideas to come out. However, I definitely recognize that bringing up a disagreement in an open environment like ours, especially when there may be a multitude of people who disagree with a disagreement, can be very scary. No one wants feelings to be hurt, and we definitely don't want to drive someone away because of criticism. As well, if someone is contributing that you may look up to, it can be hard to give criticism, since you don't want to offend them, you might feel like an imposter, of sorts, telling them something is wrong, or you just don't want to risk publicly feeling embarrassed.

All of this comes from the stigma of failure being "bad", and that we should never fail. I think that as a project, and as a community, we should try to challenge that. If anything, we should encourage failing fast, and failing early. That way, by the time we ship something, we have something ✨ absolutely amazing ✨.

I think we should come up with some mission statements for this project, that celebrate the creative spirit we aspire to have, and that inspire people to get involved. They can be similar to the statements Hoodie already has. I'll likely write up a couple at some point, but I really want to make sure everyone has the chance to suggest what we're trying to foster in this community, so that we're actively working together. The more we work together, the more trust we build between each other, which will lead to more openness and candor, which will create super awesome products!!

Finally, on the point of including people from underrepresented groups. I mentioned this in the Slack channel as well, but I really think we're on the right path by working transparently as we have so far. Overall, this is something I really feel we can, and we should, do right. I want to leave it to others to give their thoughts on this matter, since I'm not really affected in the same way as some people, and won't have the perspective others will. All I want to make sure is that we feel comfortable talking about this. 😄

As always, I welcome everyone's feedback and comments. 🎉

P.S.

I've been writing a lot of process stuff for this team, as I'm really excited about its possibilities. I hope that no one feels I've dominated any conversations so far. I promise you: it's just excitement, and a motivation to get this project to its full potential! Whenever I ask for feedback, I truly mean it, and I'm always happy about everything everyone has to say. My goal for now with my participation in this project is to get the ball rolling, so that soon enough, it's a bit less of what we're going to do, and a bit more of what we are doing. 😉

🎯 The goal

the current background banner image is a bit outdated:

We would like to replace at least the image on the right side with one or two images from our Meet the Hoodies events, which show that we are more than young white boys hacking on a couch :)

📋 Step by Step

• claim this issue (@girvo)
• take the background image, replace the couch image on the right with one or two images from one of these: https://www.flickr.com/photos/116240988@N08/sets/72157664073558051
• comment below if the final image, we will put it in :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

We need someone to create some copy (1-2 sentences) about Hoodie and submit it to the official PouchDB site (http://pouchdb.com/users.html).

I can assist with getting assets to send along with our submission.

• Claim this issue (@turcapat)
• Research and write a 1-2 sentence description of what Hoodie does.
• Find out the guidelines for submitting to http://pouchdb.com/users.html.
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• Ping any of the above for a logo asset to submit with the final copy.
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

The Issue

Not everyone feels able to talk in the open about what they want to, or feel able to challenge things publicly.

The Solution

Add a paragraph to the README and/or CONTRIBUTING to show people who they can contact privately should they need to. Point out that you can privately DM on Slack, but also private email addresses if possible.

As the team is in its infancy, I think myself and Jan should be the points of contact.

When the issue is considered complete

It is clear in a document who can be contacted privately (and how) should the need arise.

Hello Editorial Team 👋

I will co-host a "Welcome to Open Source" event / workshop in Atlanta in April, and I wrote a blog post to introduce the idea behind it to the world, and also to send it out to other Open Source projects so that they can participate. I’ve started a Pull Request to our blog here:
hoodiehq/hood.ie#253

Per hoodiehq/discussion#90
Part of #49

We need a contributor to help create copy for a landing page for new and existing contributors (currently at http://hood.ie/contribute/). It would be like docs.hood.ie, but documentation for contributors, not users.

We could document conventions like how we create READMEs, how we prepare issues to make them "starter" issues, what tools we use, why, and how, we could make tutorials where we go through the code base explaining how things work together. And all this for both, code & editorial contributors, of course.

You would be coordinating and collaborating with @gr2m

This would be an ongoing effort, so multiple contributors can help!

UPDATE: APRIL 5 @gr2m and I (@rubymorillo) spoke about the content and discussed a few considerations which would widen the scope for this project. Here's a summary of what was discussed below:

• The contributors page is envisioned as a standalone site (a single page app, perhaps?). The goal is for it to have all of the information people would need without being restrained by the format of the current site.
• The goals of this page are to 1. Provide documentation for contributors who are involved/want to get involved. This includes answering questions about how to become a contributor or a maintainer, and understanding the workflow of each team for ease of use. 2. Showcase the different tracks (code, design, editorial, documentation) through use of the mascots, and allow contributors to access track-specific documentation and see tickets (more below).

Possible site flow

TOP LAYER
Icons of the mascots (with track names underneath), preceded by a "get started" icon. When a user clicks on "Get Started" it'll jump to a section with general documentation that is relevant to all contributors, regardless of track.

TRACKS
When a user clicks on a track mascot, they'll jump down to that track which will have a few sections: 1. Track-specific documentation, with information about preferred Git flow, formatting, etc. 2. Existing Contributors: Issues that are available to people that have contributed before? (We didn't clear up what else could live here) and 3. New contributors: tips for new contributors and issues that are tagged with Your First PR (or another label).

Other possible elements

Something else that was discussed but we couldn't answer was: how do we showcase a place with who did what? What contributions have been made and by whom? Presently, we celebrate PRs on Twitter, but it would be great to have a place where we expand on this further; institutionalizing appreciation for contributors in general. We aren't sure if this /contributors page is the best place for it, so that's a question we wanted to throw out to the team.

Final things to consider

We talked about how people frequently ask "How do I become a contributor?" or "How do I become a maintainer?", questions which could live on this page. Are there any other questions around contributions that could live here? If so, what?

Please add your thoughts, everyone! cc @janl @renrutnnej

UPDATE: APRIL 12 @jsimplicio and I (@gr2m) spoke about the information architecture and user experience of what this contributors landing page could be. Here’s a summary of what we came up with, the full log of our chat is here: https://gist.github.com/gr2m/8a22d8bd923f760831c42fd308e74400

We came up with a name for this thing: "Hoodie Camp". It resonates with me, because it makes sense with the "Hoodie Camp Release" where we decided to focus on contributors. The "Hoodie Camp" will remain after this release though as the place where all Hoodie Contributors hang out, see what is happening, who needs help, and what is up next. Also "Hoodie Camp Site" is so fantastically ambiguous :)

We came up with this overall architecture:

• Contribute
  This is where we could show open for new contributors, returning contributors, pull requests that need reviews, etc
• Roadmap & News
  Show our overall master plan (Camp / Village / City) release, what parts we currently work on, and show a log of what happened lately
• Help
  Documentation for contributors and maintainers, e.g. how to start a pull request, how to rebase / squash commits, how to create a new contributor-friendly issues, what are starter issues, etc etc etc

"Contribute" (or how ever we will call the part of the site) would be the default landing page. We could start with it and ignore the other two parts for the first version and add them later. The Contribute landing page would welcome (new) contributors and show open YFPR issue by default. I can change that to show "next step" (or non-YFPR or how-ever we want to call them) issues, or to show me issues that people are currently working on, showing me pull-request that are awaiting review, etc. So I can set a filter depending on wether I am a new contributor, a returning contributor or a maintainer / reviewer. I get an overview of open issues across all teams: code, design, documentation, editorial (sorted alphabetically ¯_(ツ)_/¯). When I’m part of the editorial team, I can dive into the "Editorial Contribute" landing page and see more issues and what ever else makes sense to display there.

Where do the issues come from?

Our idea is to create a new repository like https://github.com/hoodiehq/camp. All teams use that repository to create well-prepared issues for new and existing contributors. The idea is to bring us all together to one place, and to have a central place we can send people to instead of them getting lost in all our Hoodie repositories. The issues would have tags to differentiate between issues for new and existing contributors (maybe a single "Your First PR" label would be enough) and tags to differentiate the different kind of work like "Design", "Code", "Editorial" etc. Of course issues can have multiple team tags, too :)

Where does the Roadmap / updates / docs come from?

Roadmap can be generated out of "High level issues" and Milestones like we did at http://gr2m.github.io/milestones/, which is generated out of https://github.com/gr2m/milestones/issues. Help & Docs can be generated (or simply link to) the repositories wiki page. And latest updates can be loaded from the a special wiki page, too :)

The Issue

Right now, I believe that @janl and @gr2m are the people who manage the Hoodie Twitter account. It is not very active and curated so we'd like to curate Tweets from all parts of the Hoodie community and outside. We have a lot to talk about, we need to share it!

The Solution

Work out the best way to get people scheduling tweets (Buffer?) and then decide what we will tweet and when. Perhaps 1-2-3 dedicated Tweeters who want to take up the task.

When the issue is considered complete

There is a tweet team who are set up to schedule tweets on the @hoodiehq twitter account.

Part of hoodiehq/hood.ie#234

Starter Issue

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects ☺️

✏️ The Task

In preparation for the Camp Release we are trying to update the hood.ie site. This specific writing task involves adding content to the Hoodie Animals page to give readers a better idea of our revolving cast of animal characters. 🐻

• Claim this issue (@NeekyRabbit)
• Write a bio between 200-400 words long.
• Submit to @renrutnnej @Charlotteis or @janl for review (Google docs probably work best for this sort of thing)
• You are done 👏 comment below that your content is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)