LimeSurvey/LimeSurvey — comment on commit a54baec19ce68734fe4e878873e8b560234e2d06
File:  line 0
By TMSWhite:

Carsten-

I think it's critical to get the repository right for personal, community and maintenance reasons.

Although I'm thrilled that 1.92 is now released, and people can now use Git to more easily add features, I'm dismayed that my entire history of contribution could be lost. I've devoted all of my spare time for 10 months to the the project, totally re-writing the front-end, but a newcomer reading the Git history wouldn't see my name listed at all on GitHub after the garbage collection runs. Instead, if people do "blame" on the code, it will look like EM was written by the most recent person do do a merge origin/dev dev. Losing the whole history of my contributions would be incredibly upsetting.

If we can't get the attributions right, other members of the community may feel the same way. People may be less inclined to donate their time and code if there is no guarantee that their contributions will be remembered.

Lastly maintenance will be much harder if we don't get this right. It will be hard for the community to collaborate if they can't use Git to figure out who is really authored and modified sections of code rather than who did the most recent merges.

So, yes, although it may be a bit of a pain to fix this, and the 10 people who forked LS would need to re-clone their repositories, I think it's critical to fix this.

Perhaps Dragooon can help. I'm also expecting you could do a new fork and branchto manage the fix, and once it is right in a new branch, then merge or re-base it back into master (e.g. so that this fix doesn't have to slow down development of Yii)

/Tom