Re: [sage-devel] Re: mailing list administration

[Luca De Feo]

> Should we start a process of nominating/electing moderators?

Before that, we should decide what the process is. That's something
that might be complicated to do via email (remember what happened with
the code of conduct).

In my opinion, a Sage Days completely dedicated to this kind of issues
would be a better venue to have this kind of discussion, provided we
manage to get enough people to come.

> What did just happen to MariaDB? (I am asking as I have no glue what you
> speak about; Google brings up something, but this all seems not relate
> with your "just".)

http://www.infoworld.com/article/3109213/open-source-tools/open-source-uproar-as-mariadb-goes-commercial.html

But see also:

http://www.theregister.co.uk/2016/08/24/monty_interview/

Luca

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [Yet again] Sage's R vs system's R

[kcrisman]

> ... which was less of a problem with our "legacy" spkgs, as you in many 
> cases could simply install an older or a more recent version when 
> available /somewhere/, or even easily create your own, just replacing 
> the upstream version in the src/ folder. 
>
> More or less just out of curiosity, did we ever upgrade R because of 
> bugs in R (besides build/installation issues) R-thru-Sage users 
> complained about? 
>
>
R is pretty stable in its core set, so I would find that highly unlikely. 
 However, we have definitely upgraded R because without having the latest R 
one would not have access to many (MANY) of the R user packages.  R is 
pretty aggressive on allowing projects to specify e.g. R version > 2.10 to 
function properly, and so we've had to upgrade for that reason.  I guess 
that is not a bug, though.
 

> Closer on topic, is there urgent need to upgrade our current version of 
> R?  (The 'configure' bug I reported upstream May last year is by the way 
> still in 3.3.1, although the patch I submitted is pretty trivial.) 
>

Like Maxima and others, in principle it would be great to have "rolling" 
upgrades that semi-automatically happened once passing some tests (in R's 
case, including graphics, maybe).  Which presumably supports the general 
notion of decoupling things better? 

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: mailing list administration

[Daniel Krenn]

On 2016-08-25 10:01, Luca De Feo wrote:
> [...] Even though you do not have the power to do the same with Sage
> as what just happened with MariaDB [...]

What did just happen to MariaDB? (I am asking as I have no glue what you
speak about; Google brings up something, but this all seems not relate
with your "just".)

Daniel

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [Yet again] Sage's R vs system's R

[Jean-Pierre Flori]

By the way I've got all we need for the upgrade. Just got to put it into a 
branch.

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [Yet again] Sage's R vs system's R

[leif]

kcrisman wrote:
> 
> I think maybe even a better distinction than "sage-the-distro" is to
> call it "SageMath, the Application".  As far as users of the
> application are concerned I agree the it should have the goal of being
> a general purpose stack of mathematics software.  For short I'll call
> the application/distribution SageMath in (camel-case) and the Python
> package "sage" since that's what the actual package is called.
> 
> But treating that larger software stack, and the `sage` Python package
> as one in the same makes development on the latter more difficult, and
> probably ultimately the former as well.  For example--continuing with
> R as the test particle--say I'm a SageMath user who makes heavy use of
> R for my statistics, and like being able to use R with sage.  What
> happens when a critical bug is fixed in R, and a new patch release
> comes out (something Sage, by the way, doesn't even have but should).
> How do I get that patch release?  Well I have to wait for a new
> version of sage (the package, and everything else that comes with it).
> That might include a bunch of other new dependencies that I didn't
> really think I needed.  Possibly even API breakage elsewhere (though
> fortunately sage itself is normally pretty good about that).
> 
> 
> Yes, I agree that is a very significant issue and of course has been for
> some time (with respect to many, many packages, I couldn't even list
> them all for you).

... which was less of a problem with our "legacy" spkgs, as you in many
cases could simply install an older or a more recent version when
available /somewhere/, or even easily create your own, just replacing
the upstream version in the src/ folder.

More or less just out of curiosity, did we ever upgrade R because of
bugs in R (besides build/installation issues) R-thru-Sage users
complained about?

Closer on topic, is there urgent need to upgrade our current version of
R?  (The 'configure' bug I reported upstream May last year is by the way
still in 3.3.1, although the patch I submitted is pretty trivial.)


-leif


-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] mailing list administration

[David Joyner]

On Thu, Aug 25, 2016 at 10:33 AM, kcrisman  wrote:
>
>
>>> > I deleted it as flame bait.   I'm sick of people using sage-devel as a
>>> > forum to attack others
>>>

I have set Nathann to moderated posting on sage-devel.

IMHO, his last several posts were flame-bait and go in sage-flame not
sage-devel.

>>> I'm sick of it too. But this kind of unilateral actions only fuels the
>>> flame, it does not extinguish it.
>>>
>>> Especially given your position as a CEO of a for profit company, William.
>>> Even though you do not have the power to do the same with Sage as what just
>>> happened with MariaDB, the community is entitled with a legitimate
>>> (unfounded, I believe) fear of SageMath Inc. trying to do something similar
>>> at some point. This kind of unilateral censorship, although well
>>> intentioned, can only spark more of those flames.
>>
>>
>> If people really want flame bait on this list, then I am going to stop
>> reading sage-devel.
>
>
> It's a tough call here, because in a technical sense it was accurate and not
> attacking, so I would be inclined to have handled it via a "This is flame
> bait" response message (and indeed perhaps moving to sage-flame, if that's
> possible).  Even though I think regular readers of this know it was probably
> intended in some manner as an attack, for a first-time reader this might not
> have been clear.  But the lack of context (despite the link provided) is
> definitely problematic.  It would have been nice if someone other than the
> intended victim had been able to deal with the post, though, as it shouldn't
> have been his job. If having more moderators helps with that it's fine.  But
> will there be enough moderators?
>
>
> --
> 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 https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] mailing list administration

[kcrisman]

> I deleted it as flame bait.   I'm sick of people using sage-devel as a 
>> > forum to attack others
>>
>> I'm sick of it too. But this kind of unilateral actions only fuels the 
>> flame, it does not extinguish it.
>>
>> Especially given your position as a CEO of a for profit company, William. 
>> Even though you do not have the power to do the same with Sage as what just 
>> happened with MariaDB, the community is entitled with a legitimate 
>> (unfounded, I believe) fear of SageMath Inc. trying to do something similar 
>> at some point. This kind of unilateral censorship, although well 
>> intentioned, can only spark more of those flames.
>>
>
> If people really want flame bait on this list, then I am going to stop 
> reading sage-devel.
>

It's a tough call here, because in a technical sense it was accurate and 
not attacking, so I would be inclined to have handled it via a "This is 
flame bait" response message (and indeed perhaps moving to sage-flame, if 
that's possible).  Even though I think regular readers of this know it was 
probably intended in some manner as an attack, for a first-time reader this 
might not have been clear.  But the lack of context (despite the link 
provided) is definitely problematic.  It would have been nice if someone 
other than the intended victim had been able to deal with the post, though, 
as it shouldn't have been his job. If having more moderators helps with 
that it's fine.  But will there be enough moderators?
 

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [Yet again] Sage's R vs system's R

[aishen]

There is a SAGE accounting with is very interfering if you don't write 
sagemath in a research !

Le samedi 20 août 2016 16:09:20 UTC+2, Emmanuel Charpentier a écrit :
>
> While trying my hand  at porting 
> R 3.3.1 to Sage (needs_review, by the way), I found this in the current R 
> Installation and Administration manual 
>  :
>
> > C.8 Cygwin
> > 
> > The 32-bit version has never worked well enough to pass R’s make check, 
> and residual support from
> > earlier experiments was removed in R 3.3.0.
> > 
> > The 64-bit version is completely unsupported.
>
> Maybe we should consider to have an interface to system's R rather than 
> our own version (and therefore make it an optional package)
>
> It would be more difficult (but not impossible) to offer the same kind of 
> access to an external R as to a tightly-knit R. I'm thinking graphics, 
> notebook(s) integration, etc...
>
> OTOH, the existence of a good R interface (Rpy2) could make things easier. 
> The largest problem that one can forecast is, of course, backwards 
> compatibility in existing programs.
>
>
> On the third hand, what can be said if the future of a native Windows port 
> of Sage, which could do without Cygwin monkeying ? I understand that a) 
> it's not really easy and b) some significant advances have been made 
> recently...
>
> Ideas, suggestions, etc ?
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: mailing list administration

[Dima Pasechnik]

On Thursday, August 25, 2016 at 9:01:54 AM UTC+1, Luca De Feo wrote:
>
> > I deleted it as flame bait.   I'm sick of people using sage-devel as a 
> > forum to attack others
>
> I'm sick of it too. But this kind of unilateral actions only fuels the 
> flame, it does not extinguish it.
>
> Especially given your position as a CEO of a for profit company, William. 
> Even though you do not have the power to do the same with Sage as what just 
> happened with MariaDB, the community is entitled with a legitimate 
> (unfounded, I believe) fear of SageMath Inc. trying to do something similar 
> at some point. This kind of unilateral censorship, although well 
> intentioned, can only spark more of those flames.
>

Removing obvious flamebaits and spam really should not require a long 
consultation process.
(Censorship is a different story; while there cannot be a clear border 
between a flamebait and a good argument; intentional misquoting, as in the 
case we are talking about,
does qualify as an obvious flamebait, IMHO)

Having said that, I would like to see a more regular setup on "official" 
sagemath googlegroups; more people should be able to moderate posts/posters.
Repeated posting of flamebaits or/and other obviously damaging things 
should result in placing the poster under moderation (i.e. posts by this 
posters are held in
a moderation queue, and released only upon moderator's approval).

Should we start a process of nominating/electing moderators?

Dima

 

>
> Any long lived community on the net has moderators, be they elected or 
> co-opted. No one moderator takes this kind of decisions alone. Can we try, 
> once again, to start a process to become a well behaved community? There is 
> no shortage of very good examples of well behaved, long lived, FOSS 
> communities. Think Debian, think Software carpentry, ...
>
> Luca
>
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: [Yet again] Sage's R vs system's R

[kcrisman]

> I think maybe even a better distinction than "sage-the-distro" is to 
> call it "SageMath, the Application".  As far as users of the 
> application are concerned I agree the it should have the goal of being 
> a general purpose stack of mathematics software.  For short I'll call 
> the application/distribution SageMath in (camel-case) and the Python 
> package "sage" since that's what the actual package is called. 
>
> But treating that larger software stack, and the `sage` Python package 
> as one in the same makes development on the latter more difficult, and 
> probably ultimately the former as well.  For example--continuing with 
> R as the test particle--say I'm a SageMath user who makes heavy use of 
> R for my statistics, and like being able to use R with sage.  What 
> happens when a critical bug is fixed in R, and a new patch release 
> comes out (something Sage, by the way, doesn't even have but should). 
> How do I get that patch release?  Well I have to wait for a new 
> version of sage (the package, and everything else that comes with it). 
> That might include a bunch of other new dependencies that I didn't 
> really think I needed.  Possibly even API breakage elsewhere (though 
> fortunately sage itself is normally pretty good about that). 
>
>
Yes, I agree that is a very significant issue and of course has been for 
some time (with respect to many, many packages, I couldn't even list them 
all for you).  Perhaps unreasonably, I want us to be able to have our cake 
and eat it too, at least in this regard.  Which is why it is awesome you 
are on board since maybe eventually this will happen :)

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: [Yet again] Sage's R vs system's R

[Erik Bray]

On Wed, Aug 24, 2016 at 6:58 PM, kcrisman  wrote:
>
>
> On Tuesday, August 23, 2016 at 4:54:45 PM UTC-4, leif wrote:
>>
>> kcrisman wrote:
>> >
>> > Make R optional?  (Nothing in Sage depends on it, except for the
>> > interface to it, including Rpy2.)
>> >
>> > Gosh, R has been standard for*ever*, practically,
>>
>> Hört sich nach Schwäbischem Dreiklang an.
>>
>
> Not being from southern Germany, I have no idea what you're talking about
> ...
>
>>
>>
>> > and is often heavily
>> > advertised as a good reason to use Sage.  There are certainly many who
>> > have been using them together (as mentioned, obviously nowhere near the
>> > number of "pure" R users, but still we definitely get queries about this
>> > regularly)
>>
>> Well, I guess the ratio of R-thru-Sage users to Sage users is as
>> "negligible" as that to pure R users. ;-)
>>
>
> Just today:
> http://ask.sagemath.org/question/34571/linear-regression-with-r-in-sagemath/
>
> I'm not saying it's a huge user group, but if Sage is actually mathematics
> software and not "people in number theory" software, it would be nice to
> have good stats and the tons of optional R packages just waiting.  It has
> definitely been a selling point in many discussions I've had, and I and
> others have used it ourselves.  Note that even for "brial"/polybori which
> presumably is not a huge user base either we made things work out.
>
> How this relates to "Sage-the-package" versus "Sage-The-distro" I don't care
> as long as it's still in "sage-the-distro".

Absolutely it should be--by default in fact, since it already has
been. It would be a major regression to remove it.

I think maybe even a better distinction than "sage-the-distro" is to
call it "SageMath, the Application".  As far as users of the
application are concerned I agree the it should have the goal of being
a general purpose stack of mathematics software.  For short I'll call
the application/distribution SageMath in (camel-case) and the Python
package "sage" since that's what the actual package is called.

But treating that larger software stack, and the `sage` Python package
as one in the same makes development on the latter more difficult, and
probably ultimately the former as well.  For example--continuing with
R as the test particle--say I'm a SageMath user who makes heavy use of
R for my statistics, and like being able to use R with sage.  What
happens when a critical bug is fixed in R, and a new patch release
comes out (something Sage, by the way, doesn't even have but should).
How do I get that patch release?  Well I have to wait for a new
version of sage (the package, and everything else that comes with it).
That might include a bunch of other new dependencies that I didn't
really think I needed.  Possibly even API breakage elsewhere (though
fortunately sage itself is normally pretty good about that).

Better would be to have a stable version of SageMath the application
stack, with a stable version of sage at its core, to which one can
receive small patch upgrades both to sage, as well as to the other
software in the stack, and only make "big" upgrades if I need to, or
want to be on the bleeding edge (it's also perfectly possible and
reasonable to have several at once--a stable version used for work,
and a development or experimental version in a different install
path).

Another option of course is to provide one's own R installation and
have sage use that instead of the R installed in the SageMath stack.
This should definitely be doable for most of sage's dependencies,
especially the optional, non-core ones (and there has been some
progress on that front).  In sage there  should be at most a way to
get the path to the R to use, and a minimal (best guess at least)
version check for whether it's supported by the interface.

Jeroen and others have pointed out examples where it isn't always so
nice--for example getting important bug fixes bundled up with major
API change bombs in ways that are difficult to extricate.  This is
sort of thing is certainly a pain to deal with--sometimes it can force
an otherwise unwanted upgrade.  But a model that separates SageMath
from sage doesn't preclude that either.  It just means that the stable
release of the former may not get all fixes all the time.  In practice
this is rare.  Many packages are well-behaved in terms of their
versions, and maintaining stable release lines for a decent amount of
time.  For those that don't, most of the time at worst it is the job
of a downstream integrator (like us) to manually cherry-pick a
sensible patch set.  Most bug fixes are not hard to backport if
they're relevant to older releases.



On Wed, Aug 24, 2016 at 6:57 PM, leif  wrote:
> A matter of introducing more package "types" (such as "mandatory",
> "shipped by default", "installed by default" etc.), and changing mainly
> some (build, release and dist) scripts accordingly.  (In addition,
> portions of the Sage library 

Re: [sage-devel] mailing list administration

[Erik Bray]

On Aug 25, 2016 10:18, "William Stein"  wrote:
>
>
>
> On Wednesday, August 24, 2016, Luca De Feo 
wrote:
>>
>> > I deleted it as flame bait.   I'm sick of people using sage-devel as a
>> > forum to attack others
>>
>> I'm sick of it too. But this kind of unilateral actions only fuels the
flame, it does not extinguish it.
>>
>> Especially given your position as a CEO of a for profit company,
William. Even though you do not have the power to do the same with Sage as
what just happened with MariaDB, the community is entitled with a
legitimate (unfounded, I believe) fear of SageMath Inc. trying to do
something similar at some point. This kind of unilateral censorship,
although well intentioned, can only spark more of those flames.
>
>
> If people really want flame bait on this list, then I am going to stop
reading sage-devel.

I'm inclined to agree. I think that characterizations like "unilateral" and
"censorship" are needlessly pejorative in this case. Sometimes swift and
unforgiving action against ill-willed and toxic trolling is justified.
*Especially* given a lack of better moderation standards. That said, while
I think the lack of community standards justifies it, that lack still isn't
excused.

>> Any long lived community on the net has moderators, be they elected or
co-opted. No one moderator takes this kind of decisions alone. Can we try,
once again, to start a process to become a well behaved community? There is
no shortage of very good examples of well behaved, long lived, FOSS
communities. Think Debian, think Software carpentry, ...

Here I agree with Luca. I think this is desperately needed this community.
I've been wanting very much to bring it up for a while but as I know from
personal experience it takes a lot of work and I'm already spread too thin.
Also being rather new to this community I don't feel comfortable taking the
lead on such a discussion. But I think it does need to happen. (Just not
starting in this thread of course).

Best,
Erik

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: git trac push error

[Julien Lavauzelle]

Ok, we solved it by a force push.

The weird  was probably because of french accents 
in git log error.

Julien

Le jeudi 25 août 2016 10:06:31 UTC+2, Julien Lavauzelle a écrit :
>
> Hi,
>
> I have the following git trac push error:
>
> Pushing to Trac #20100...
> Guessed remote branch: u/jlavauzelle/cyclic_code
> Traceback (most recent call last):
>   File "/usr/local/bin/git-trac", line 18, in 
> cmdline.launch()
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/cmdline.py", line 
> 223, in launch
> app.push(ticket_number, remote=args.remote, force=args.force)
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/app.py", line 216, 
> in push
> self.repo.push(remote, force)
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/git_repository.py"
> , line 197, in push
> self.git.echo.push('trac', refspec)
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
> line 341, in meth
> return self.execute(git_cmd, *args, **kwds)
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
> line 98, in execute
> popen_stderr=subprocess.PIPE)
>   File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
> line 263, in _run
> raise GitError(result)
> git_trac.git_error.GitError: 
>
>
> I tried many things: reinstall git-trac, change the remote url, use 
> different internet connections.
> None of them work.
> Weirdly, git trac checkout #ticket works though.
>
> Can someone help me?
>
> Thanks,
>
> Julien Lavauzelle
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] mailing list administration

[William Stein]

On Wednesday, August 24, 2016, Luca De Feo 
wrote:

> > I deleted it as flame bait.   I'm sick of people using sage-devel as a
> > forum to attack others
>
> I'm sick of it too. But this kind of unilateral actions only fuels the
> flame, it does not extinguish it.
>
> Especially given your position as a CEO of a for profit company, William.
> Even though you do not have the power to do the same with Sage as what just
> happened with MariaDB, the community is entitled with a legitimate
> (unfounded, I believe) fear of SageMath Inc. trying to do something similar
> at some point. This kind of unilateral censorship, although well
> intentioned, can only spark more of those flames.
>

If people really want flame bait on this list, then I am going to stop
reading sage-devel.

  - William


>
> Any long lived community on the net has moderators, be they elected or
> co-opted. No one moderator takes this kind of decisions alone. Can we try,
> once again, to start a process to become a well behaved community? There is
> no shortage of very good examples of well behaved, long lived, FOSS
> communities. Think Debian, think Software carpentry, ...
>
> Luca
>
>





> --
> 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 https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my massive iPhone 6 plus.

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [sage-support] (William Stein) "my top priority right now is to **make a lot of money**"

[Justin C. Walker]

Why is this still being discussed?  It belongs on the flame list.

On Aug 24, 2016, at 13:12 , Nathann Cohen wrote:

