Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread kcrisman
> > Once more, the rules make a point to enforce politeness but they seem > to avoid things like having the respect to answer a honest question. > > Collated for ease of reply, though there were also implicit questions and examples of what was meant in the email. - what is our commitment to

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread Nathann Cohen
Hello guys, Once more, the rules make a point to enforce politeness but they seem to avoid things like having the respect to answer a honest question. Could we thus have an answer to the ones aked by Therry ? Not ignoring anybody is also part of elementary "friendliness". Nathann On 25 Novembe

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread kcrisman
> > > [Edited because this should be a family show] > > I was trying to be sarcastic and make visible a risk for machismo or > androcracy that could follow from establishing some kind of competition > within the community. > > I realize that the way i wrote those two lines somehow strengthen

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread Thierry
> > [Edited because this should be a family show] I was trying to be sarcastic and make visible a risk for machismo or androcracy that could follow from establishing some kind of competition within the community. I realize that the way i wrote those two lines somehow strengthen such theses. I am

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread Thierry
Hi, On 24/11/2014 15:06, kcrisman wrote: > It seemed to me that this was an attempt to provide some slightly less > arbitrary measure than "the BDFL and whoever he likes" or "the release > manager and his friends". I am pretty sure that there were calls to > perhaps find a different measure. Natur

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread kcrisman
> > Trac tickets and comments, however, are public. Thus, among the many > good questions raised by Thierry which deserve an answer, I am also > interested by the answer to the following question: > > I consider myself as a Sage developer, i have never heard about this > initiative before. Cou

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-24 Thread Nathann Cohen
Hello, > Realistically, that is not how we operate. Somebody opens a ticket, works on > it, and then posts the result for review. I have found quite a number of > random failures on the buildbot (tagged by the random_fail keyword: > http://trac.sagemath.org/query?keywords=~random_fail) and nobody

Re: [sage-devel] Code of Conduct (missing dependencies)

2014-11-23 Thread Vincent Delecroix
> For example: > > - what is our commitment to free software ? > - should we collaborate (fund, advertise,...) with closed proprietary > software ? > - how do we take decisions (equality, transparency, collaboration, taking > care of minorities,...) ? > - are there some reserved territories wit

Re: [sage-devel] Code of Conduct

2014-11-20 Thread Francois Bissey
> On 21/11/2014, at 18:54, William Stein wrote: > > On Thu, Nov 20, 2014 at 9:51 PM, Francois Bissey > wrote: >> I have abstained from the thread but read quite a bit of it and I think >> that the idea there are really two issues is correct. >> >> I have been thinking for a while but abstained

Re: [sage-devel] Code of Conduct

2014-11-20 Thread William Stein
On Thu, Nov 20, 2014 at 9:51 PM, Francois Bissey wrote: > I have abstained from the thread but read quite a bit of it and I think > that the idea there are really two issues is correct. > > I have been thinking for a while but abstained because there is a lot of > stuff already on the thread and w

Re: [sage-devel] Code of Conduct

2014-11-20 Thread Francois Bissey
I have abstained from the thread but read quite a bit of it and I think that the idea there are really two issues is correct. I have been thinking for a while but abstained because there is a lot of stuff already on the thread and we are at a stage where the signal/noise is quite low. So anyway si

Re: [sage-devel] Code of Conduct

2014-11-18 Thread Anne Schilling
On Saturday, November 15, 2014 2:10:04 PM UTC-8, P Purkayastha wrote: > Yes. Typically, they ban the user for a period of time. The violations are > dealt with on a case-by-case basis. It seems quite a few requests (code of > conduct violations, and otherwise) have piled up in > http://forums.g

Re: [sage-devel] Code of Conduct

2014-11-17 Thread Ben Salisbury
> > [X ] Yes, this is a great idea. About time! > To a newcomer, some of the posts may make the Sage community look aggressive and end up steering them in another direction. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fr

Re: [sage-devel] Code of Conduct

2014-11-15 Thread P Purkayastha
On Sun Nov 16 2014 at 12:44:39 AM Anne Schilling wrote: > On 11/15/14 7:32 AM, P Purkayastha wrote: > > > > > > On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby > Microwave Ltd) wrote: > > > > On 13 November 2014 18:48, Volker Braun > wrote: > > > and welcome every

Re: [sage-devel] Code of Conduct

2014-11-15 Thread Dr. David Kirkby (Kirkby Microwave Ltd)
On 15 November 2014 16:44, Anne Schilling wrote: >> > Code of Conduct > > Thanks for the links to the guidelines. It is interesting to see how other > communities handle this. > Dave's question was how situations will be handled when a violation occurs or > that are reported. > Does your com

Re: [sage-devel] Code of Conduct

