So, I got a question by someone making a hardware adaptation of MeeGo for hobbyist purposes, not for publishing with an actual device. A project existing outside the current MeeGo.com project so to say.
Is those hardware adaptations, if fully based on RPMs and .ks'es from repo.meego.com considered able to call themselves "MeeGo for X device"? Or what's the best way? "Unofficial MeeGo hardware adaptation for X"? Or are people supposed to use totally different naming and a different theming packages? Parallels can be drawn to for example derivative distributions of Debian not being able to call themselves Debian <something>. Asking these questions because it's better to have that conversation early* than when someone makes a successful derivative users like and project asks them to switch name :) Best regards, Carsten Munk * I'm hoping to see more compliance information on the next TSG meeting but so far compliance seems to have been around devices getting sold with MeeGo and not this scenario. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
