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

Addition of CONTRIBUTING and PROCEDURES file #10

Open
lilluzzi opened this issue Feb 22, 2022 · 2 comments
Open

Addition of CONTRIBUTING and PROCEDURES file #10

lilluzzi opened this issue Feb 22, 2022 · 2 comments

Comments

@lilluzzi
Copy link
Contributor

lilluzzi commented Feb 22, 2022

Proposal to add CONTRIBUTING and PROCEDURES file to governance repo.

----DRAFT-----

CONTRIBUTING and PROCEDURES

Code of Conduct & Diversity

All activities related to the L3AF project must adhere to our Code of Conduct and Diversity policies

Licensing

All contributions must conform to the licensing guidelines of the L3AF project

Issues

Issues are opened and managed in GitHub Issues under each repository: https://github.com/l3af-project

Ways to Contribute

  • Code Contribution
  • Issue submission, resolution, comment
  • Wiki contribution- L3AF Wiki
  • Contribution a document
  • Ask a question or provide feedback to the project
  • Share your knowledge!

General GitHub Workflow:

Guidelines for Contributors:

  • Each code submission should include an issue identifier number to reference what is being addressed by this change.
  • Each code submission that includes new code branches must include automated test cases to exercise the new code branches added.
  • Commits must be signed and DCO approved.
  • Commits should be rebased into the latest branch's HEAD.
  • Additionally, we recommend the following Best Practices: https://docs.releng.linuxfoundation.org/en/latest/best-practices.html

Guidelines for Committers/PTL:

  • When performing code reviews, committers should check the following items:
    • Make sure CI versification was successful.
    • Verify that the submission contains appropriate test cases.
    • Verify that the commit message is explicit and is appropriate for the code being changed/added/removed.
  • After code is merged, the committer should make sure any post CI processing was successful.
  • Pull Requests require approval from the committers team for the respective repo.
  • New committers can be selected by performing a TSC vote.

Branch Guidelines:

  • Main development happens in the "main" branch.

Procedures:

  • Governance and procedures for the project can be found here.
  • A list of L3AF Technical Steering Committee Representatives can be found here.
@dthaler
Copy link
Collaborator

dthaler commented Feb 23, 2022

Can you open a pull request?

@jniesz
Copy link
Contributor

jniesz commented Mar 24, 2022

When you open PR can you please include the names directly into the file instead of linking to the wiki?

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

No branches or pull requests

3 participants