Hi friends,
I am writing on behalf of the Community Council with some updates.
We wanted to be in touch and let folks know what we have been up to since the recent election.
We have had several meetings with the new Council (Alison, qbi, Linda, Hiro, Gunner). We are enjoying working together.
In the near term, we are prioritizing the drafting of policies and procedures for the Council.
Our plan is to draft these sequentially and then ask for community input once we think specific policies and procedures are ready for feedback.
Procedures we are drafting include case handling, Council operations (e.g. when and how we meet), and Council elections.
Policies we are drafting include conflict of interest, operational security (in particular what we store and where), and confidentiality (what is and is not confidential).
We welcome anyone interested to reach out to any or all Council members if you have input, questions or concerns you would like to share
We'll continue to update the community at least once a month.
thanks,
On Tue, Jun 27, 2017 at 12:40:19AM +0200, Jens Kubieziel wrote:
We welcome anyone interested to reach out to any or all Council members if you have input, questions or concerns you would like to share
Thanks Jens! I was thinking about this topic recently in the context of some other policies I was helping to draft, where some folks wanted to put in guidance for how the community council should approach problems, and I pushed back mostly because guidance for the community council didn't make sense in those particular policy documents.
But it made me think that it would be great to have the new council take some notes for itself, for us, and for future councils, about how it approaches problems. Not to make those notes force the same behavior on future councils (or even on this council in future decisions), but so we can start accumulating a body of knowledge of how things have gone (including what worked and what didn't) in the past.
Otherwise we end up in the situation where a few people remember how things used to be, which means access to that information is not as widespread as it could be, and also their memories diverge over time.
It sounds like you have thought of all of this too, so, great. :) Let us know how we can help.
--Roger
On Tue, Jun 27, 2017 at 12:40:19AM +0200, Jens Kubieziel wrote:
Hi friends,
Hi Jens, Council,
I am writing on behalf of the Community Council with some updates.
We wanted to be in touch and let folks know what we have been up to since the recent election.
Thanks!
We have had several meetings with the new Council (Alison, qbi, Linda, Hiro, Gunner). We are enjoying working together.
In the near term, we are prioritizing the drafting of policies and procedures for the Council.
Our plan is to draft these sequentially and then ask for community input once we think specific policies and procedures are ready for feedback.
This is great. Can you give us a hint as to which policy and/or procedure you started working on?
Procedures we are drafting include case handling, Council operations (e.g. when and how we meet), and Council elections.
And can you clarify what you mean by "Council elections"? Isn't this already described in the voting procedures we voted on earlier this year?
Policies we are drafting include conflict of interest, operational security (in particular what we store and where), and confidentiality (what is and is not confidential).
Thanks for working on these important documents.
- Matt
Hi Matt,
Replying on behalf of the Community Council here.
Matthew Finkel:
This is great. Can you give us a hint as to which policy and/or procedure you started working on?
See below! We listed them in the next sentence.
Procedures we are drafting include case handling, Council operations (e.g. when and how we meet), and Council elections.
And can you clarify what you mean by "Council elections"? Isn't this already described in the voting procedures we voted on earlier this year?
The current policies specify how voting takes place, and how Councilmembers can run for Council and get elected. They are missing some other important procedures, like how the question and answer period should run. We all saw a need to fill in some of these blanks after the last election became a little chaotic.
Policies we are drafting include conflict of interest, operational security (in particular what we store and where), and confidentiality (what is and is not confidential).
Thanks for working on these important documents.
No problem! We'll share them out when we've got something worth sharing. :)
Alison (on behalf of the CC)
- Matt
On Mon, Jul 03, 2017 at 01:13:00PM +0000, Alison wrote:
Hi Matt,
Replying on behalf of the Community Council here.
Matthew Finkel:
This is great. Can you give us a hint as to which policy and/or procedure you started working on?
See below! We listed them in the next sentence.
Heh. Okay, yeah... I'm sure I had a good reason for asking this, but I don't remember at this point :)
Procedures we are drafting include case handling, Council operations (e.g. when and how we meet), and Council elections.
And can you clarify what you mean by "Council elections"? Isn't this already described in the voting procedures we voted on earlier this year?
The current policies specify how voting takes place, and how Councilmembers can run for Council and get elected. They are missing some other important procedures, like how the question and answer period should run. We all saw a need to fill in some of these blanks after the last election became a little chaotic.
Cool, that's great! Thanks for giving some more info.
Policies we are drafting include conflict of interest, operational security (in particular what we store and where), and confidentiality (what is and is not confidential).
Thanks for working on these important documents.
No problem! We'll share them out when we've got something worth sharing. :)
Looking forward to it :)
<3
Alison (on behalf of the CC)
- Matt
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project@lists.torproject.org