contributors guide

[ashleygwilliams]

as a first step to solving #129, after a long convo with @jmeas, i think creating a very specific contributing guide at CONTRIBUTING.md will help clarify both for ourselves and potential contributors what further extensions of js-assessment should be.

in keeping with rmurphey/js-assessment-answers#31 re: style, i think that we should also focus on the technical details and styles of contributions in this doc

[kadamwhite]

+1! Contributing guides are great, and reduce a lot of confusion. I second that we be prescriptive about technical aspects as well, in the interest of maintaining this project's consistency.

Do you have a sense of how you would like to put that document together, and what we & others could do to help?

[ashleygwilliams]

good question @kadamwhite. i think my plan is to whip up a basic structure/outline with some initial ideas and commit that to a branch. and hopefully from there do some inline discussion, and have people push to that branch if we end up assigning sections, or such.

what do you think? i'd like to keep this on github (as opposed to a google doc) so it's transparent and all in one place, but perhaps that's unrealistic?

[kadamwhite]

Actually I love your suggestion, b/c I'd had the same concern about Google Docs! Let's give the branch approach a try, and we can reference this issue in PRs.

[ashleygwilliams]

cool! not sure if i'll get to it today, as i'm working on my jsconf talk a lot. but perhaps in a moment of procrastination :) either way, def something by the weekend

[jacobroufa]

@ashleygwilliams Any progress on this? Is there anything I might do to help? Also, seeing as we're both going to be at jsconf -- would you like to collaborate and have a small doc sprint for this project in person? If there's any input I can provide or anything I can help with, I'm happy to lend a hand! 👍

[ashleygwilliams]

@jacobroufa that sounds awesome! let's do it.

[rmurphey]

I'm going to close this due to inactivity. A pull request is welcome!