spencerone@???:
>> sajolida[at]pimienta.org:
>> Thanks for raising the trademark issue as it honestly never occurred to
>> us. I created a ticket to keep track of our discussion regarding that.
>> https://labs.riseup.net/code/issues/9047 Still, I'm not sure whether
>> we are
>> ready to consider such a debate.
>
> I think it most likely should be trademarked, at least with a ™.
> Dedicate a page on the website to this and we are good to go.
Ok, now I understand better the difference between unregistered and
registered trademarks. I added this info to #9037.
>>> spencerone[at]openmailbox.org:
>>> I would encourage us to be designing Tails, not GNOME or anything else.
>>> Using the styleguides as a reference or as insight into architectural
>>> layout or element/text composition/usage is cool, but copying is no good
>>> and will lead to a product that is not Tails, eventually requiring this
>>> presumably avoided redesign. Also, it allows us to fall into the trap
>>> of blind conformity, by using industry standards as resolutions though
>>> common logic would instruct us otherwise.
>>>
>>
>> Keep in mind that what we ship to our users is only 1% specific to
>> Tails, all the rest is a wild mix of Debian, GNOME, GNU, whatever.
>>
>> See our statement on relationship with upstream:
>> https://tails.boum.org/contribute/relationship_with_upstream/
>
> Yeah, but this mostly, if not only, refers to the puzzle-like structure
> of global FOSS and writing compatible code.
No, those 99% of stuff reused from GNOME, Debian, and others also
include user experience (interactions, appearance, features, etc.).
>> So we are copying 99% of what we do already and Tails couldn't exist
>> otherwise. In that perspective, when we create the 1% of custom Tails
>> stuff we need to pay attention to how it fits in the broader picture of
>> the 99% that we copied. And as far as basic desktop application and
>> integration goes, this is GNOME.
>
> Yes. But there is a difference between copying the functional structure
> of something and copying the style.
Not really as everything ends up being code that we inherit from
upstream: documentation, interfaces, appearance. For the same reasons
that we don't have the capacities to rewrite the functional structure,
we don't have the capacity to rewrite the user experience (or the code
behind it if you prefer). Compare the budget and human resources of any
commercial operating system and the one of Tails and you'll get my point
pretty easily. That's why we insist so much on behind coherent with
them. We don't have the capacity nor the will to rewrite everything
that's "not invented here".
--
sajolida
