4

Attribution in projects. Etiquette.

Submitted by xxi in programming (edited )

A while ago I added extra functionality to a piece of software which got merged into the projects main branch. A day or two later I added some code to deal with cross-platform compability.

The lead developer asked me if I'd consider to transfer some code from another similar application. Hesitated to do it at first, my curiosity won and I did it. I liked the challenge.

My contributions was admittedly relatively small. Went off to do other things for a couple of weeks. Checked in it recently. Never got any attribution (well, people can see it in the git logs and stuff like that), didn't bother me. What I wrote was trivial, at least as far as I was concerned.

The other day the application version numbering got bumped up, the only new features mentioned was my changes. So yeah, I didn't spend days on what I did, but seeing as only my code was said to be the new features I started to think it was sort of odd. The contributions was good enough to be described as "selling points", but not a mention.

I've mucked around with programming on my own, but I'm pretty new to collaboration. Is this acceptable? How much do you invest before you ask for attribution? In the latter case how would you do that?

[Too many post-post edits. Tired.]

Comments

You must log in or register to comment.

1

Fossidarity wrote

What kind of attribution are you talking about, do you want to receive money or just a "thank you"?

In the case of the "thank you", it's completely up to the maintainer but if someone put the effort into making your software better some credits would be highly recommended, especially if you want people to keep contributing..

3

xxi wrote

Wasn't anything monetary. I did it for the joy of it and because it is free software that hasn't changed. So in light of the latter I wasn't expecting anything.

As I mentioned, it was only when I saw the notification for a new release I even thought about it. Thank you.