Skip to content

First stab at MAINTAINERS.md & OWNERS.md & CONTRIBUTING.md#238

Merged
mum4k merged 9 commits intoenvoyproxy:masterfrom
oschaaf:maintainers-doc
Dec 21, 2019
Merged

First stab at MAINTAINERS.md & OWNERS.md & CONTRIBUTING.md#238
mum4k merged 9 commits intoenvoyproxy:masterfrom
oschaaf:maintainers-doc

Conversation

@oschaaf
Copy link
Copy Markdown
Member

@oschaaf oschaaf commented Dec 15, 2019

  • A pre-merge checklist
  • Documents what goes into an update to the Envoy dependency

Fixes #230

Signed-off-by: Otto van der Schaaf oschaaf@we-amp.com

- A pre-merge checklist
- Documents what goes into an update to the Envoy dependency

Fixes envoyproxy#230

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@caniszczyk
Copy link
Copy Markdown

Where is the actual list of maintainers for the project?

@oschaaf
Copy link
Copy Markdown
Member Author

oschaaf commented Dec 16, 2019

Possibly I am using the wrong terminology here; this document targets to be helpful to reviewers.

Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

Thanks for putting this together, CC @envoyproxy/nighthawk-maintainers

# Maintainers

This document aims to assist maintainers.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you add some stuff on how to spot which changes are Nighthawk local vs. those that require deeper Envoy internals and architecture knowledge?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

done

@htuch
Copy link
Copy Markdown
Member

htuch commented Dec 16, 2019

@caniszczyk good point. Can we have an OWNERS.md file @oschaaf in the same style as https://github.com/envoyproxy/envoy/blob/master/OWNERS.md?

We should also link to the @envoyproxy/nighthawk-maintainers team page.

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@oschaaf
Copy link
Copy Markdown
Member Author

oschaaf commented Dec 16, 2019

@envoyproxy/nighthawk-maintainers please check the newly created OWNERS.md in this PR; it has email addresses and suggests areas of expertise indicating what should be routed to whom; both need feedback.

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@oschaaf oschaaf changed the title First stab at MAINTAINERS.md First stab at MAINTAINERS.md & OWNERS.md & CONTRIBUTING.md Dec 16, 2019
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

Thanks, looks great. We're finally a real project with governance :) !

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@oschaaf
Copy link
Copy Markdown
Member Author

oschaaf commented Dec 17, 2019

Thanks for the feedback @htuch, based on that I pushed 009ab22

@mum4k mum4k self-requested a review December 17, 2019 14:20
CONTRIBUTING.md Outdated

# Communication

* Before starting work on a major feature, please reach out to us via GitHub, Slack,
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should we include link to or at least mention the Slack workspace we are using?

CONTRIBUTING.md Outdated

* Generally Nighthawk mirrors [Envoy's policy](https://github.com/envoyproxy/envoy/blob/master/CONTRIBUTING.md#pr-review-policy-for-maintainers) with respect to PR submission policy.
* Any PR that changes user-facing behavior **must** have associated documentation in [docs](docs) as
well as [release notes](docs/root/intro/version_history.rst).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This file doesn't seem to exist, while a version_history.md directly under root does:

https://github.com/envoyproxy/nighthawk/blob/master/docs/root/version_history.md

@oschaaf oschaaf added P2 and removed waiting labels Dec 17, 2019
Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
Copy link
Copy Markdown
Member Author

@oschaaf oschaaf left a comment

Choose a reason for hiding this comment

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

@mum4k comments addressed in 66ba23d

CONTRIBUTING.md Outdated

# PR review policy for maintainers

* Generally Nighthawk mirros [Envoy's policy](https://github.com/envoyproxy/envoy/blob/master/CONTRIBUTING.md#pr-review-policy-for-maintainers) with respect to maintainer review policy.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: mirrors

CONTRIBUTING.md Outdated

# DCO: Sign your work

Commits need to be signed off. [See here](https://github.com/envoyproxy/envoy/blob/master/CONTRIBUTING.md#dco-sign-your-work).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: I would put the See outside of the link

MAINTAINERS.md Outdated

As a guideline, concepts in Nighthawk that are derived from Envoy
require someone with Envoy domain expertise in review. Notable examples
are the way Nighthawk internal computes cluster configuration, its
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: "Nighthawk internally"

MAINTAINERS.md Outdated

- Does the PR have breaking changes? Then that should be explicitly mentioned in the [version history](docs/root/version_history.md).
- New features should be added to the [version history](docs/root/version_history.md).
- Breaking changes to the [proto apis](api/) are not allowed.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: "protobuf APIs"

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@oschaaf
Copy link
Copy Markdown
Member Author

oschaaf commented Dec 19, 2019

@htuch nits fixed in 7ff2dd2

htuch
htuch previously approved these changes Dec 19, 2019
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

Thanks!

@mum4k mum4k self-assigned this Dec 20, 2019
Copy link
Copy Markdown
Collaborator

@mum4k mum4k left a comment

Choose a reason for hiding this comment

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

Thank you Otto, looks good. One remaining comment.

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
@mum4k mum4k removed the waiting-for-review A PR waiting for a review. label Dec 21, 2019
@mum4k mum4k merged commit 52199ba into envoyproxy:master Dec 21, 2019
eric846 pushed a commit to eric846/nighthawk that referenced this pull request Dec 21, 2019
…y#238)

* First stab at MAINTAINERS.md

- A pre-merge checklist
- Documents what goes into an update to the Envoy dependency

Fixes envoyproxy#230

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review feedback: CONTRIBUTING.md & OWNERS.md

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review-feedback: Envoy domain expertise section

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review feedback

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review feedback

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review: fix nits

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

* Review: fix bad link, .rst -> .md

Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>
Signed-off-by: eric846 <56563761+eric846@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a PR pre-merge checklist for maintainers

4 participants