Add a preface to introduce terms; revise CF Council and introduce the EGC #52
Conversation
|
LGTM |
Comments about voting should go into decision making or to specific member/cf-council pages. So yes, let's make them, but we don't necessarily need it here. |
ebullient
force-pushed
the
preface
branch
3 times, most recently
from
b78bf7a
to
cf3cc18
Compare
ebullient
changed the title
ebullient
changed the title
bylaws/2-cf-membership.md
Outdated
| ## Project Leaders and Code Owners | ||
|
|
||
| Project Leaders and Code Owners are the pillars of their projects and the CF at large. | ||
| Each CF project is represented by a nominated **Project Leader**. |
There was a problem hiding this comment.
Only one, or at least one?
There was a problem hiding this comment.
That's the question. How do I avoid swamping the single maintainer of a project by another project that has 5 leads?
There was a problem hiding this comment.
I think you could just say that each project gets one vote if that's the problem.
There was a problem hiding this comment.
That was the intent. I suppose I could revise to use the word "representative" rather than leader. I think I'll do that. less confusing.
There was a problem hiding this comment.
Updated. WDYT?
bylaws/2-cf-membership.md
Outdated
|
|
||
| - **Responsibilities**: Managing access to project repositories and steering project direction and development. They ensure their projects adhere to CF policies, and collaborate with the CFC to ensure policies remain relevant and reduce procedural burden. | ||
| - **Membership and Voting Rights**: Project leaders and code owners are automatically eligible for CF membership, with voting rights and eligibility for CFC positions. | ||
| **Code Owners:** The `CODEOWNERS` file in a GitHub project organization's repository specifies individuals responsible for code in a repository. Nominated Project Leaders should be listed in their project's CODEOWNERS file. The CF wants to ensure that individuals representing the project on the EGC have a demonstrable commitment to that project's ongoing health and success. |
There was a problem hiding this comment.
This implies projects should follow certain guidelines and meet a minimum set of requirements in their file structure and contents. Such requirements must be defined and explicitly listed somewhere.
There was a problem hiding this comment.
Yes. We can summarize. see templates .. I have to put a CODEOWNERS in there, but yes. we can clarify (I think in templates) what breadcrumbs/artifacts we expect projects to have. (and try to keep them light)
There was a problem hiding this comment.
I updated the templates/README.md to describe these files (as they are currently drafted).. Does that help?
There was a problem hiding this comment.
Revised the language of this section to drop reference to CODEOWNERS, as that belongs elsewhere. I think it reads better now.
I also updated the description of projects to be less GitHub-centric.
| - Officers may resign at any time by notice to the CFC. | ||
| Expanding beyond the CFC, the Extended Governance Committee (EGC) plays a vital role in encompassing broader representation and decision-making within the CF. | ||
|
|
||
| - **Composition:** The EGC includes every member of the CF Council and one nominated leader from each CF project. |
There was a problem hiding this comment.
How do we handle potential conflicts in EGC membership. i.e, a project would like a different member to step up to the EGC but the current member does not want to let go for example.
There was a problem hiding this comment.
That is another good question, aside from conflict resolution help, I'd expect this to be resolved by the project itself. One of the things the foundation will ask for (between GOVERNANCE.md and CODEOWNERS) is a clear definition of who the project leaders (not just the EGC rep) are.
A project could decide to adopt CF decision making processes (and maybe the automation that comes with it), in which case, votes are held, and access/representation changes, whether that person is a fan of the plan or not.
ebullient
force-pushed
the
preface
branch
2 times, most recently
from
b0980c6
to
74eb636
Compare
Co-authored-by: Yoann Rodière <[email protected]>
Co-authored-by: Yoann Rodière <[email protected]>
|
Merging for first pass legal review. |
@gavinking and @yrodiere .. does this suffice for an initial introduction of terms?
There will need to be additional edits between Members & Council to round these out..