Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Jeffrey Cliff]

> many packages come from GitHub

And I intend on filing a bug report on every single one of those packages,
as they come up.  This is a huge problem, but one that can be solved since
it is free software we are talking about.


On Tue, 26 Mar 2019 at 15:28, Xavier  wrote:

> Le 26/03/2019 à 20:17, Jeffrey Cliff a écrit :
> > As maintainer, that's up to you, but I do not accept any project hosted
> > in the NSA/Microsoft walled garden as the legitimate upstream of
> > anything and I will continue to host 'progress', in particular,
> > somewhere, until a 2.0.0+ version is available in some other upstream
> place.
>
> So I recommend you to no more use Debian since many packages come from
> GitHub. Anyway, publishing a fork of a software without changing its
> name isn't a good thing and may be invalid. Please host this somewhere
> else.
>


-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Xavier]

Le 26/03/2019 à 20:17, Jeffrey Cliff a écrit :
> As maintainer, that's up to you, but I do not accept any project hosted
> in the NSA/Microsoft walled garden as the legitimate upstream of
> anything and I will continue to host 'progress', in particular,
> somewhere, until a 2.0.0+ version is available in some other upstream place.

So I recommend you to no more use Debian since many packages come from
GitHub. Anyway, publishing a fork of a software without changing its
name isn't a good thing and may be invalid. Please host this somewhere else.

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Jeffrey Cliff]

As maintainer, that's up to you, but I do not accept any project hosted in
the NSA/Microsoft walled garden as the legitimate upstream of anything and
I will continue to host 'progress', in particular, somewhere, until a
2.0.0+ version is available in some other upstream place.

On Tue, 26 Mar 2019 at 14:34, Xavier  wrote:

> Le 26/03/2019 à 19:04, Jeffrey Cliff a écrit :
> > 2.0.0 was the version when Microsoft captured Github.  That's the newest
> > one I have, but thankfully that's as new as is needed by the version of
> > eslint in RFP.
> >
> > I prefer to do my contributions anonymously.  I am not the author.
> >
> >> Following https://www.npmjs.com/package/progress, repo is
> > https://github.com/visionmedia/node-progress.
> >
> > Indeed, it does go to NSA/Microsoft's walled garden.
> >
> >> There is de debian/ dir in your repo, why ?
> >
> > I can remove that
>
> >> So if you're upstream author, I suggest you to publish a 2.0.4 in
> >> npmjs.com with new repo in your package.json, then we could safely
> >> change debian/watch.
>
> I won't update anything unless you publish a new version accepted by
> npmjs.com: it will prove that you've some rights on node-progress.
>
> Debian can't accept an hostile takeover. If you're not upstream, you can
> publish your fork under another name.
>


-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Xavier]

Le 26/03/2019 à 19:04, Jeffrey Cliff a écrit :
> 2.0.0 was the version when Microsoft captured Github.  That's the newest
> one I have, but thankfully that's as new as is needed by the version of
> eslint in RFP.
> 
> I prefer to do my contributions anonymously.  I am not the author.
> 
>> Following https://www.npmjs.com/package/progress, repo is
> https://github.com/visionmedia/node-progress.
> 
> Indeed, it does go to NSA/Microsoft's walled garden.
> 
>> There is de debian/ dir in your repo, why ?
> 
> I can remove that

>> So if you're upstream author, I suggest you to publish a 2.0.4 in
>> npmjs.com with new repo in your package.json, then we could safely
>> change debian/watch.

I won't update anything unless you publish a new version accepted by
npmjs.com: it will prove that you've some rights on node-progress.

Debian can't accept an hostile takeover. If you're not upstream, you can
publish your fork under another name.

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Xavier]

