X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Sun, 8 Sep 2013 17:50:59 -0400 Message-Id: <201309082150.r88Loxd3023541@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com CC: peter AT peter-b DOT co DOT uk, geda-admins AT lists DOT launchpad DOT net, geda-user AT delorie DOT com, geda-developers AT lists DOT launchpad DOT net In-reply-to: <522CE8ED.2040200@jump-ing.de> (message from Markus Hitter on Sun, 08 Sep 2013 23:15:25 +0200) Subject: Re: [geda-user] Re: [Geda-developers] git.geda-project.org permissions change References: <87fvtffapt DOT fsf AT harrington DOT peter-b DOT co DOT uk> <201309082104 DOT r88L4Rx2003804 AT envy DOT delorie DOT com> <522CE8ED DOT 2040200 AT jump-ing DOT de> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > To date I still wait for somebody showing me an incident where harm > actually happened. The goal is to prevent harm, not react to it. I really want to grow geda's developer community, but there's always a risk with new people, and the risk grows as the community grows. My current policy about new developers is to err on the side of them helping us, which further increases the risk. People who have earned more priviledges can easily be given them. > Instead, Peter told us he actually uses exactly the workflow I use > myself, outlined a week ago, In his personal repo, not the master repo. > No problem at all. I couldn't put in the amount of time I liked to put > in anyways. The list of open source projects I'm participating in is > simply too long and getting rid of PCB will do me a favour. > > At times is was a joy to work with you, folks. I wish you all the best! Sorry to see you go. I was hoping you'd ask to become one of the pcb admins, instead of just leaving, but I certainly understand the time issue ;-)