From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [directory-discuss] guix tags that could be automatically extracted Date: Sun, 16 Jul 2017 15:04:06 +0000 Message-ID: <20170716150406.w5e7xecnvh2azdq2@abyayala> References: <87fudx6u4u.fsf@riseup.net> <20170716120743.6bjezyufuxra5wji@abyayala> <08829de5-d4ed-a892-1202-1c815147e795@tobias.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="a6mfr3gou6bgjx5x" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60107) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dWmPa-0003GV-UC for guix-devel@gnu.org; Sun, 16 Jul 2017 12:28:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dWmPX-0004hc-LW for guix-devel@gnu.org; Sun, 16 Jul 2017 12:28:50 -0400 Received: from aibo.runbox.com ([91.220.196.211]:41338) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dWmPX-0004gz-D9 for guix-devel@gnu.org; Sun, 16 Jul 2017 12:28:47 -0400 Content-Disposition: inline In-Reply-To: <08829de5-d4ed-a892-1202-1c815147e795@tobias.gr> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tobias Geerinckx-Rice Cc: guix-devel@gnu.org, ng0@pragmatique.xyz --a6mfr3gou6bgjx5x Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tobias Geerinckx-Rice transcribed 3.3K bytes: > ng0, >=20 > On 16/07/17 14:07, ng0 wrote: > > What I expressed last night: > >=20 > > I don't want any additions to the connections made without the=20 > > consent of people using guix. >=20 > The proposal then was using Guix to =E2=80=98feed=E2=80=99 the Directory,= not the other > way round. We as a project can't prohibit others to export data from Okay, then it's all good for me and I did not understand Quiliro. > their Guix checkout to their wiki if they'd so desire. >=20 > However, individual authors probably have some sort of copyright over > the data in some jurisdiction, which is why I don't see it happening. Yep. > > What exactly does this mean? Everything should be within Guix. The=20 > > default should be to *not* call some mediawiki for more information.=20 > > If we even have the option to query this mediawiki and the=20 > > information doesn't have to be present in guix like translations, I=20 > > want it to be optional and you have to opt-in to (receiving) these=20 > > (informations). >=20 > A sentiment which I support in general, but which makes no sense when > discussing =E2=80=98guix import=E2=80=99, whose entire purpose in this li= fe is to query > external sources. What's so different about this one? I did not read the full initial post. I responded to what Quiliro wrote in IRC before I left yesterday night. As we already established that I did not understand it correctly and now do, let me explain how I understood the proposal on IRC. I though the function would be to have some sort of mechanism in guix package etc which sends a QUERY to the mediawiki of fsf to receive data like categories (tags). If this would happen without the ability to reject this I would have vetoed against it. I'm not viewing this from a developer perspective but from users who want to be in control over the connections. There's more to it, but I'm not motivated to explain entire scenarios today. > (I'm not personally advocating adding *this particular one* =E2=80=94 I h= ave > nothing against the project, but do think our descriptions are slightly > better on average.=20 Yes, I think the fsf wiki is not really good. Really really not good. Maybe mediawiki/wikidata of wikipedia might have better resources. > 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 :-) Okay, I think I still don't understand it. Why an importer when it should be the other way around as you explained earlier? At first I understood Quiliro this way: FSF MW -> Guix. After the first part of your email it was this: Guix -> FSF MW. And now an importer... for descriptions which are worse than ours? Help me out here as I really don't know what the point of such an importer would be, unless I got lost in the explanation. >=20 > > Please discuss this either on guix-devel or on the other list, but=20 > > don't CC me into one of the famous gnu.org cross-posting > > discussions. Thanks for your consideration. >=20 > What? >=20 > 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. This wasn't directed at you specifically, I just want discussion to happen on one list. gnu.org has the tendency to spread certain discussions to at least 2 lists "because reasons". Crossposting is never a good idea, and I just wanted to discourage it for anyone replying to this, to not take some other list back into the CC. (I know you just posted this to guix-devel, which is good :)) > Kind regards, >=20 > T G-R >=20 --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --a6mfr3gou6bgjx5x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAllrgGYACgkQ4i+bv+40 hYghOw/8CYYF/UN5LA1DBrUOxUK4WmjgghBRx9hS2c8ncixID3LxAnB9Zc91iuFG 079I90xRfwqybfgDThL49DJrvDkC4+mtj94/Yrmg2XY5wVg7gi/7m7Xkm6MyvRfs LppoAs/oczVGipv3DAaBjNYGvvcYmJHlD5OTpYiSlzNy2cvXSso9yD1yWtpfHfFJ guDOAHMjsrSkhPOcXHBwV1k7tXgueCCR5qZ5zqsqjGtVis/te9T7e75EIv128q4y JpsLD34+RSqFDDt86cfFlLCJL8T0B/3l0+rfAskLDMf5/bKZyo3S6UhW88kmc1oE Cav0KAzBbYMsGTSB+AdjQhpfYkBtlTH6X2DZG9+Zl6/eedXQl402g4fCQYatsPxd dUHpGROCkoEyp9Jm4Y9Djejoqw4iJFepmPpB76FKx/lqM7Bsw2EEk6dThJ6LsV7/ aCRGO/e2mO9jF/+RFx0WklcqZXCERehKiX/QSMQ+p2nV8VHacwjJlPlmCx8on2HK DEjlj3B/fVNY7Bpitj7OdIKfIufe1FHojeMaCz6c5ZcfXw8IhXh+7ZvOLq1aPQQb wiBCvx4EI2EIGoOrF8Awct8LGjFGjZfiWHVwmhKN5QRu9mlg1Y/julJdrknofzmx RQa6RSJmevIdBTUQ1wJuTM4RxRyLST+syZ5319ln8Dq75+CXRy0= =BtCN -----END PGP SIGNATURE----- --a6mfr3gou6bgjx5x--