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

Add minder technical charter. #4834

Closed

Conversation

riaankleinhans
Copy link

Summary

Add Minder Technical Charter

Signed-off-by: riaan kleinhans <[email protected]>
@riaankleinhans riaankleinhans requested a review from a team as a code owner October 28, 2024 08:55
@CLAassistant
Copy link

CLAassistant commented Oct 28, 2024

CLA assistant check
All committers have signed the CLA.

@staceypotter staceypotter requested review from JAORMX and puerco October 28, 2024 11:27
@puerco
Copy link
Contributor

puerco commented Oct 28, 2024

Hey @riaankleinhans thanks for adding this, I have a couple of questions:

  • Do you have a markdown version? I think I would like to check it in as text from the beginning to track the evolution of the document via its commit history.
  • Do we need to host the charter on the main site? In other projects, I've hosted the charter in the community repository (for example in openvex), which helps keep the governance documents neatly separate from the code. Of course, we would point back to it from here and the other repositories.

@riaankleinhans
Copy link
Author

@puerco the LF Project formation team prefer that the PDF version is kept on in the repo.
There is not suppose to be any changes to the document without the approval of the LF Formation team.
You can convert it to .md without change, as it is a legal document.
The document can live in any of folders within this repo and should be easily discoverable by the community.

@evankanderson
Copy link
Member

evankanderson commented Oct 28, 2024

See mindersec/community#11 -- I've converted to markdown and updated the document we'd checked in ahead of time in the community repository. There are also a few changes in the PDF from what we proposed that I'd love to get @riaankleinhans feedback on.

evankanderson added a commit to evankanderson/minder-community that referenced this pull request Oct 28, 2024
evankanderson added a commit to evankanderson/minder-community that referenced this pull request Oct 28, 2024
@riaankleinhans
Copy link
Author

See mindersec/community#11 -- I've converted to markdown and updated the document we'd checked in ahead of time in the community repository. There are also a few changes in the PDF from what we proposed that I'd love to get @riaankleinhans feedback on.

@evankanderson moving the document to the community repo would not be a problem as it is still within the GH Org dedicated to the project.
However the changes proposed in the mindersec/community#11 can not be made without the LF Formation team updating the PDF document.
Due to he fact that a change that seem like a "cosmetic" change to the average contributor could have a serious legal impact on the project, the Formation team require that the document must be added to the repo without any changes.

If the changes are important to the project, I can request for it to be reviewed and updated and a new PDF be issued.

@evankanderson
Copy link
Member

The changes in mindersec/community#11 undo changes that we'd wanted to make, to make the checked-in document match the LF PDF here.

I'd checked in our red-lined copy of the document when creating that repository, before the LF legal review was completed.

I'm happy to go through the appropriate process to get the changes we care about that differ from the PDF approved or countered by LF legal (probably mostly the electronic vote simplification). The most important part for me was getting our existing copy corrected, and making sure that future changes were tracked and guarded effectively.

@riaankleinhans
Copy link
Author

@evankanderson @puerco
Closed in favor of mindersec/community#11

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.

4 participants