71–76 of 76 posts
Hello, I'm Gabriel, the original author of Guake. Let me clarify the whole story: In 2006 I had just gotten into college and was learning Python by myself, my English skills (also self-taught) were pretty low and I had to rely a lot on whatever material was available in Portuguese (I'm from Brazil). In 2007 I had an amazing college teacher, the "drop of water in the desert" kind of teacher. He was trying to convince…
Well, as far as I can tell, the Authors file was removed completely. In all of the files that I could find that are old enough for him to have contributed to, his copyright notice remains. In his own branch, the first commit is October 2007 and the vast majority of commits after that are from Lincoln de Sousa. So I don't think anyone was doing anything untoward here. I'm not really familiar with the project, but it d…
yeah they switched to pbr, so AUTHORS file is generated on build. Not tracked on git PS: actually original author is in AUTHORS file
Earlier quoted context omitted.
I only have a working knowledge of git but wouldn't that be equivalent to re-writing the whole history of the repo? Rebasing would give all of the commits a new commit ID and would cause conflicts everywhere. Unless of course you just meant as an interesting way of being able to see the full history rather than suggesting the project adopt it.
Git has the ability to use grafts for this scenario. https://stackoverflow.com/questions/1220557/how-do-i-prepend...
http://www.catb.org/esr/reposurgeon/
https://gitlab.com/esr/git-debubble
https://gitlab.com/esr/git-weave
Some background information provided by ESR, in addition to what you can find on the homepage:
https://groups.google.com/forum/m/#!topic/golang-nuts/WstriK...
Earlier quoted context omitted.
Ship of Theseus is a great argument for crediting the original author, even if it's been 100% re-written over time: The ship would have started from one (or more) expert ship builders, while the continual patching could be done by comparatively-unskilled hands. (Not that this is the case in software, but merely saying that that parable would lend itself to an easy answer as to whether to credit the original or not.)
You could equally argue that Gail's law is applicable. Without someone creating something simple but working it may never have existed.
Hello, I'm Gabriel, the original author of Guake. Let me clarify the whole story: In 2006 I had just gotten into college and was learning Python by myself, my English skills (also self-taught) were pretty low and I had to rely a lot on whatever material was available in Portuguese (I'm from Brazil). In 2007 I had an amazing college teacher, the "drop of water in the desert" kind of teacher. He was trying to convince…
I'm Max @ulidtko, I took over Guake maintenance from Lincoln, did a dozen patches, l10n merges and maybe one release... Together with Pierre we welcomed Gaetan years later.
I'm still using Guake pretty much every day.
It was amazing to contribute, and having burned out from it -- to see the project live on with people continuing contributions & maintenance; and even reaping BountySource rewards for new features! https://github.com/Guake/guake/pull/1415
Really sorry for this situation. It somehow slipped through, I honestly didn't notice it happening. I don't think anyone wished you anything bad, it's just generic inexperience (per the Hanlon's razor).
I, too, remember myself fiddling with copyright lines in translation files. I just had the single goal, to iron out inconsistencies and make adding new l10n's as smooth as possible. Never had intentions to take away credit from noone.
Glad to see you living full life. Sorry again; I'd be among those whose should've noticed and reverted that change. Hope you got a good enough resolution of this issue!
Cheers