Reputation
Next privilege 125 Rep.
Vote down
Badges
2
Impact
0 people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Nov
23
comment What's the right way to fork/re-use code from an open source project?
@TechnikEmpire Chronological order makes sense, but for a contributors list rather than a copyright notice? I thought copyright notices might be better arranged according to the sections of code they apply to and the value/quantity of those sections in the package. It's useful to have a list of the people you need to contact, in order of priority, if you want to change something about the license. So if you get permission from the first few, but not the last, you have a smaller amount of code to recreate if you are determined to make the change. I wonder what Linus does?
Sep
24
awarded  Autobiographer
Apr
4
comment What's the right way to fork/re-use code from an open source project?
At what point should the main license file have your copyright notice above the original authors'? When your SLOCs exceed 200% of the original project SLOCs? 300%? If the project you forked ends up being one of many librares or modules within your project?
Jan
13
awarded  Supporter
Dec
15
comment Do TODO comments make sense?
Eclipse highlights them and consolidates a list of them for you as well. And writing a TODO comment while the thought is on your mind is not a bad idea, even if you never get around to actually DOing it. Some magnanimous soul may actually be browsing the code looking for things to do (OSS).