Le 26/03/2019 à 17:53, Jeffrey Cliff a écrit :
> I don't use NSA/Microsoft github so I'll assume you mean to update the
> readme in the repo I control, which I have added a note to.  Is there
> anything in specific you are interested in my adding?
> 
> On Tue, 26 Mar 2019 at 07:17, Xavier  > wrote:
> 
> Le 26/03/2019 à 08:07, Jeffrey Cliff a écrit :
> > Package: node-progress
> > Version: 1.1.8-1
> > Severity: normal
> >
> > As NSA/Microsoft has taken over Github, it is long since time to
> move to
> > a non-Microsoft source for projects like node-progress.  I have made a
> > non-microsoft repo at salsa
> > at https://salsa.debian.org/themusicgod1-guest/progress/ for use as a
> > future 'upstream' for this package.
> >
> > Also of note: the version of progress at the above repo is 2.0.0,
> which
> > is a newer version.  A diff can be made available if it is required. 
> >
> > Jeff Cliff
> 
> Hello,
> 
> could you also update
> https://github.com/visionmedia/node-progress#readme ?

There are some troubles here:
 * For now, you are not mentioned as node-progress contributor neither
   author
(https://github.com/visionmedia/node-progress/blob/master/package.json).
 * Github/npmjs version is 2.0.3 while yours is 2.0.0.
 * Following https://www.npmjs.com/package/progress, repo is
   https://github.com/visionmedia/node-progress.
 * There is de debian/ dir in your repo, why ?

So if you're upstream author, I suggest you to publish a 2.0.4 in
npmjs.com with new repo in your package.json, then we could safely
change debian/watch.

Debian package of node-progress is hosted on
https://salsa.debian.org/js-team/node-progress

Cheers,
Xavier

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Jeffrey Cliff]

I don't use NSA/Microsoft github so I'll assume you mean to update the
readme in the repo I control, which I have added a note to.  Is there
anything in specific you are interested in my adding?

On Tue, 26 Mar 2019 at 07:17, Xavier  wrote:

> Le 26/03/2019 à 08:07, Jeffrey Cliff a écrit :
> > Package: node-progress
> > Version: 1.1.8-1
> > Severity: normal
> >
> > As NSA/Microsoft has taken over Github, it is long since time to move to
> > a non-Microsoft source for projects like node-progress.  I have made a
> > non-microsoft repo at salsa
> > at https://salsa.debian.org/themusicgod1-guest/progress/ for use as a
> > future 'upstream' for this package.
> >
> > Also of note: the version of progress at the above repo is 2.0.0, which
> > is a newer version.  A diff can be made available if it is required.
> >
> > Jeff Cliff
>
> Hello,
>
> could you also update https://github.com/visionmedia/node-progress#readme
> ?
>
>

-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation

Bug#925517: [Pkg-javascript-devel] Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Xavier]

Le 26/03/2019 à 08:07, Jeffrey Cliff a écrit :
> Package: node-progress
> Version: 1.1.8-1
> Severity: normal
> 
> As NSA/Microsoft has taken over Github, it is long since time to move to
> a non-Microsoft source for projects like node-progress.  I have made a
> non-microsoft repo at salsa
> at https://salsa.debian.org/themusicgod1-guest/progress/ for use as a
> future 'upstream' for this package.
> 
> Also of note: the version of progress at the above repo is 2.0.0, which
> is a newer version.  A diff can be made available if it is required. 
> 
> Jeff Cliff

Hello,

could you also update https://github.com/visionmedia/node-progress#readme ?

Bug#925517: Non-NSA/Microsoft upstream repo, new version

[Jeffrey Cliff]

Package: node-progress
Version: 1.1.8-1
Severity: normal

As NSA/Microsoft has taken over Github, it is long since time to move to a
non-Microsoft source for projects like node-progress.  I have made a
non-microsoft repo at salsa at
https://salsa.debian.org/themusicgod1-guest/progress/ for use as a future
'upstream' for this package.

Also of note: the version of progress at the above repo is 2.0.0, which is
a newer version.  A diff can be made available if it is required.

Jeff Cliff