elementary-dev-community team mailing list archive

[Jaap Broekhuizen <jaapz.b@xxxxxxxxx>]

Christian said:

> For what it's worth, the name is meaningless to actual copyright
> disputes. I tend to like if I can see at a glance who's the person to
> talk to for a certain file.


If that is true, then i'd vote for just elementary, if this is not true
then of course we'd have to add the name of the developer who created the
file (and the name of developers who made huge changes). Are the names in
the copyright actually used by people to find out who made the file? Most
of the time it's just the name of the maintainer of a specific project, and
when someone is working on a project they will probably know who that
maintainer actually is. Now for something like granite, where a lot of
files are written by a lot of different people, there it would come in
handy, but i don't know how much of a necessity it would be in the other
projects. At least i cant think of projects that we have other than granite
where multiple devs do really big changes to files.

I could be wrong though :)

--
Jaap


On Thu, Jun 14, 2012 at 2:51 PM, xapantu <xapantu@xxxxxxxxx> wrote:

> Hi,
>
>
> 2012/6/14 Jaap Broekhuizen <jaapz.b@xxxxxxxxx>
>
>> I would vote the second one too, it looks cleaner IMHO, and i don't think
>> we need to have the names of the developers in the source file, those can
>> be found in the about dialog.
>>
> I doubt it is legal : how can you write that there is a copyright, which
> isn't assigned to anyone? No, you can't put the team name, it is not an
> official structure. The day we have a elementary trademark, entreprise, and
> everything, yes, it could work. It is called copyright assignment (and I am
> opposed to it, just keeping the names is good)...
>
> Lucas
>
> --
> Mailing list: https://launchpad.net/~elementary-dev-community
> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elementary-dev-community
> More help   : https://help.launchpad.net/ListHelp
>
>