Should I leave that there and add notes under that regarding the changes made?
Whatever you do, leave the copyright and license notice(s) intact and don't misrepresent code that you didn't write as your own work. What I sometimes do is add my own copyright notice right above the one from upstream. That makes it clear that I touched the software the last time, so I'm to blame for the bugs.
Also, do I need to have any file that keeps track of all changes? (that sounds like a lot of work)
Put it on an open source code hosting website such as GitHub. That's a good idea anyway, regardless of whether you legally need it. (I don't think you do, but read the LGPL carefully; you have to be able to supply source code for any binary release you did. If you distribute the source code along with the binaries, it should be fine.)
发布评论
评论（1）
无论您做什么，请完整保留版权和许可声明，并且不要将并非您自己编写的代码歪曲为自己的作品。我有时会在上游的版权声明之上添加我自己的版权声明。这清楚地表明我上次接触过该软件，因此我应对这些错误负责。
将其放在开源代码托管网站（例如 GitHub）上。无论如何，这都是个好主意，无论您是否合法地需要它。 （我认为您不会这样做，但请仔细阅读 LGPL；您必须能够为您所做的任何二进制版本提供源代码。如果您将源代码与二进制文件一起分发，应该没问题。
） >我不是律师。
Whatever you do, leave the copyright and license notice(s) intact and don't misrepresent code that you didn't write as your own work. What I sometimes do is add my own copyright notice right above the one from upstream. That makes it clear that I touched the software the last time, so I'm to blame for the bugs.
Put it on an open source code hosting website such as GitHub. That's a good idea anyway, regardless of whether you legally need it. (I don't think you do, but read the LGPL carefully; you have to be able to supply source code for any binary release you did. If you distribute the source code along with the binaries, it should be fine.)
I am not a lawyer.