unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: [Feature idea] Adding wikidata, wikipedia & screenshot-url fields to package-recipes
Date: Thu, 1 Nov 2018 11:21:50 +0100	[thread overview]
Message-ID: <20181101102150.naklct2uiujtp2rl@thebird.nl> (raw)
In-Reply-To: <a0541da7-0cf2-6921-c018-ba391ed2362c@riseup.net>

On Thu, Nov 01, 2018 at 10:44:19AM +0100, swedebugia wrote:
>    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?

Absolutely the way forward. Totally excited you want to run with this!

Wikidata is linked data and dry and by using it we can share between
distros and software building projects (conda, easybuild etc.). It
scales because the software maintainers themselves will be encouraged
to update project information - such as a reference to a mailing list
- which is the only way to really keep up-to-date in a scalable way.
Wikipedia will use that information too. Wikidata is DRY.

People don't realise it, but in science to find the right tools for
the job is often a challenge. Wikidata will help us create sections
for tools that address certain tasks. For example variant calling in
sequencing data. I and others here have a direct stake in solving this
problem. This meta-information does not belong in Guix, so we need a
place to handle it. When you have a proof-of-concept we can even
consider writing a paper about it.

Will you join our Guix event at FOSDEM? This would be an interesting
working group. I know also a few people outside Guix who will be
interested.

Pj.

  reply	other threads:[~2018-11-01 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  9:44 [Feature idea] Adding wikidata, wikipedia & screenshot-url fields to package-recipes swedebugia
2018-11-01 10:21 ` Pjotr Prins [this message]
2018-11-01 22:33   ` swedebugia
2018-11-02  7:24     ` Pjotr Prins
2018-11-02 11:37       ` swedebugia
2018-11-02 15:37         ` Pjotr Prins
2018-11-01 13:37 ` Amirouche Boubekki
2018-11-01 23:25   ` swedebugia
2018-11-03  7:53     ` Catonano
2018-11-01 15:00 ` Tobias Geerinckx-Rice

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=20181101102150.naklct2uiujtp2rl@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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).