Page MenuHomeFreeBSD

Update to the 'hats' policy
ClosedPublic

Authored by matthew on Jun 13 2015, 2:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 10 2024, 1:26 AM
Unknown Object (File)
Feb 29 2024, 12:57 PM
Unknown Object (File)
Dec 28 2023, 9:21 AM
Unknown Object (File)
Dec 24 2023, 11:24 AM
Unknown Object (File)
Nov 15 2023, 1:12 AM
Unknown Object (File)
Nov 11 2023, 5:20 AM
Unknown Object (File)
Nov 9 2023, 7:28 PM
Unknown Object (File)
Nov 8 2023, 11:11 PM
Subscribers

Details

Reviewers
glebius
gnn
Group Reviewers
Core Team
Commits
rD46906: Update to the hat policy.
Summary

As discussed at the restaurant meeting at BSDCan.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

matthew retitled this revision from to Update to the 'hats' policy As discussed at the restaurant meeting at BSDCan..
matthew updated this object.
matthew edited the test plan for this revision. (Show Details)
matthew added a reviewer: Core Team.
matthew retitled this revision from Update to the 'hats' policy As discussed at the restaurant meeting at BSDCan. to Update to the 'hats' policy.
matthew updated this object.

Fix typo and remove extraneous whitespace.

Ooops. Didn't mean to include administration.xml

This revision is now accepted and ready to land.Jun 15 2015, 9:17 AM
gnn added a reviewer: gnn.
gnn added a subscriber: gnn.

Change "should appoint" to "must appoint" It may not happen but we want the stick.

Other than that, I approve.

emaste added inline comments.
internal/hats.xml
55–57 ↗(On Diff #6167)

I think we should be a bit stronger in encouraging people to rotate through. We should have some guidance as to under what conditions a role-holder would continue -- as written it seems odd to suggest the limit is two terms, but there's no limit. Maybe we just add "in exceptional circumstances" or such?

It is expected that each hat will serve for no more than two complete two-year core terms. In exceptional circumstances role-holders may continue for longer.

matthew edited edge metadata.

should appoint -> must appoint

Strengthen the encouragement to rotate hats.

This revision now requires review to proceed.Jun 17 2015, 6:04 AM
hrs added inline comments.
internal/hats.xml
36 ↗(On Diff #6258)

This "they" is a bit difficult to understand for me. Does this mean a group of individuals on the active? An individual may serve if core approves the hat. And he may keep working as long as he is willing to continue and core does not oppose it. So I think approval by core should come first in the bullet list, and then continuation conditions do. The descriptions after the list are in this order.

internal/hats.xml
36 ↗(On Diff #6258)

'They' in this case refers to the individual mentioned in the previous paragraph. It's pretty standard English.

The point about re-ordering the items is well put though and I'll certainly re-order as you suggest -- but when I do so "They" will become ambiguous (Core or the Individual?) so I guess I'll address your first point as well.

matthew edited edge metadata.

Following hrs' comments

internal/hats.xml
36 ↗(On Diff #6270)

I guess singular they is perhaps confusing to non-native speakers. "The appointment" might work here, although maybe not relevant with a broader change.

Comments from Peter:

  • Simplify the mapping of hat terms to core terms.
  • Distinguish between volunteers and paid staff.

s/a/the/ in a few places and note that a core term is two years.

Whitespace changes according to igor(1)

I think this is ready to commit. If you have any last comments please add them soon. Otherwise I'll commit in a day or so's time.

This revision was automatically updated to reflect the committed changes.