[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3158 [Company]: Need a clearer policy about who gets ldap accounts
#3158: Need a clearer policy about who gets ldap accounts
---------------------+------------------------------------------------------
Reporter: arma | Owner: phobos
Type: defect | Status: new
Priority: normal | Milestone:
Component: Company | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
Comment(by sjmurdoch):
Replying to [comment:4 rransom]:
> But longer-term, we should set up a separate community-git.tpo (or
similar)
An alternative we could consider is to set up a !GitHub "organization"
under which we can put community-run projects which are somehow part of
the Tor ecosystem. People with !GitHub accounts could be easily added to
the access-control-lists ("teams") by a Tor administrator and people can
fork projects without having to ask for permission.
One downside of this (and the community-git.tpo) approach is to
differentiate between Tor Inc. and non-Tor Inc. projects. Another which
only affects using !GitHub is that it could go down permanently or
temporarily. We could mitigate this problem by having automated backups.
Setting up an organization is free for open-source projects and you get
0.3 Gb for repositories (but this can be extended if a case is made). I've
done it for the CTSRD TESLA project: https://github.com/CTSRD-TESLA/
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3158#comment:6>
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