Opened 9 months ago

Last modified 4 days ago

#22079 new project

Community governance documents

Reported by: alison Owned by: alison
Priority: Medium Milestone:
Component: Community Version:
Severity: Normal Keywords:
Cc: community-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


This is the parent ticket for organizing ideas and drafts for community governance documents.

Child Tickets

#22082closedalisonRefine membership guidelines draft and submit proposal to tor-internal@Community
#22511newTor Code of ConductCommunity

Change History (6)

comment:1 Changed 2 months ago by alison

Amendments needed to existing documents:

  • Change Community Council guidelines to say that a person must be a Core Contributor and remain a Core Contributor in order to stay on the Council.
  • Change membership guidelines to say that you need six months of activity to become a core contributor, but activity within the last 12 months is enough to stay a core contributor.
  • Separate membership secretary/account manager roles into two separate roles:

administer the list of core contributors, and
make sure we are following the core contributor process.

comment:2 Changed 2 months ago by atagar

For what it's worth concerning the 'split secretary/account manager roles' I think Tim suggested that to reduce load on me, but as discussed on the thread that wouldn't be helpful.

comment:3 Changed 2 months ago by atagar

Oh, also if you're collecting amendment ideas then something from May...

Speaking of which, if we want to have a Q&A as part of next year's council
selection someone should write a proposal for it. The vote we just had
made it clear there's quite a few differing views on how this should be

comment:4 Changed 2 weeks ago by alison

what happens when a councilmember resigns?

the current policy says we can:

  • continue with a 4 person council until terms end on March 31 (our policy lets us have a 3, 4 or 5 member council)
  • hold community council elections early (we need 5 people to ask for this)

maybe instead we should revise the CC guidelines to have a countback, which means filling vacancies with the person who received the next highest votes.

comment:5 Changed 6 days ago by teor

I'd like us to make new and revised documents more readable. This helps people who know fewer English words. (Most people I have talked to prefer simple English over translations.)

Here is a process that seems to work so far:

  1. Get permission to copy the text into an online readability checker. Remove comments and names first!
  2. Use the readability checker to highlight long words and long sentences.
  3. Put the highlights into the document.
  4. Ask for help to rewrite them.

comment:6 Changed 4 days ago by teor

Someone found a better readability site:

It does live checking. And it doesn't have usage limits.

Note: See TracTickets for help on using tickets.