WhereYouGo icon indicating copy to clipboard operation
WhereYouGo copied to clipboard

Clarify file header: copyright, author

Open bekuno opened this issue 5 years ago • 7 comments

In WhereYouGo are currently on most source files header with a license information and partly a author information. In c:geo is this not realized.

We should dicuss and define a standard procedure for the future.

bekuno avatar Mar 13 '20 21:03 bekuno

You mean it like described or the other way around?

Lineflyer avatar Mar 13 '20 22:03 Lineflyer

This is a open discussion.

In old files in WhereYouGo - see e.g. https://raw.githubusercontent.com/cgeo/WhereYouGo/master/src/main/java/menion/android/whereyougo/geo/orientation/IOrientationEventListener.java - is a GPL disclaimer and an author tag.

Current point for starting this discussion is PR #40 with an new file, see https://raw.githubusercontent.com/cgeo/WhereYouGo/c2856f7dbce45c2f9a9e5bb80e4b350524c963b2/src/main/java/menion/android/whereyougo/network/activity/OpenLocalActivity.java

For me - I can live well with the way it is currently handled in c:geo. I would propose not to include this parts.

Maybe there was such a discussion in c:geo before?

bekuno avatar Mar 13 '20 23:03 bekuno

I remember this non resolved issue: https://github.com/cgeo/cgeo/issues/749

Is there any common practice defined for the different licenses?

Lineflyer avatar Mar 13 '20 23:03 Lineflyer

see https://en.wikipedia.org/wiki/GNU_General_Public_License in general

see https://www.gnu.org/licenses/gpl-howto.en.html for source code recommendation

bekuno avatar Mar 15 '20 01:03 bekuno

These licenses are based on the Copyright that you have to claim explicitly in some countries (e.g. USA). We don't have a CLA, so if we want to do any legal stuff, we have to ask anyone who has contributed to the file for their permission or support.

SammysHP avatar Mar 15 '20 06:03 SammysHP

@SammysHP What do you suggest?

bekuno avatar Mar 15 '20 11:03 bekuno

I'm not a legal expert, so I can't really make any suggestions. But I think we should

  • be careful to not remove an explicit copyright line
  • use/adopt a CLA
  • require all future contributors to accept the CLA
  • try to ask a legal expert
  • not think about this because we don't have the resources to enforce copyright/license violations in court anyway

SammysHP avatar Mar 15 '20 12:03 SammysHP