[Docs] Hackathon

[ahmadnassri]

Hey guys,

we (@pearlchen + @ahmadnassri) are thinking of the viability of running a Yeoman Hackathon in Toronto as part of the Yeoman Toronto group, where developers can provide loving support in the form of:

• tackling some bugs
• helping test & close Github tickets
• build new features & plugins for the rest of the world to use

The format would be something along the lines of:

• Intro to open-source contribution etiquette and github pull-request process. (for those unfamiliar)
• Guidelines from the maintainers (that's you!)
• Issue board / backlog grooming / picking group & assignment
• Split into groups and start tackling assigned tasks.

I'm not sure how big the open-source community is in the city, and how many people would be interested in donating their time to open-source projects, but I am highly optimistic :)

I'm also not certain to what degree would a group hacakathon in this format would be of value to the core development? or if any at all? the idea is to help the maintainers, not create more work for them!

love to get some feedback, thoughts, and if any similar experiment was done before, any key learnings?

cc: @sindresorhus @addyosmani

[robwierzbowski]

Depending on when / how long, I might be interested in coming up from
Pittsburgh.

On Wednesday, June 25, 2014, Ahmad Nassri notifications@github.com wrote:

Hey guys,

we (@pearlchen https://github.com/pearlchen + @ahmadnassri
https://github.com/ahmadnassri) are thinking of the viability of
running a Yeoman Hackathon in Toronto as part of the Yeoman Toronto group
http://www.yeoman.to, where developers can provide loving support in
the form of:

• tackling some bugs
• helping test & close Github tickets
• build new features & plugins for the rest of the world to use

The format would be something along the lines of:

• Intro to open-source contribution etiquette and github pull-request
  process. (for those unfamiliar)
• Guidelines from the maintainers (that's you!)
• Issue board / backlog grooming / picking group & assignment
• Split into groups and start tackling assigned tasks.

I'm not sure how big the open-source community is in the city, and how
many people would be interested in donating their time to open-source
projects, but I am highly optimistic :)

I'm also not certain to what degree would a group hacakathon in this
format would be of value to the core development? or if any at all? the
idea is to help the maintainers, not create more work for them!

love to get some feedback, thoughts, and if any similar experiment was
done before, any key learnings?

cc: @sindresorhus https://github.com/sindresorhus @addyosmani
https://github.com/addyosmani

—
Reply to this email directly or view it on GitHub
#256.

Rob Wierzbowski
@robwierzbowski http://twitter.com/#!/robwierzbowski
http://github.com/robwierzbowski
http://robwierzbowski.com

[sindresorhus]

@yeoman/yeoman-core

[SBoudrias]

The way I see how we organize the project, there's 4 main axis:

1- The core system yeoman/generator
2- The documentation yeoman/yeoman.io
3- The officials generators yeoman/generator-n
4- The plugins (usually Grunt stuff)

As this is a hackathon, I think the more interesting is the core system and the generators (could also be creating a generator from scratch).

About our contributions guidelines, we have some stuff here, although it is not 100% up to date around submitting PR and issues: http://yeoman.io/contributing/ (some work could be done to bring it up to speed)

Right now there's no formal guidelines about how we track and label our issues. I guess if you want to pick from our list of bugs/features, a clear organization would greatly help.

Then, having an idea of what potentials participants are interested in would help too. Are they into particular frameworks? Then they could help adding new features / unit tests to existing generators. Do they want to learn about Node? Then they should help adding features / code coverage to the core system. Are they looking to learn Yeoman? Then they could create a new generator from scratch and participate in the documentation effort. Do they just want to get involve in OSS? Then there's lots of issues to tackle about the new website.

Actionable items

• Setup meetup group (probably already done)
• Setup poll with about subjects of interest
• Updating Yeoman project contributions guidelines
• Defining an issue classification norm allowing easy discoverability for new contributors

[ahmadnassri]

@SBoudrias thank you for the detailed break down! quick notes:

• yes, I agree, the focus should be on the core + generators.
• work on the contribution guidelines prior to kicking this off to bring it up to speed would be best
• clear organization of the bugs/features would also be ideal, but this could also be a task for hackathon contributors, give us the guidelines and we'd help sort / label issues?
• participants: we have a very strong Node community here in Toronto, the question is willingness to participate, to which we can start polling folks to see where the interest is.

Action Items for @ahmadnassri + @pearlchen

• meetup group + website already setup and active.
• setup poll through meetup group

I'll be in SFO tomorrow _June 29th_ then back in YYZ on _July 5_
@SBoudrias (and anybody in SFO?) would be great if we sync up over coffee?

[SBoudrias]

@ahmadnassri Yes sure it'd be great to meet and sync! There's @eddiemonge in SF too.

[SBoudrias]

Just updated our contributing guide: http://yeoman.io/contributing/

I updated the first page about how to get started and the one about sending a PR. Let me know how you find it, and be sure to help us improve it!

[ahmadnassri]

@SBoudrias just sent you an email, RE: meet up in SFO.

[eddiemonge]

a meetup in sf sounds good

[eddiemonge]

Added an official repo at https://github.com/yeoman/Hackathons

This should have a Hackathon starter kit of sorts:

• Tips on how to organize a hackathon
• Sample schedules
• Ideas for people to work on curated by the team members
• How to get sponsors and generate interest
• Other things?

There should be a generator to create a sample site or info to paste to things like meetup

[SBoudrias]

I'll close this issue as we now have a dedicated repository.