Re: [tor-bugs] #20923 [Internal Services/Service - lists]: Please create tor-employees mailing list

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#20923: Please create tor-employees mailing list
-----------------------------------------------+---------------------
 Reporter:  ewyatt                             |          Owner:  qbi
     Type:  defect                             |         Status:  new
 Priority:  Medium                             |      Milestone:
Component:  Internal Services/Service - lists  |        Version:
 Severity:  Normal                             |     Resolution:
 Keywords:                                     |  Actual Points:
Parent ID:                                     |         Points:
 Reviewer:                                     |        Sponsor:
-----------------------------------------------+---------------------

Comment (by lunar):

 When we [[wiki:org/meetings/2015SummerDevMeeting/MembershipProcess|drafted
 the first ideas of a formal membership]] a bit more than a year ago, I
 advocated for such a list.

 Very minor point: if contractors are going to be on this list, I don't
 think it's wise to call it “tor-employees”. It could maybe be used against
 Tor to say that contractors are disguised employees.

 The main rationale is: without such a list, you make it automatic that
 every contractors or employees automatically become members of the
 project.

 But what I wanted was: it should become a member of the Tor community
 because you get hired or contracted by Tor the company. Because they work
 on different time scales, it seems to make more sense to make them
 different processes. If announcements regarding employees and contractors
 use the communication channels that are dedicated to project members (who
 have been through a community-run membership process), you require
 contractors or employees to be on these communication channels. That would
 make them exempt of the community process (bad in my opinion) or have
 special temporary status (bad in my opnion).

 Meanwhile, I need to say that with the current trend where, as a
 volunteer, I have very little idea on what the company is doing, this
 feels quite worrying. Almost every week there's a new email which makes me
 think “oh, I didn't even knew we needed to make such a decision” or “oh, I
 didn't even knew we had an open position”.

 So I guess I still support a separate list, but without a company that
 takes more input from the community, or a way for the community to have
 better control over the company, this is likely going to reinforce the
 exclusion of members of the community who are not contractors or
 employees.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20923#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs