Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(maintenance): add project guides #36

Merged
merged 1 commit into from
Oct 2, 2018

Conversation

profnandaa
Copy link
Contributor

  • issue template
  • PR template
  • contributing guide
  • maintainers guide

closes #35

Copy link

@JaKXz JaKXz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome! I have some suggestions though.

- At least two Collaborators must approve a pull request before the pull request lands.
- PRs with commits that don't follow the [conventional commits standard](https://www.conventionalcommits.org) should be re-written when merging.
- Use Github's _squash and merge_ when landing PRs.
- CI must pass before landing PRs, needless to day.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, needless to say

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good, catch, fixing.

CONTRIBUTING.md Outdated
```
- Open the pull request, see details in the template.
- Make any necessary changes after review.
- In order to land, a Pull Request needs to be reviewed and approved by at least one `c8` Collaborator.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is different from the maintainers' guide

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I can remove this; looks like it's creates confusion...

CONTRIBUTING.md Outdated

### Setting up your local environment

- Make sure you have installed the latest version of Node.js
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a minor thing, you could just use 1. for every bullet point and markdown will figure out the numbering, even if we have to add or remove steps later.

CONTRIBUTING.md Outdated
```
$ npm run test:snap
```
- If all is passing, commit your changes following the [conventional commits guideline](https://www.conventionalcommits.org/)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd argue this isn't strictly necessary since the maintainers can do this with the squash and merge function. IME this is a barrier to entry for beginners, so I'd put it in the Maintainers' guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, will move it.

- [ ] `npm run test:snap` (to update the snapshot)
- [ ] tests and/or benchmarks are included
- [ ] documentation is changed or added
- [ ] commit message follows [conventional commit guidelines](https://www.conventionalcommits.org/)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as mentioned below, this can be optional for the contributor and is really up to the merger to enforce with GH's squash and merge function.

@profnandaa
Copy link
Contributor Author

@JaKXz -- thanks for the review Jason, fixed 👍

@coveralls
Copy link

Pull Request Test Coverage Report for Build 51

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 90.934%

Totals Coverage Status
Change from base Build 48: 0.0%
Covered Lines: 214
Relevant Lines: 218

💛 - Coveralls

CONTRIBUTING.md Outdated
## Issues

- You can open [issues here](https://github.com/bcoe/c8/issues), please follow the template guide.
- You can come over to the `node-tooling/c8` channel for discussions, [follow this link](https://devtoolscommunity.herokuapp.com/) to request for an invite.
Copy link

@JaKXz JaKXz Sep 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nit: drop for

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rephrased.

- At least two Collaborators must approve a pull request before the pull request lands.
- PRs with commits that don't follow the [conventional commits standard](https://www.conventionalcommits.org) should be re-written when merging (squash and merge).
- Use Github's _squash and merge_ when landing PRs.
- CI must pass before landing PRs, needless to say.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, if it's needless to say, it doesn't need to be here. I should've said that the first time, sorry.


- Label the issues appropriately, see the list of labels and their description [here](https://github.com/bcoe/c8/labels)
- Be welcoming to first-time contributors, identified by the GitHub `first-time contributor` badge.
- At least two Collaborators must approve a pull request before the pull request lands.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious if @bcoe thinks this project is at that level of maturity already... I wouldn't want to block a contribution waiting for that 2nd review.

Maybe this could be relaxed to should be approved by 1-2 collaborators before merging? 🤷‍♂️

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think 1 is decent; and looks like that's how it has been... rewriting.

@JaKXz
Copy link

JaKXz commented Sep 30, 2018

Thanks @profnandaa - I have a few more thoughts... sorry for the piece-meal reviews!

@profnandaa
Copy link
Contributor Author

profnandaa commented Sep 30, 2018 via email

- issue template
- PR template
- contributing guide
- maintainers guide

closes bcoe#35
@profnandaa
Copy link
Contributor Author

@JaKXz -- thanks, done.

##### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->
- [ ] `npm test`, tests passing
- [ ] `npm run test:snap` (to update the snapshot)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps add here, if any new tests have been added.

Copy link
Owner

@bcoe bcoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is very good, I'm comfortable landing; @JaKXz any more blockers?

Copy link

@JaKXz JaKXz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm done now, thanks @profnandaa :)

@profnandaa profnandaa merged commit b0d1b7b into bcoe:master Oct 2, 2018
@profnandaa profnandaa deleted the chore-35-maintenance branch October 2, 2018 04:43
mcknasty pushed a commit to mcknasty/c8 that referenced this pull request Feb 2, 2024
- issue template
- PR template
- contributing guide
- maintainers guide

closes bcoe#35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

maintenance: house-keeping proposal
4 participants