Earlier quoted context omitted.
“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...
Project Neudora on github in 5, 4, 3, 2...
Computer History Museum Makes Eudora Email Client Source Code Available
31–40 of 152 posts
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#32Damn. The "bad" words have been sanitized. Seeing the programmers' frustrations as they appear in the comments enhances the experience when viewing old code like this.
Even on my own OSS projects I tend not to do that anymore.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#33It's under an open source license too: "The transfer agreement allows CHM to publish the code under the very liberal BSD open source license, which means that anyone can use it for either personal or commercial purposes."
It's also interesting they have completely separate windows and mac code bases.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#34I still use Eudora... heavily .... maybe this is a sign
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#35Earlier quoted context omitted.
“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...
It's a bit weird, just above they say "they decided not to simply grant a license, but to transfer ownership of the code, the Eudora trademarks, the copyrights, and the Eudora domain names to the Computer History Museum". 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…
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#36It's under an open source license too: "The transfer agreement allows CHM to publish the code under the very liberal BSD open source license, which means that anyone can use it for either personal or commercial purposes."
I'm guessing they had to go through the code pretty carefully to make sure they could. I'm seeing embedded PNG, zlib, qt3 and other libraries buried down in there. It's also interesting they have completely separate windows and mac code bases.
At the time I don’t really think that was uncommon.
I mean, you barely had FOSS portable libraries to base the core functionality on, even before you started tackling platform specific issues.
There were different CPU architectures. Machines back then were completely different, with each type having it’s separate types of HW devices and connectors. Etc etc.
Literally nothing were common between PCs and Macs. I’m not surprised at all.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#37Earlier quoted context omitted.
“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...
It's a bit weird, just above they say "they decided not to simply grant a license, but to transfer ownership of the code, the Eudora trademarks, the copyrights, and the Eudora domain names to the Computer History Museum". 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…
You can have Firefox branding if you compile it yourself, but you can't distribute the binaries (Gentoo has a notice about this in the build process). This is why Debian created the IceWeasel package.
The museum might want to preserve the name associated with that piece of history, so Eudora always points to that final release. If the license for the code is BSD, people can of course publish their own ports with new names.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#38Re: Computer History Museum Makes Eudora Email Client Source Code Available
#39"Eudora was specifically designed with the idea that standards are a key to successful adoption. Indeed, the rapid acceptance of the Internet is largely due to the standardization process. Published standards are what allow applications from multiple sources to cooperate with each other. Without standards organizations would only be able to use their own applications together, and not those from outside. Also, by all…
This is beautiful. One of the "so obvious it's invisible" truths of the modern age, and I nearly forgot that Eudora and other pioneers of the age were making a somewhat risky choice to only support standard protocols and eschew the proprietary mailers. Most of them are now long dead yet POP3, IMAP, SNMP chug along. At the time, though, it wasn't so clear.
Re: Computer History Museum Makes Eudora Email Client Source Code Available
#40I uploaded the code to GitHub: https://github.com/avar/rhqben
https://github.com/avar/rhqben/blob/master/Eudora_M_source/V...