2014-11-15 Thread Anne Schilling
On 11/15/14 7:32 AM, P Purkayastha wrote: > > > On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby > Microwave Ltd) wrote: > > On 13 November 2014 18:48, Volker Braun > wrote: > > and welcome everyone to > > vote on it. > > > > > > Code of Conduct >

Re: [sage-devel] Code of Conduct

2014-11-15 Thread P Purkayastha
On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > > On 13 November 2014 18:48, Volker Braun > > wrote: > > and welcome everyone to > > vote on it. > > > > > > Code of Conduct > > --- > > > If you believe someone is violating the c

Re: [sage-devel] Code of Conduct

2014-11-15 Thread John Cremona
It had never occurred to me that such a thing would ever be necessary. Any exclusions should be collective decisions not by some oligarchy, and should allow for reinstatement if the perpetrators are contrite. John On 15 November 2014 08:49, Andrew wrote: > In an ideal world I think that a code o

Re: [sage-devel] Code of Conduct

2014-11-15 Thread Andrew
In an ideal world I think that a code of conduct would not be necessary. Sadly, the world is not ideal. I think that SImon's example of what happened with the German translation project is a great example of why it would be good to have a code of conduct: some one's comments turned him off work

Re: [sage-devel] Code of Conduct

2014-11-14 Thread Dr. David Kirkby (Kirkby Microwave Ltd)
On 13 November 2014 18:48, Volker Braun wrote: > and welcome everyone to > vote on it. > > > Code of Conduct > --- > If you believe someone is violating the code of conduct, we ask that you > report it by emailing sage-ab...@googlegroups.com. The group administrators > will consider t

Re: [sage-devel] Code of Conduct

2014-11-14 Thread Simon King
Hi William, Am Donnerstag, 13. November 2014 20:00:58 UTC+1 schrieb William: > > [ ] No, I greatly value the freedom to spout offensive profanity, and > will fork Sage in frustration if there is such a code. I think you misunderstand the motivation for not wanting any published code of conduct

Re: [sage-devel] Code of Conduct

2014-11-14 Thread rjf
To the extent that a code of conduct looks like an attempt to limit freedom of speech, it may be counterproductive. It is possible to legislate "politeness" by moderating newsgroups. I suppose it is possible to resolve disagreements about the course of open software development by (a) achieving c

Re: [sage-devel] Code of Conduct

2014-11-13 Thread john_perry_usm
On Friday, November 14, 2014 3:55:34 AM UTC+1, Travis Scrimshaw wrote: > > Bullying can get so bad that the teachers need to step in and enact the > correct punishment. > ...yet, in my experience, they usually don't, and often because the bullies are likable, or socially influential (e.g., son o

Re: [sage-devel] Code of Conduct

2014-11-13 Thread Anne Schilling
I agree with Travis that it is good to have guidelines that one can point people to if discussions escalate. I agree that it is best to try to work things out mutually, but this does not always seem possible. So ... [X ] Yes, this is a great idea. About time! Best, Anne -- You received thi

Re: [sage-devel] Code of Conduct

2014-11-13 Thread Travis Scrimshaw
I believe we need to have such a code-of-conduct posted stating the manner in which we should act. Like Jan and Simon, this should not be some strict set of rules that gets referenced every time someone feels another developer is out of line. By publishing such a code, we give explicit guide

Re: [sage-devel] Code of Conduct

2014-11-13 Thread kcrisman
> > > good to always aspire to better ourselves. Some of the Sage developers > who > > are better with words than me went ahead and stole a lot more, mostly > from > > Fedora (http://fedoraproject.org/code-of-conduct) and Django > > (https://www.djangoproject.com/conduct), to formulate a "Cod

Re: [sage-devel] Code of Conduct

2014-11-13 Thread Jan Groenewald
Hi Great to have in place to refer to as an educational guideline (not to be abused as strict rules). It could also mention core values of Libre Software, with additional emphasis on scientific transparency. Regards, Jan On 13 November 2014 21:00, William Stein wrote: > On Thu, Nov 13, 2014 a

Re: [sage-devel] Code of Conduct

2014-11-13 Thread William Stein
On Thu, Nov 13, 2014 at 10:48 AM, Volker Braun wrote: > Can we create an environment... where character matters, hard work is > respected, humility is valued, and support for one another is unconditional? > > I admittedly stole that quote, but only because I wholeheartedly agree it is > good to al

[sage-devel] Code of Conduct

2014-11-13 Thread Volker Braun
Can we create an environment... where character matters, hard work is respected, humility is valued, and support for one another is unconditional? I admittedly stole that quote, but only because I wholeheartedly agree it is good to always aspire to better ourselves. Some of the Sage developers