unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: ng0@n0.is
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Add badass.
Date: Wed, 31 Jan 2018 06:54:09 +0300	[thread overview]
Message-ID: <87h8r2znry.fsf@gmail.com> (raw)
In-Reply-To: <87tvv390c6.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> (ng0@n0.is's message of "Tue, 30 Jan 2018 09:12:41 +0000")

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

Hello,

ng0@n0.is writes:

>>> Why do you think this belongs in Guix?  Do you intend to use it
>>
>> So we do have Quality Standards for software that goes into Guix
>> now as in "you must be this tall to ride"? Didn't apply before
>> when other people sent in what I'd consider garbage.
>>
>> I'd be okay with keeping it outside of Guix in my own repos, so
>> go ahead and drop it for random reasons.
>
> Sorry, my reply was a bit too harsh. Here's another try:
>
> I don't have any ability to predict the taste of people.
> If we decline certain software entry into Guix, we should make it
> clear.. case by case? standards?
> Fyi I'm using this on github and other websites that make use of
> the activity graph.
>
> We do have software in our repository that I consider trash, so
> it's always subjective.
>
>>> yourself, or do you have reason to believe that Guix users would want
>>> this?
>>>
>>> There's a lot of garbage out there.  Guix doesn't need to include every
>>> script that someone uploaded to github.  Frankly, I'm embarrassed to
>>> have a package like this in Guix.

If a program was written and distributed with a free or open license,
then it's not a garbage for a writer at least.  The purpose of usage
for everyone else could be different, maybe be a learning as example.

So, even if it's a simple script, but which somebody use and update, is
where a reason to block it?  After all it's not breaking anything.  :-)


Thanks,
Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2018-01-31  3:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180129215805.7086.26926@vcs0.savannah.gnu.org>
     [not found] ` <20180129215806.5F45C20512@vcs0.savannah.gnu.org>
2018-01-29 23:09   ` 01/01: gnu: Add badass Mark H Weaver
2018-01-30  4:17     ` Leo Famulari
2018-01-31 13:53       ` Package inclusion criteria Ludovic Courtès
2018-01-31 14:10         ` ng0
2018-01-31 17:56           ` myglc2
2018-01-31 23:48           ` Ludovic Courtès
2018-01-30  9:05     ` 01/01: gnu: Add badass ng0
2018-01-30  9:12       ` ng0
2018-01-31  3:54         ` Oleg Pykhalov [this message]

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=87h8r2znry.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ng0@n0.is \
    /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).