From: Pjotr Prins <pjotr.public12@thebird.nl>
To: guix-devel@gnu.org
Subject: Re: [PATCH] xscreenshot and imagefile
Date: Thu, 30 Jul 2015 09:04:05 +0200 [thread overview]
Message-ID: <20150730070405.GA9314@thebird.nl> (raw)
In-Reply-To: <87oaiue4hh.fsf@netris.org>
How about creating a policy that people can refer to?
One of the great things about Guix is that is is accessible and
hackable, unlike most other packaging systems. Guix encourages
contributions and I think it is great that someone comes out of
nowhere and submits a package in the Guix way. If there is nothing
wrong with the package expression we can take the submission
seriously.
I don't think we can accept/reject packages on use or usefulness. I,
for one, will submit bioinformatics packages which may be meaningless
to 99.9999% of (eventual) Guix users. Are you saying it does not have
a right to go in because core maintainers do not see the benefit?
I think we should focus on compliance, i.e., the package expression
itself and the license, and maybe audit suspect software for not being
a spam/worm/virus. Otherwise I think we should be neutral in what
other people consider important. It is a bit of evolution
too. Unmaintained, defunct or nasty software gets removed eventually.
So, what would be a good policy for accepting/rejecting software
packages?
I favour accepting packages by default, provided the license is
acceptable, and remove them again if too many people complain *after*
using a package or *after* auditing the software itself for
maliciousness. We need to accept by default since we don't have the
time to go through all software source code *every* time.
I don't favour a policy of core maintainers deciding on what package
should go in, or not, in ad hoc fashion. I also don't favour a policy
of rigorous mentoring and acceptance, such as used by the Debian
project.
So, what is great about Guix? And what would be a suitable policy?
Pj.
On Wed, Jul 29, 2015 at 10:58:18PM -0400, Mark H Weaver wrote:
> Mark H Weaver <mhw@netris.org> writes:
>
> > Orchidaceae Phalaenopsis <orchid.hybrid@gmail.com> writes:
> >> * xscreenshot which takes a screenshot and saves it as .if format
> >> * imagefile which contains a few programs to convert .if to gif, png
> >
> > Honestly, I'm doubtful whether our users will have any interest in these
> > programs.
>
> I received a private email suggesting that my response here was
> unfriendly. I'm sorry that it came off that way, because that was not
> my intent. I'm just trying to express my opinion honestly.
>
> I've since looked closer at xscreenshot. Its final commit was the day
> after its initial commit, which was almost exactly one year ago. In
> that time, the only references I can find to it in a web search are:
>
> (1) a few messages on the suckless email list within a day or so after
> it was written
> (2) the current discussion on guix-devel, a year later
>
> and that's it. So, what we have here is a program with a two day commit
> history that produces a novel format that apparently nobody uses, and
> I've been unable to find any discussion about it in the year since then.
>
> Do other people think that such programs belong in Guix?
> Am I being an ungrateful ass?
>
> Mark
>
--
next prev parent reply other threads:[~2015-07-30 7:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 17:50 [PATCH] xscreenshot and imagefile Orchidaceae Phalaenopsis
2015-07-28 23:33 ` Guix-Bot
2015-08-18 15:22 ` Guix review bot Ludovic Courtès
2015-08-18 23:26 ` Cyril Roelandt
2015-08-25 21:31 ` Ludovic Courtès
2015-07-28 23:34 ` [PATCH] xscreenshot and imagefile Guix-Bot
2015-07-28 23:41 ` Guix-Bot
2015-07-28 23:42 ` Guix-Bot
2015-07-29 15:51 ` Mark H Weaver
2015-07-29 18:24 ` Alex Kost
2015-07-30 2:58 ` Mark H Weaver
2015-07-30 7:04 ` Pjotr Prins [this message]
2015-07-30 22:41 ` Cyril Roelandt
2015-07-31 17:59 ` Andreas Enge
2015-08-01 8:09 ` Pjotr Prins
2015-07-30 9:10 ` Mathieu Lirzin
2015-07-30 19:31 ` Packaging vs. Maintaining (was: [PATCH] xscreenshot and imagefile) Jeff Mickey
2015-07-31 1:51 ` [PATCH] xscreenshot and imagefile Mark H Weaver
2015-08-18 15:13 ` Ludovic Courtès
2015-07-29 17:48 ` Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150730070405.GA9314@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).