-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe best practice if including code from other projects #242
Comments
page covering licensing for this situation - not linked anywhere yet - partially addresses #239 - tangentially addresses #242, could be extended to address including code from other projects more explicitly - with some additional work (feedback wanted) could be useful to link as another "situation" from the home page
+1. I'd like to know this myself, specifically how authors of abandoned works should be attributed in derived and heavily-modified codebases. |
@pmackay @Alhadis for MIT (and most open source licenses) you have to keep copyright notices and copies of licenses. This is true whether a project is "abandoned" (assume you mean unmaintained) or not. You CAN add your own copyright notice (and even license, if the original license is compatible), but you don't have to. This explains various patterns you see, like
and
and
and
If there are copyright notices in file headers it's a very good idea to keep those as well. You CAN further annotate a I've kept this issue because I agree it would be good to have some very easily understandable information about using others' open source licensed code on choosealicense.com. No great idea of how to do this or existing materials to use have struck me yet. I'll keep this open...suggestions welcome. |
@mlinksva Okay, different question, and I'm not sure if this is the place for it... but since you're site staff, I have an impetus to ask: Would GitHub allow the transfer of my repositories to a willing maintainer if I dropped dead, if I explicitly stated it in a will, or something? I know, stupid question. But this PR got me thinking, and I realised how much I'd hate for a grammar I'd worked so hard on falling beyond the ability of somebody to keep it going. I'm somewhat of a hermit, so I have no friends or "next of kin" I can just offer my projects to if I suddenly cark it. FYI, I've written two grammars that're being used to provide syntax highlighting on GitHub:
There's another grammar pending, and I'm busy working on yet another (probably the most detailed grammar I've written to date). These are also Atom packages, so I'd prefer they be transferred instead of forked... (Sorry for the awkward question, but I'm kind of a forward-thinker...) |
@Alhadis definitely good to think ahead and not a stupid question at all. It is a bit out of scope for this issue and this repo. You should submit your question at https://github.com/contact. Now my unsolicited and probably obvious advice that doesn't directly answer your question:
|
I like having a file called ACKNOWLEDGMENTS(.txt|.md)? and it is what is mentioned in |
As GitHub obviously encourages, some projects will include code from other projects. What is the best thing to do in that situation? Should the originator's copyright info in their license be added to the license file in the new project? Something like this? e.g.
The text was updated successfully, but these errors were encountered: