[lmi] Fwd: Re: PR: Check that the run order is the same for all cells and the case

[Greg Chicares]

[resending because original was missing from html archive]


-------- Forwarded Message --------
Subject: Re: [lmi] PR: Check that the run order is the same for all cells and 
the case
Date: Sat, 03 Oct 2015 00:58:52 +0000
From: Greg Chicares <address@hidden>
Reply-To: Let me illustrate... <address@hidden>
To: Let me illustrate... <address@hidden>

On 2015-10-02 21:37, Vadim Zeitlin wrote:
> 
>  Let me try to experiment with a new mechanism for patch submission: using
> GitHub pull requests. It's a bit strange to use them when you don't use
> GitHub (yet...), but it does have some advantages: you can view the patches
> easily in a nice, coloured and syntax highlighting GitHub diff viewer and I
> can keep track of different patches more easily. This would also allow
> updating the patches if you make any comments about them here or on GitHub
> (which is the simplest way to do it but does require a GitHub account --
> OTOH GitHub account is as non intrusive as an account can be and doesn't
> require you providing any information at all AFAIR).

I am glad to accept terms like these to use an online service:

http://savannah.gnu.org/register/requirements.php
| Use of project account ... Using it to host or advertise non-free software
| is considered harmful to free software. ... your project must be free
| software ... Please label it as "free software" rather than as "open
| source". ... (GNU with Linux as the kernel) ... While using our hosting
| services, please acknowledge our work by referring to this system as
| "GNU/Linux", not just "Linux"

or these to create an account:

https://savannah.gnu.org/account/register.php
| maximum allowed password length: 256.
| minimum length for passphrases: 11
| Do not use a hotmail or comcast address

But I balk at terms like these:

https://help.github.com/articles/github-terms-of-service/#f-copyright-and-content-ownership
| You shall defend GitHub ... shall indemnify GitHub for any damages ...
| and for reasonable attorney’s fees incurred by, GitHub ... at Your expense.

I just don't see the wisdom in agreeing to that. And their system isn't
even free software:

| ... You may not duplicate, copy, or reuse any portion of the HTML/CSS,
| Javascript, or visual design elements or concepts

They support free software...by hosting it on non-free software? Huh?

> Of course, if you
> don't like it and prefer the old way of submitting patches, please just let
> me know and I'll revert to doing it like this.

I am willing to try anything that does not require a github account.

If I can't 'git pull' from github without agreeing to indemnify their
attorneys, then I'll "Just Say No". Perhaps I can still grab your
patches through their public web interface.

http://savannah.gnu.org/register/requirements.php
| you can point people to commercial support offerings for your
| free software project

I already have an account at this most excellent company, which
I'm glad to point people to for lmi support:
  http://www.tt-solutions.com/fr/home/
and am of course willing to 'git pull' from there if you like
(even if it lacks a "nice, coloured and syntax highlighting"
diff viewer; of course, you could simply copy github's, except
that github is not free software).


_______________________________________________
lmi mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lmi