Add to the 'policies' page on the website
Details
Details
- Reviewers
bcr jhb - Group Reviewers
Core Team - Commits
- rD51812: Update wording to highlight that FreeBSD Project Members are meant to
rD50324: Add documentation describing the new 'FreeBSD Project Member' status,
rD50195: Revert r50193 and r50194: this is all still under discusion and not
rD50194: Fix ommision from earlier commit:
rD50193: Add documentation about 'FreeBSD PRoject Associates'
Diff Detail
Diff Detail
- Repository
- rD FreeBSD doc repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
A textual nit, nothing big.
| en_US.ISO8859-1/htdocs/internal/associates.xml | ||
|---|---|---|
| 41 ↗ | (On Diff #27494) | s/the way/the same way/ |
Comment Actions
Rename 'associates.xml' to 'members.xml'
Reword the document in terms of 'Project members' where 'Committers'
are that sub-set of members that have commit bits.
| en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 18 ↗ | (On Diff #27898) | I think you can drop this paragraph entirely. |
| 32 ↗ | (On Diff #27898) | I would simplify this (and use some of the language from your first paragraph above) to say: Committers are members who have been granted commit access (a "commit bit") to one or more of the Project's repositories. Committers are expected... |
| 38 ↗ | (On Diff #27898) | Aren't all members required to abide by the CoC? Also, in the original language, this list of requirements about licensing was required of associates as well. I think perhaps instead we should have a separate itemized list of "obligations" to match the list of "benefits" and move everything starting with "comitters are expected..." into that section and have it apply to all members. That would mean structuring this as: A FreeBSD Project Member is... Comitters are members who have been granted commit access... <h2>Member Responsibilities</h2> <li>Contributed material adheres to project's standards and practices. <li>Contributed material is correctly attributed to its authors <li>Contributed material has appropriate licensing <h2>Member Benefits</h2> /* existing "receives" list */ <h2> Committer Benefits</h2> In addition to member benefits, active committers can vote. Members MUST create SSH and PGP... |
Comment Actions
Address points raised by jhb:
- Drop the introductory paragraph. This (or something like it) can be the preamble to the announcement to announcement message rather than being part of the definitive document.
- Simplify and reorganise the structure. Explain what all Member benefits are, what all Members responsibilities are in common, and add some text to explain the additional benefits and responsibilities of Committers.
- Attempt to be consistent in capitalizing terms like 'Project', 'Member', 'Committer' etc.
- Fix the <!ENTITY title "FreeBSD Project Members"> tag.
Comment Actions
Thanks, a few minor suggestions
| en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 32 ↗ | (On Diff #28100) | Perhaps drop this paragraph now? |
| 44 ↗ | (On Diff #28100) | Tweak: "Committer Benefits:" to match formatting of earlier <h2> for Member Benefits. |
| 50 ↗ | (On Diff #28100) | Trailing colon here as well? |
| 62 ↗ | (On Diff #28100) | I would drop "in exactly the same way as Committers have done previously" as that detail only matters temporarily. |
| 74 ↗ | (On Diff #28100) | s/designate, that/designate to/. I think this reads a bit clearer as if you drop the clause in commas you get "Core ... should review.." |
| 77 ↗ | (On Diff #28100) | For this last sentence perhaps "There is no formal definition of inactive accounts. Core and the designated teams will use their own discretion to determine inactivity." |
| en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 32 ↗ | (On Diff #28100) | I disagree here -- the @FreeBSD.org address is probably the most attractive benefit of becoming a Project Member -- it's the one thing that the rest of the world will be able to see. It's the public acknowledgement of their contribution to the Project. |
Comment Actions
Address some more commments from jhb:
- Make the <h2> heading format more consistent
- Reword the sentence about core delegating the rights to award Member status to other groups.
- Drop reference to previous status in the requirement for SSH and PGP keys.
| en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 32 ↗ | (On Diff #28100) | To be clear, by "paragraph" I mean the literal "<p>All members receive:</p>" as it is redundant with the heading in the line above, not to remove the list of benefits. |
| en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 32 ↗ | (On Diff #28100) | Oh, I see. Sorry for the misunderstanding. Yes, I guess that line could go. |
| head/en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 18 | "has made a notable contribution" (past tense) or "contributes" (present tense)? We may not be able to clearly articulate how to measure currency of contribution for non-committing members (i.e., there's no simple equivalent to "you must have committed within the last N months"), but isn't the intention that current members are currently contributing to the Project? | |
| head/en_US.ISO8859-1/htdocs/internal/members.xml | ||
|---|---|---|
| 18 | Hmm... it really should be both. Being awarded "Project Member' status is a recognition of past contributions, but it's also a reward for on-going contributions -- the status should eventually lapse for someone that ceases to contribute. | |
Comment Actions
Note that 'FreeBSD Project Members' are expected to be currently
active contributors.