<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">Am 20.04.2016 um 00:38 schrieb Chris
Barker:<br>
</div>
<blockquote
cite="mid:CALGmxEKZQs0XYeD7odQrU6EXcrZvJ3moJK5+yOdeu8ywddB2rQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Apr 19, 2016 at 9:45 AM,
Ronny Pfannschmidt <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:opensource@ronnypfannschmidt.de"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:opensource@ronnypfannschmidt.de">opensource@ronnypfannschmidt.de</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Instead
of overtaking,<br>
how about clearly marking packages as abandoned/maintained
clearly<br>
pointing out the mark was imposed by community action<br>
</blockquote>
<div><br>
</div>
<div>I think that would be a good idea -- and maybe start
with just that -- then we'd learn how big an issue it
really was, etc.</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
and listing potential/primary replacements<br>
</blockquote>
<div><br>
</div>
<div>that required real work on someone's part -- so not
sure when that would actually happen.</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">its
important that community imposed abandonment is not simply
removable<br>
by doing a minor "noop"-release,<br>
</blockquote>
<div><br>
</div>
<div>why not? I brought tis all up to address truly
abandoned projects -- maybe we want to go some day to the
idea of the names being community owned, but that's not
the way ti is now -- and if someone makes the effort to do
a noop release, then they have no abandoned the name --
maybe aren't maintaining it worth a damn, but there you
go.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
a community action is supposed to be imposed after extended
non-reaction,<br>
an next to no effort way to get out of it seems counter such an
invsive move.<br>
<br>
its not given lightly, and it shouldn't be easy to weasel out of it.<br>
Actually a noop release is a good indicator that the mark is
well-deserved and should be keept.<br>
Making an effort to remove a mark without making the reason for its
existence go as well is a lie in plain sight.<br>
<br>
this reminds me of the whole setuptools/distribute situation.<br>
<br>
-- Ronny<br>
<br>
<blockquote
cite="mid:CALGmxEKZQs0XYeD7odQrU6EXcrZvJ3moJK5+yOdeu8ywddB2rQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Personally, I think there is no point in anything
between the current free for all, and a "curated" package
repo -- a curated repo would support the idea that
anything on it had met some minimum standard: no malware,
some maintenance, some minimum usefulness, etc.</div>
<div><br>
</div>
<div>It's kind of a shame that there are so many "toy"
packages and experiments on PyPi, but in fact, it's worked
pretty darn well..</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">pip
could warn on installation/update<br>
</blockquote>
<div><br>
</div>
<div>I think that would be good too</div>
<div><br>
</div>
<div>-Chris</div>
<div><br>
</div>
</div>
-- <br>
<div class="gmail_signature"><br>
Christopher Barker, Ph.D.<br>
Oceanographer<br>
<br>
Emergency Response Division<br>
NOAA/NOS/OR&R (206) 526-6959 voice<br>
7600 Sand Point Way NE (206) 526-6329 fax<br>
Seattle, WA 98115 (206) 526-6317 main reception<br>
<br>
<a moz-do-not-send="true"
href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div>
</div>
</blockquote>
<br>
</body>
</html>