I applaud Qualcomm for donating all trademarks and copyrights too, which means literally anyone can recompile it and still call it "Eudora". Unfortunately Eudora is basically three completely different codebases (Windows, Mac, and a rebranded Thunderbird for Linux). I guess only the Windows one is likely to ever be revived.
“The license does NOT allow you to use any of the trademarks or domain names related to Eudora, including Eudora™, www.eudora.com, and www.eudora.org.” — http://www.computerhistory.org/_static/atchm/the-eudora-emai...
Computer History Museum Makes Eudora Email Client Source Code Available
21–30 of 152 posts
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#22Earlier quoted context omitted.
That license means it's essentially dual licensed, and the more liberal license will trump it (BSD), you cannot publish something as BSD and then "downgrade it" afterwards. The license you were forced to accept is probably just a generic license covering all software in the computer history museum for when the owners have _not_ provided a more liberal license.
> The license you were forced to accept I didn't accept it. I'll try to get them to remove those terms, that appeals to me more than agreeing to legal terms I don't intend to abide by.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#23Wonder why they chose not to host on GitHub...
This is meant to provide an archive for the code. A major attraction of using GitHub is to allow easy pull requests and issues. If you're not going to be using those features, it's mostly useless when you already have your own infrastructure for hosting data. Lastly, if you're using a version control system other than Git, GitHub is not going to work well.
Besides, I find it a whole lot easier to just casually browse through code on Github rather than download 129 megs of eudora_w_source.zip, extract it somewhere and rifle through it...
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#24Re: Computer History Museum Makes Eudora Email Client Source Code Available
#25Of course I found its UI frustrating enough (for reasons I barely remember now) that I wound up installing something else to use on my workstation.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#26I applaud Qualcomm for donating all trademarks and copyrights too, which means literally anyone can recompile it and still call it "Eudora". Unfortunately Eudora is basically three completely different codebases (Windows, Mac, and a rebranded Thunderbird for Linux). I guess only the Windows one is likely to ever be revived.
“The license does NOT allow you to use any of the trademarks or domain names related to Eudora, including Eudora™, www.eudora.com, and www.eudora.org.” — http://www.computerhistory.org/_static/atchm/the-eudora-emai...
So it's the CHM who is barring people from using the name. The relevant clause must be this: "Neither the name of Computer History Museum nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission." Is this really "BSD license", if the name is off-limits? This looks like an extra clause to me. Honest question.
EDIT: also, that clause mentions the names of contributors, not of the actual software. So they would have to argue that Eudora is barred by "contributor Eudora Inc." -- does that company even exist anymore?
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#27I still use Eudora... heavily .... maybe this is a sign
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#28Re: Computer History Museum Makes Eudora Email Client Source Code Available
#29Wonder why they chose not to host on GitHub...
This is meant to provide an archive for the code. A major attraction of using GitHub is to allow easy pull requests and issues. If you're not going to be using those features, it's mostly useless when you already have your own infrastructure for hosting data. Lastly, if you're using a version control system other than Git, GitHub is not going to work well.