From: ng0 <ng0@infotropique.org>
To: guix-devel@gnu.org
Subject: Re: [directory-discuss] guix tags that could be automatically extracted]
Date: Sun, 16 Jul 2017 15:17:52 +0000 [thread overview]
Message-ID: <20170716151752.azoo6lco6dwbxbjz@abyayala> (raw)
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
I think I switched off the @pragmatique.xyz email accounts a while ago.
If I didn't and my first send of this came through I'm sorry.
> 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
>
----- End forwarded message -----
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2017-07-16 15:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170716151752.azoo6lco6dwbxbjz@abyayala \
--to=ng0@infotropique.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.