workshoppers forward

[llkats]

Picking up the discussion from #2 and continuing recent conversation in nodeschool/discussions, we are trying to get some momentum moving forwards again on workshoppers.

[llkats]

Here are a bunch of questions I asked in the nodeschool issue, just to have them upfront:

• Should all workshoppers be refactored to pull from the same base library (e.g., workshopper-adventure? (I think, yes! Consistency would )
• Should discussion about a workshopper's code be separated from people asking for help with concepts/exercises? Just looking at workshopper/nodeschool's issues, there's a mix of bug reports and requests for help, which seems suboptimal for parsing out actionable tasks.
• Is there a common code standard for workshoppers? Is there one for the example code used inside exercises?
• Guidelines for oversight should be established. It would be far too much for just two or three people to triage issues for all 8 core workshoppers. For example, we could have individual volunteers in charge of each workshopper, or even try to get chapters into the mix. I imagine chapters using workshoppers to teach their attendees how to submit pull requests, or have mentor hack nights as team-building exercises of sorts. But there should be some sort of process for handing off maintenance responsibilities so that they don't languish.
• I found Node's CONTRIBUTING document to be extremely useful in contributing to Node. Would that be a welcome addition to workshopper/org and/or each of the workshoppers? (I volunteer as tribute to make a PR).

What else is there to consider?

[martinheidegger]

How about giving an invitation to all contributors of workshoppers @ nodeschool to the workshopper repo?

[martinheidegger]

I have collected a few thoughts on quality tests in: https://github.com/workshopper/workshopper-adventure-test/issues

[llkats]

With stream-adventure and learnyounode under the workshopper org, that leaves six workshoppers out in the wild.

Pinging the following maintainers:

javascripting - @sethvincent git-it - @jlord how-to-npm - @npm @ashleygwilliams (or someone else?) scope-chains-closures - @jesstelford elementary-electron - @maxogden how-to-markdown - @denysdovhan

👋 Hi everyone, thoughts on the above discussion? Thanks!

[martinheidegger]

(Note: I have invited all of the above mentioned people to the org.)

[sethvincent]

I'm happy to transfer javascripting. Maintenance has been a community effort and putting it in an org makes a lot of sense. I'll just go ahead and do that.

Sidenote: I've been working on adventuretron (https://github.com/adventuretron/adventuretron) with the goal of making nodeschool-like workshops using electron. It's still pretty early, but so close to being ready for initial use! At some point it would be cool to try out turning javascripting into an electron/adventuretron app, as well as experimenting with loading any of the workshoppers in electron.

[ashleygwilliams]

i'm super happy to transfer the how-to-npm one! i'll need to see what npm thinks, but it could really use some more (any) stewardship than i have the time for (none).

[denysdovhan]

gonna transfer my how-to-markdown workshopper this evening.

UPD: how-to-markdown is transfered to workshopper org.

[jesstelford]

scope-chains-closures has been moved to the workshopper org :tada:

[martinheidegger]

Closing this issue due to inactivity.