Dnia poniedziałek, 14 maja 2012 o 12:46:14 Alexey Eromenko napisał(a): > I have one GREAT IDEA: > Trademark enforcement !
Oh my, here we go. -_-' > Once a good open-source Skype-like project is born, with central > registry, and firewall bypass, it *should* use it's own trademark > that defines that forks must re-name themselves. > Call this project "The Unique". > > I.e. if a forker wants to change the code to point at a different > central repository, he should be forced to change project name as > well. (like FireFox -> Debian's IceWeasel trademark fork, due to > inability to backport security patches to old versions of > FireFox-proper.) As you yourself called upon Firefox/IceWeasel issue, you should already know why this is a *bad* idea. > So all users whom get the original "The Unique" project, they all > are guaranteed to use central registry, and this guarantee can be > enforced by project trademark, rather than code licensing. > > In a similar way, Red Hat is protecting their brand, and CentOS > cannot use Red Hat's trademark, but can use it's code. I have a better idea: use primarily protocol names, instead of application/project names. XMPP instead of Pidgin. E-Mail instead of Thunderbird. See - this works! Diaspora instead of Joindiaspora.com. SIP instead of Ekiga. Now, we can have a (semi)central repository protocol for federation/search, and that would just mean projects like Thunderbird or Pidgin, or Ekiga would have to simply implement this protocol - which would be treated as a "feature" instead of "infringement on freedom of developers". The best part is: all the above mentioned protocols use the user@server scheme. -- Pozdrawiam Michał "rysiek" Woźniak Fundacja Wolnego i Otwartego Oprogramowania
signature.asc
Description: This is a digitally signed message part.