> Quote from William Stein, CEO of SageMath Inc (private for-profit
> Delaware company) [1]
> 
>So there is no confusion, my top priority right now is to **make a lot
>of money** by building a profitable company on open source software
>(Latex, Linux, Sage, Octave, R, etc.)
> 
>(full post)
>https://groups.google.com/d/msg/sage-devel/B3WnJr6S1bw/JQ_jvOITBAAJ
> 
> This post being entirely factual, I shouldn't be held responsible for
> its content.
> 
> Nathann
> 
> [1] 
> http://www.edgarcompany.sec.gov/servlet/CompanyDBSearch?page=detailed=0001634867_back=23
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-supp...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income

Experience is what you get
  when you don't get what you want.




-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] git trac push error

[Julien Lavauzelle]

Hi,

I have the following git trac push error:

Pushing to Trac #20100...
Guessed remote branch: u/jlavauzelle/cyclic_code
Traceback (most recent call last):
  File "/usr/local/bin/git-trac", line 18, in 
cmdline.launch()
  File "/usr/local/lib/python2.7/dist-packages/git_trac/cmdline.py", line 
223, in launch
app.push(ticket_number, remote=args.remote, force=args.force)
  File "/usr/local/lib/python2.7/dist-packages/git_trac/app.py", line 216, 
in push
self.repo.push(remote, force)
  File "/usr/local/lib/python2.7/dist-packages/git_trac/git_repository.py", 
line 197, in push
self.git.echo.push('trac', refspec)
  File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
line 341, in meth
return self.execute(git_cmd, *args, **kwds)
  File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
line 98, in execute
popen_stderr=subprocess.PIPE)
  File "/usr/local/lib/python2.7/dist-packages/git_trac/git_interface.py", 
line 263, in _run
raise GitError(result)
git_trac.git_error.GitError: 


I tried many things: reinstall git-trac, change the remote url, use 
different internet connections.
None of them work.
Weirdly, git trac checkout #ticket works though.

Can someone help me?

Thanks,

Julien Lavauzelle

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: mailing list administration

[Luca De Feo]

> I deleted it as flame bait.   I'm sick of people using sage-devel as a 
> forum to attack others

I'm sick of it too. But this kind of unilateral actions only fuels the 
flame, it does not extinguish it.

Especially given your position as a CEO of a for profit company, William. 
Even though you do not have the power to do the same with Sage as what just 
happened with MariaDB, the community is entitled with a legitimate 
(unfounded, I believe) fear of SageMath Inc. trying to do something similar 
at some point. This kind of unilateral censorship, although well 
intentioned, can only spark more of those flames.

Any long lived community on the net has moderators, be they elected or 
co-opted. No one moderator takes this kind of decisions alone. Can we try, 
once again, to start a process to become a well behaved community? There is 
no shortage of very good examples of well behaved, long lived, FOSS 
communities. Think Debian, think Software carpentry, ...

Luca

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.