Skip to content

add operational notes #157

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

Merged
merged 1 commit into from
Aug 13, 2018
Merged

add operational notes #157

merged 1 commit into from
Aug 13, 2018

Conversation

japaric
Copy link
Member

@japaric japaric commented Aug 10, 2018

As suggested in #148 (comment).

I'm putting them in a PR for now regardless of wherever we decide to put them in the end because that seems like a better place than in my head :-).

cc @jamesmunns @adamgreig

@japaric japaric requested review from dylanmckay, jcsoo, thejpster and a team as code owners August 10, 2018 04:39
Copy link
Contributor

@ryankurte ryankurte left a comment

Choose a reason for hiding this comment

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

Looks good to me! Thanks for writing it out.

Copy link
Contributor

@therealprof therealprof left a comment

Choose a reason for hiding this comment

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

LGTM

@jamesmunns
Copy link
Member

LGTM! Thanks for writing this all out.

@jamesmunns jamesmunns self-requested a review August 10, 2018 10:25
japaric added a commit to dvc94ch/riscv-rt that referenced this pull request Aug 11, 2018
japaric added a commit to dvc94ch/riscv that referenced this pull request Aug 11, 2018
[team]: https://github.com/rust-embedded/wg#the-cortex-m-team
```

- If the repository uses CI, configure bors. Add a `.github/bors.toml` file with these contents:
Copy link
Member

Choose a reason for hiding this comment

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

I think this should just be bors.toml, not inside .github/?

Copy link
Member Author

Choose a reason for hiding this comment

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

That's where I have been putting it so far but I've been told that putting it inside .github also works. I think is better to make it less visible since most people (both contributors and reviewers) won't be modifying it.

Copy link
Member

Choose a reason for hiding this comment

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

Fine with me. Should we move it on the existing repositories then?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes. I also need to add block_labels = ["needs-decision"] to most of them.

@jamesmunns
Copy link
Member

Seems like discussion is complete, merging manually.

@jamesmunns jamesmunns merged commit 3987e92 into master Aug 13, 2018
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.

7 participants