On Sat, Nov 15, 2014 at 12:18 PM, john_perry_usm <john.pe...@usm.edu> wrote: > William > >> Understand, there are also consequences to not having some sort of >> successful code of conduct. These include: >> >> 1. Continuing to lose talented Sage developers specifically because >> they do not feel comfortable with the tone of the lists, and > > > Can you give an example of this, even if vaguely? I don't read every > conversation on the lists, but in my personal experience, the community has > been very supportive, even when I'm an idiot. (Sometimes you have been > supportive *especially* when I'm an idiot.) I do see a lot of > rough-and-tumble when there are disagreements on some things, but I thought > they were expressed civilly, for the most part.
I don't think I should, though if anybody reading this wants to give an example, I encourage them. > > I concede that I know of two reasons why some people grow discouraged > developing with Sage, but neither seems a consequence of the tone of the > lists. > > (1) When switching development to Git, it became harder for the less > talented to contribute. I'm not the only one who encountered a complete > recompilation of Sage when reviewing a new ticket -- even one that didn't > touch Cython. See, e.g., some of my comments on ticket #17298, where at one > point I wrote, "I can't afford to tie up my installation for 2 hours of > compilation every time a few lines of Python code change." > > This used not to occur in Mercurial. That certainly discourages me, in part > because I'm not talented. Admittedly, I wasn't contributing much to start > with ;-) though I did have a pretty good series of tickets w/Nathann last > year. (Thanks, Nathann!) +1 This is a HUGE problem and you're definitely not the first to complain to me about it. Back in the old days I spent a huge amount of time ensuring this didn't happen, because once at an Arizona Winter School I remember seeing this frustrated Russian grad student trying to do "sage -br" and suffering very badly -- it really left an impression on me. There's genuine negative fallout from the git transition, which negatively impacts developer productivity, unfortunately... > (2) A speaker at one conference mentioned the pickiness (IIRC) of a *major* > Sage developer as discouraging development, and a particular subsystem of > great interest to that speaker was languishing as a result. Was this mentioned when the speaker was publicly speaking? > > I might have misunderstood #2; perhaps the speaker meant in fact the tone > that developer took, but I don't think so. Even if it was the tone, that > returns to the question I raised before: if a major developer is a problem, > would the powers that be exclude the person's patches? Especially as the > tone people take in some conversations can be very culturally based. > > john perry > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
