unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: ng0@pragmatique.xyz
Cc: guix-devel@gnu.org
Subject: Re: [directory-discuss] guix tags that could be automatically extracted
Date: Sun, 16 Jul 2017 15:33:59 +0200	[thread overview]
Message-ID: <08829de5-d4ed-a892-1202-1c815147e795@tobias.gr> (raw)
In-Reply-To: <20170716120743.6bjezyufuxra5wji@abyayala>


[-- Attachment #1.1: Type: text/plain, Size: 1801 bytes --]

ng0,

On 16/07/17 14:07, ng0 wrote:
> What I expressed last night:
> 
> I don't want any additions to the connections made without the 
> consent of people using guix.

The proposal then was using Guix to ‘feed’ the Directory, not the other
way round. We as a project can't prohibit others to export data from
their Guix checkout to their wiki if they'd so desire.

However, individual authors probably have some sort of copyright over
the data in some jurisdiction, which is why I don't see it happening.

> What exactly does this mean? Everything should be within Guix. The 
> default should be to *not* call some mediawiki for more information. 
> If we even have the option to query this mediawiki and the 
> information doesn't have to be present in guix like translations, I 
> want it to be optional and you have to opt-in to (receiving) these 
> (informations).

A sentiment which I support in general, but which makes no sense when
discussing ‘guix import’, whose entire purpose in this life is to query
external sources. What's so different about this one?

(I'm not personally advocating adding *this particular one* — I have
nothing against the project, but do think our descriptions are slightly
better on average. Quiliro's proposal seemed interesting enough to
discuss here: they're obviously eager to contribute, and this would be a
relatively easy importer to write :-)

> Please discuss this either on guix-devel or on the other list, but 
> don't CC me into one of the famous gnu.org cross-posting
> discussions. Thanks for your consideration.

What?

I don't think this proposal will be going anywhere because of licencing
hurdles alone, anyway, so you'll not be disturbed by any more replies
from me.

Kind regards,

T G-R


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]

  reply	other threads:[~2017-07-16 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fudx6u4u.fsf@riseup.net>
2017-07-16  6:19 ` [directory-discuss] guix tags that could be automatically extracted Tobias Geerinckx-Rice
2017-07-16 12:07   ` ng0
2017-07-16 13:33     ` Tobias Geerinckx-Rice [this message]
2017-07-16 15:04       ` ng0
2017-07-16 18:02         ` Adonay Felipe Nogueira
2017-07-17 14:08           ` Ludovic Courtès
2017-07-21 13:18             ` Adonay Felipe Nogueira
2017-07-21 13:07     ` Adonay Felipe Nogueira

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=08829de5-d4ed-a892-1202-1c815147e795@tobias.gr \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=ng0@pragmatique.xyz \
    /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).