Maxime Devos writes:
> Upgrading the GPLv2-only code might be dificult if multiple people hold
> the copyright, so for the GPLv2-only code, it might be a good idea to still
> require copyright assignment.
When we did it for Mercurial, going from GPLv2 only to or later took
years and a *lot* of
Maxime Devos, le ven. 13 août 2021 15:42:37 +0200, a ecrit:
> so for the GPLv2-only code, it might be a good idea to still
> require copyright assignment.
The GPLv2-only code is essentially the pfinet stack from Linux, for
which we don't have any assignment anyway. But again, this is getting
repla
Hi Adriano and Ricardo,
I'm also _very_ interested in keeping issues in the same repo as code
and I'm really envious of Fossil users [1] :-D
Ricardo Wurmus writes:
[...]
> Many years ago I used Bugs Everywhere
> (https://bugs-everywhere.readthedocs.io/en/latest/) for my
> personal projects.
On Fri, 13 Aug 2021, jbra...@dismail.de wrote:
Hey Guix,
Apparently there is going to be a virtual Packaging Conference this year:
https://packaging-con.org/
[…]
* Submissions close: 31 August 2021
Thanks to you and Dong Carl on IRC for sharing! This looks like a very
interesting eve
Damien Zammit schreef op do 12-08-2021 om 12:18 [+1000]:
> Hi Ludo,
I'm not Ludo, but here's my response anyway.
(I'm interested in doing some small and larger things with the Hurd,
but I keep being occupied by other things and I'm having a hard time
understanding the inner workings ...)
> On 11
Hi Adriano,
some time ago, in the context of an on line conference about
Guix,
someone suggested me that the bitcoin community had run a survey
about
available solutions for issue tracking in git
Was it perhaps Carl Dong?
I don't remember the name of such person and I am wondering if
amy
Hey,
> So I’d suggest turning that into ‘publish?’, defaulting to #t.
Yeah, you're completely right, I reversed the logic with:
cfd2442488971420289a12d5ca8f07816e1149bf.
Thanks,
Mathieu
