Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project

[Erich Eckner]

Hi Martin,

your list looks good, but I'd like to include the following items:

1st:
Configurational changes we deem necessary to make Arch Linux 32 running
and maintainable (e.g. we obviously have a separate mirror list and an
extra keyring). - Or did you mean to cover this in your 2nd point?

2nd:
Recompiling older packages from Arch Linux and/or the Arch User
Repository. (There have been cases where a package was dropped on Arch
Linux, due to it's arcaneness - but x86 users still wanted it)

Aaron, can you give us formal approval on the list of deviations we're
allowed to make while still calling us "Arch Linux 32"?

regards,
Erich

On 13.07.2018 15:01, Martin Michlmayr wrote:
> * Joshua D. Drake <jd at commandprompt.com> [2018-07-12 12:12]:
>> I think it would be good to have a link to the trademark policy,
>> perhaps even in the resolution. It isn't like we haven't heard of
>> FOSS projects getting a little touchy after the fact.
> 
> It might be a good idea to have a (simple) trademark agreement which
> outlines under which conditions Arch Linux 32 can use the "Arch Linux"
> name and under which they would have to rename.
> 
> e.g. recompiling source from Arch Linux without modification is fine.
> Recompiling source from Arch Linux with modification for x86 is ok.
> Recompiling source from Arch Linux with _other_ modification: probably not fine.
> Using Debian instead of Arch Linux: rename ;)
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.spi-inc.org/pipermail/spi-general/attachments/20180716/7b3a93f8/attachment.pgp>