search

OpenSUTD / community

OpenSUTD's DNA
MIT License
0 stars 2 forks source link

Contribution Guidelines #1

Open tlkh opened 6 years ago

tlkh commented 6 years ago

As an example: https://gist.github.com/PurpleBooth/b24679402957c63ec426

I'm thinking a separate code of conduct document is still a good idea though. In which case:

Let's get this worked out ASAP.

welcome[bot] commented 6 years ago

Thanks for opening your first issue here! Please check out our contributing guidelines and code of conduct.

tlkh commented 6 years ago

Haha and let's have another discussion on some automation on the OpenSUTD repos. (See welcome-bot above haha)

joel-huang commented 6 years ago

There are some primitive guidelines I created on the original OpenSUTD repo for contribution and conduct. Those might be useful as a starting point, but we can have a permanent open discussion here to make sure they're relevant as the community & platform evolves.

Fishbiscuit commented 6 years ago

Updated the documents with proposed guidelines.

Suggest we need

  1. Some sort of theme for our internal openSUTD documents. much like how ROOT has GRASS or everything from apple starts with an 'i'
  2. Key repositories for common accessed materials
  3. Set up the roles and responsibilites of the Community architects and tech evangelists

Let's take the chance to source ideas during GRASS on 9/10/2018

methylDragon commented 5 years ago

I suggest splitting the contribution guides into its own repo for visibility purposes wrt. the pinned repositories. It'll make it easier to onboard people as well.

Can I also recommend putting project nomenclature under the contribution guide. We should make it a one-stop shop.

tlkh commented 5 years ago

Agree with @methylDragon that given how important this is, let's give it more visibility.

In addition, there's still work to be done, so recommend continuing on work in #3