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

Compliance to awesome repository requirements #38

Merged
merged 1 commit into from
Mar 27, 2020

Conversation

glours
Copy link
Collaborator

@glours glours commented Mar 26, 2020

Add

  • CODEOWNERS
  • MAINTAINERS
  • CONTRIBUTING.md

Fix README.md to be compliant with awesome repository

Signed-off-by: Guillaume Lours guillaume.lours@docker.com

@glours glours requested review from aiordache and chris-crone and removed request for aiordache March 26, 2020 17:12
Copy link
Member

@chris-crone chris-crone left a comment

Choose a reason for hiding this comment

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

Couple of minor changes, thanks @glours!

CONTRIBUTING.md Outdated
samples that can be easily deployed with [Docker Compose](https://github.com/docker/compose).

## Missing a kind of application?
You can request a new example of application by submitting an issue to our GitHub Repository.
Copy link
Member

Choose a reason for hiding this comment

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

nit: missing \n after heading

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
You can request a new example of application by submitting an issue to our GitHub Repository.
You can request a new example of an application by submitting an issue to our GitHub repository.

CONTRIBUTING.md Outdated

## Missing a kind of application?
You can request a new example of application by submitting an issue to our GitHub Repository.
If you would like to implement a new application sample, please submit an issue with a proposal first,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
If you would like to implement a new application sample, please submit an issue with a proposal first,
If you would like to submit a new application example, please start by submitting a proposal as an issue.

CONTRIBUTING.md Outdated
You can request a new example of application by submitting an issue to our GitHub Repository.
If you would like to implement a new application sample, please submit an issue with a proposal first,
to be sure that we can use it.
Then we'll consult the community to know what can be the most valuable application with this technology/language/framework...
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Then we'll consult the community to know what can be the most valuable application with this technology/language/framework...
The maintainers will then use this issue to discuss what the the most valuable example for the application, technology, language, or framework would be.

CONTRIBUTING.md Outdated
to be sure that we can use it.
Then we'll consult the community to know what can be the most valuable application with this technology/language/framework...

After the choice made, you can submit your pull request following the choice of the community without forgetting to add :
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
After the choice made, you can submit your pull request following the choice of the community without forgetting to add :
After the choice has been made, you can submit your a pull request not forgetting to:

CONTRIBUTING.md Outdated
Then we'll consult the community to know what can be the most valuable application with this technology/language/framework...

After the choice made, you can submit your pull request following the choice of the community without forgetting to add :
- a local README.md to describe the application and explain how to run/use the sample.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- a local README.md to describe the application and explain how to run/use the sample.
- include an example README.md to describe the application and explain how to run/use the sample

CONTRIBUTING.md Outdated
The goal of the Awesome Compose is to provide a curated list of application
samples that can be easily deployed with [Docker Compose](https://github.com/docker/compose).

## Missing a kind of application?
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
## Missing a kind of application?
## Missing an example?

CONTRIBUTING.md Outdated
- a local README.md to describe the application and explain how to run/use the sample.
- edit the global README.md to add your sample in the repository main list.

## Update a existing sample
Copy link
Member

Choose a reason for hiding this comment

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

We can actually remove this

CONTRIBUTING.md Outdated
Comment on lines 25 to 38
To help maintainers understand what user or developer problem needs to be
solved, the first step to a contribution is usually submitting an issue. A well
written issue is one that clearly outlines the developer or user problem that
needs to be solved along with a list of requirements for resolution of the
problem. If there are multiple possible solutions to the problem, these can be
outlined in the issue. Once consensus is reached on how to resolve the issue, a
pull request can be created.

Pull requests that propose minor changes or improvements may be submitted
without an associated issue or discussion.

For large or high impact changes, contributors can reach out to maintainers
before starting work. This will ensure that contributors and maintainers are
aligned and increase the chance that the change is accepted.
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 you can remove this as it's more targeted at code/specs

@glours glours force-pushed the awesome_compliance branch from d45e3d8 to 30178cd Compare March 26, 2020 17:54
@glours glours requested a review from chris-crone March 26, 2020 17:55
@glours glours force-pushed the awesome_compliance branch from 30178cd to af836b2 Compare March 27, 2020 09:30
Copy link
Member

@chris-crone chris-crone left a comment

Choose a reason for hiding this comment

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

Minor changes after seeing it all together. Thanks @glours!

CONTRIBUTING.md Outdated

Before submitting a new application, check if there isn't already application sample matching your need.

If there is one, consider to update it instead of create a new one.
Copy link
Member

Choose a reason for hiding this comment

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

nit:

Suggested change
If there is one, consider to update it instead of create a new one.
If there is one, consider updating it instead of creating a new one.

CONTRIBUTING.md Outdated
The maintainers will then use this issue to discuss what the the most valuable example for the application,
technology, language, or framework would be.

After the choice has been made, you can submit your a pull request not forgetting to:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
After the choice has been made, you can submit your a pull request not forgetting to:
After the choice has been made, you can submit a pull request with the example remembering to:

Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
@glours glours force-pushed the awesome_compliance branch from af836b2 to 7fcb573 Compare March 27, 2020 10:39
@glours glours requested a review from chris-crone March 27, 2020 10:39
Copy link
Member

@chris-crone chris-crone left a comment

Choose a reason for hiding this comment

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

LGTM

@chris-crone chris-crone merged commit 78d807c into docker:master Mar 27, 2020
@glours glours deleted the awesome_compliance branch December 16, 2021 11:03
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.

None yet

2 participants