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

Updated contribution guidelines with more explicit process for becomi… #723

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

aklish
Copy link
Member

@aklish aklish commented Oct 16, 2018

…ng a committer and publishing a release

I'm hoping for some healthy debate on this - so please consider this process a first pass.
Thanks.


Releases are published manually from master by project Admins.

When a new release is published, it is first published as a release candidate. The candidate will be available for up to 1 week for testing from the community before
Copy link
Collaborator

Choose a reason for hiding this comment

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

I like the idea of release candidates. That said, should we suggest a minimum time for non-critical (I.e. non-security related) releases to give the community time to consume it?

The way I’ve read this is that there is a maximum bake time of 1 week.

# Community

While anyone is free to open pull requests against the project, Elide has two defined roles:
- *Committers* - Are the gatekeepers of the repository. They approve pull requests and have write access to merge against master or other mainline branches. Committers also help set the direction for the project by deciding on major enhancements or design changes.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we detail a more complete process for committers and admins in this doc? Perhaps a doc solely related to that may make more sense.

Anyway, what I’m expecting is something outlining the primary communication channels for committees/admins to stay on the same page with design and project movement.

I imagine much of this conversation to take place in a public place, but formalizing a location may make it easier for everyone to stay in sync.


# Releases

Releases are published manually from master by project Admins.
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should also outline the release process in detail. Technically, how one would go about it, that is.

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.

2 participants