[Pkg-javascript-devel] Bug#925517: 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 <yadd at debian.org> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20190326/9e723dba/attachment.html>