From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: Re: [PATCH 2] gnunet: description (was Re: [PATCH] gnunet.scm -> various changes (description update, adds gnunet-svn, gnunet-gtk-svn, gnurl)) Date: Thu, 31 Mar 2016 09:24:16 +0300 Message-ID: <20160331062416.GB7964@debian-netbook> References: <874mcd2cl2.fsf@grrlz.net> <87wpomr4jr.fsf@grrlz.net> <20160328164646.GE8174@jasmine> <87oa9yts9p.fsf@grrlz.net> <87egar8x6n.fsf@gnu.org> <87egarfu1w.fsf@grrlz.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alW1o-0006eF-Jx for guix-devel@gnu.org; Thu, 31 Mar 2016 02:24:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alW1k-0000j9-5V for guix-devel@gnu.org; Thu, 31 Mar 2016 02:24:24 -0400 Received: from flashner.co.il ([178.62.234.194]:57034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alW1j-0000ix-QP for guix-devel@gnu.org; Thu, 31 Mar 2016 02:24:20 -0400 Content-Disposition: inline In-Reply-To: <87egarfu1w.fsf@grrlz.net> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Nils Gillmann Cc: guix-devel@gnu.org --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 31, 2016 at 01:02:51AM +0200, Nils Gillmann wrote: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: >=20 > > Nils Gillmann skribis: > > > >> Leo Famulari writes: > > > > [...] > > > >>>> + (description "GNUnet is a framework for secure, distributed, pee= r-to-peer > >>>> +networking. The high-level goal is to provide a strong foundation = of free > >>>> +software for a global, distributed network which provides security = and > >>>> +privacy. GNUnet in that sense aims to replace the current internet= protocol > >>>> +stack. Along with an application for secure publication of files, = it has > >>>> +grown to include all kinds of basic applications for the foundation= of a GNU > >>>> +internet. > >>>> + > >>>> +gnunet-0.10.1 is the last stable release candidate, however for > >>>> +development purposes and keeping up with latest changes, the SVN ve= rsion > >>>> +might be preferable until a new version is released.") > >>> > >>> Do we have a consensus on how to handle this sort of "Guix metadata"? > >> > >> Which metadata do you refer to here? > >> > >> The description is good with the GNUnet project, talked about it > >> with others involved in GNUnet. > > > > It=E2=80=99s not that simple. ;-) > > > > Descriptions for GNU packages are maintained in a canonical place > > outside of Guix (they=E2=80=99re also use for other purposes, such as g= nu.org), > > and we synchronize from them. =E2=80=98guix lint -c gnu-description=E2= =80=99 reports > > differences with said database. >=20 > I have write access in gnunet.org and only need to find some > minutes of focus and concentration to change the description on > the frontpage. But I guess again that is is not that simple > either for Guix? >=20 > > > > Thus, in general, we should keep the canonical synopsis/description for > > GNU packages, and email bug-womb@gnu.org if we think a > > synopsis/description must be changed. >=20 > As far as I understand Christian, he's good with any better > description which does not do total damage to the project. > I got input on the description I added here from most of the > people involved in SecuShare, another project I am involved in > which is part of GNUnet, and it was okay for them. >=20 > > Another comment: should we call this package =E2=80=9Cgnunet-next=E2=80= =9D, like we did > > for =E2=80=9Cguile-next=E2=80=9D? This would make it clear that it=E2= =80=99s a development > > snapshot. (Sorry for not coming up with that idea earlier.) >=20 > I am used to -git, -svn, -vcs naming but I am not fixed to it. I > can rename the two packages to -next, but it might give the > impression of a different software if the added description is > not included. >=20 > Compare the opinion of someone who has never touched gnunet about > "gnunet and gnunet-svn" vs "gnunet and gnunet-next". >=20 As someone who has never gotten past installing and uninstalling gnunet, gnunet-svn sounds like a development branch and gnunet-next sounds like it's almost ready. Other than having read this thread I would choose gnunet-next > gnunet > gnunet-svn > On the other hand it can just as well mark the next version... So > I guess it is okay to name it gnunet-next, gnunet-gtk-next >=20 > > WDYT? > > > > Thanks, > > Ludo=E2=80=99. > > > > >=20 --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJW/MKQAAoJEPTB05F+rO6T1dcQAIPEAoetgXE6H9niGeY7nmvN D39hzxhVYpkTzgklzQHrTxj/XS8U7TONxRAwaAoUlMWeiG1VBqI/mcgc/WZ1+R51 kmUhiS+Ya1GcDuUsf+aImNNjFVyMU7cXUV3bMI3m7E+4KyJZ6O5ZPzpf6pvMkOxv 8qBI/QrBpIKc6JOUHSEMpIUVYCbp6lLCS+TvSmuTGAuCHWc/0a3qLDy/yPcMlJvx Egw3gON8Sn1od0gjQT6ZnOk/v6UZskWtj3E+BigaJCFQW9agXea9FCxU6ggap9iE YldCG70+kJmA+LCJMpGePVzCJF+W+mch1zoviqWPzPgguLNWPoqu6L+80PxJF0k9 5dUQhDliknK9KCRYnJOsKFFo7ZkQ+pciRvEWzgL+KsC+ZFphWVdC6cEYZBoQ5Fyb nAW59vZtbrw3xoqge6tqEgZGrTPel2AAOO9nyVguA3n9FxMmcBnfb0TZrNXl8Dcu awXq1n4Zbc54QntyTScDWML/+otjzJPj8zqdlk1Ox0N5cH3LSs8aQLeUZEi+D/S1 d5/NZ86mApzZIB3opJa1Mxq94IYAGBOru/fxVMFe68oVCu8j70/iop5UIl1SFjN5 cANUqeyXl7DthAFRDj039OuADU9rgGYG3T7BlEPWeMdfFJbxGpR4aPmyBbVZpA4o c7Y0VQ9camXlUc/lEIGO =VOkW -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC--