Guidelines for requesting repos added to the org

[steelbrain]

Just like the title says

[DanPurdy]

Yeah I was wondering about this, do you mean actually adding to the Github organisation, to the linter website or both?

Something simple such as a checklist consisting of

• a licence
• contribution guidelines
• eslint / coffee-lint config file
• a README with acceptable instructions
• possibly some community guidelines such as with the Sass community guidelines

[steelbrain]

You don't necessarily have to be in the organization to be added to the website. I meant the AtomLinter org.

[DanPurdy]

In which case instructions to cover both would be good. I'm assuming a PR to get a plugin added to the site would be enough but the above list would be a good default guideline for having your plugin added to the organisation.

A quick breakdown of the steps needed to be taken to transfer ownership would also be ideal. Whether that's liaising to have a new blank repo setup that you have push access to or whatever.

[SpainTrain]

possibly some community guidelines such as with the Sass community guidelines

👍

http://todogroup.org/opencodeofconduct/ is a nice easy one, and is already used by Atom

[SpainTrain]

What are the concrete steps to make this so? Add the info to the AtomLInter.org site?

[SpainTrain]

Could also see something like http://eslint.org/docs/developer-guide/governance being useful for clarity and transparency. Our model is obviously more distributed, so would take some work to draft unfortunately

[Arcanemagus]

I could see our model fitting in there, each repository having a Project Lead (ower in the team), only a few have enough people to have more than that role though.

[SpainTrain]

That's almost certainly the most useful of any role we would want to canonize. I often have no clue whether a linter has an active primary maintainer (until sifting through closed and/or recent issues/PRs)

[Arcanemagus]

Yea, it would be nice to make more usage of the teams within the org.