From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: [Feature idea] Adding wikidata, wikipedia & screenshot-url fields to package-recipes Date: Thu, 1 Nov 2018 10:44:19 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------16E457FFF6B944CF5DBF162A" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49393) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gI9RJ-0004Y4-4m for guix-devel@gnu.org; Thu, 01 Nov 2018 05:38:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gI9RF-0005W8-Ty for guix-devel@gnu.org; Thu, 01 Nov 2018 05:38:57 -0400 Received: from mx1.riseup.net ([198.252.153.129]:52698) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gI9RF-0005VZ-IN for guix-devel@gnu.org; Thu, 01 Nov 2018 05:38:53 -0400 Received: from piha.riseup.net (piha-pn.riseup.net [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 3AC021A0649 for ; Thu, 1 Nov 2018 02:38:52 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by piha.riseup.net with ESMTPSA id 8D8CB63D48 for ; Thu, 1 Nov 2018 02:38:50 -0700 (PDT) Content-Language: en-US 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: guix-devel@gnu.org This is a multi-part message in MIME format. --------------16E457FFF6B944CF5DBF162A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi I am a contributor to OSM and have seen how combining OSM and=20 Wikidata/Wikipedia (WP) has been very useful. I got the idea of adding Wikidata-entries to guix package objecs would=20 be fruitful because: It makes it possible to a more useful list of packages e.g. by showing=20 links to WP entries for the program in the users local language. (E.g.=20 by firing up a browser from emacs or the shell, or by populating a (per=20 channel) html package list (with screenshots, local WP-links, etc.) and=20 firing up a throw-away web-server instance serving this with e.g. /guix=20 package --list-available-packages-html)/ It would also perhaps be of benefit to WP-contributors because we could=20 easily make statistics for how many of the packages in guix a=20 Wikidata-entry and/or WP-entry exists. Thus perhaps leading to creating=20 of more articles for notable packages or improving WP-articles with=20 outdated release information. *Implementation:* It could be implemented by adding the fields to package-objects. The rationale for adding screenshot-url to the recipe is that this=20 parsing of wikidata->en-WP->url-for-first-image for every package in our=20 list is quite expensive. Better to do it once and perhaps update all the=20 screenshot-urls once a year or so. The rationale for adding WP (list of Wikipeidas with an article in the=20 wikidata entry, e.g. ("en" "sv" "es") to the recipe is that this parsing=20 of wikidata->WP for every package in our list is quite expensive. Better=20 to do it once and perhaps update=C2=A0 once a year or so. Also to help us to associate new and existing packages with=20 wikidata-entries we could devise a guile-programmed way to associate=20 wikidata-entries to existing package objects and perhaps use this to=20 populate new package-recipes created with /guix import/ Guix would then be the first package manager to both be completely free=20 of proprietary software and to leverage knowledge from Wikidata and WP. What do you think? /Cheers/ Swedebugia PS: we could further improve our recipes by adding fields like "release=20 date" either via guix import from upstream or by populating from WP.=20 This would make it easy for WP-contributors to track when new releases=20 happen and perhaps with a script automatically update WP-articles based=20 on our recipes when we have newer information. PPS: Perhaps over time it will even be feasible for WP to use our=20 synopsis/descriptions somehow. This would enable us to integrate=20 descriptions and translations for programs. E.g. a WP-contributor sees=20 that an article in spanish for program x does not yet exist in es.WP but=20 a translated synopsis and description already exists in Guix. --------------16E457FFF6B944CF5DBF162A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi

I am a contributor to OSM and have seen how combining OSM and Wikidata/Wikipedia (WP) has been very useful.

I got the idea of adding Wikidata-entries to guix package objecs would be fruitful because:

It makes it possible to a more useful list of packages e.g. by showing links to WP entries for the program in the users local language. (E.g. by firing up a browser from emacs or the shell, or by populating a (per channel) html package list (with screenshots, local WP-links, etc.) and firing up a throw-away web-server instance serving this with e.g. guix package --list-available-pa= ckages-html)

It would also perhaps be of benefit to WP-contributors because we could easily make statistics for how many of the packages in guix a Wikidata-entry and/or WP-entry exists. Thus perhaps leading to creating of more articles for notable packages or improving WP-articles with outdated release information.

Implementation:

It could be implemented by adding the fields to package-objects.

The rationale for adding screenshot-url to the recipe is that this parsing of wikidata->en-WP->url-for-first-image for every package in our list is quite expensive. Better to do it once and perhaps update all the screenshot-urls once a year or so.

The rationale for adding WP (list of Wikipeidas with an article in the wikidata entry, e.g. ("en" "sv" "es") to the recipe is that this parsing of wikidata->WP for every package in our list is quite expensive. Better to do it once and perhaps update=C2=A0 once= a year or so.

Also to help us to associate new and existing packages with wikidata-entries we could devise a guile-programmed way to associate wikidata-entries to existing package objects and perhaps use this to populate new package-recipes created with guix import

Guix would then be the first package manager to both be completely free of proprietary software and to leverage knowledge from Wikidata and WP.

What do you think?

Cheers
Swedebugia

PS: we could further improve our recipes by adding fields like "release date" either via guix import from upstream or by populating from WP. This would make it easy for WP-contributors to track when new releases happen and perhaps with a script automatically update WP-articles based on our recipes when we have newer information.

PPS: Perhaps over time it will even be feasible for WP to use our synopsis/descriptions somehow. This would enable us to integrate descriptions and translations for programs. E.g. a WP-contributor sees that an article in spanish for program x does not yet exist in es.WP but a translated synopsis and description already exists in Guix. --------------16E457FFF6B944CF5DBF162A--