On 5/31/10, Gaveen Prabhasara <[email protected]> wrote: > Hi Peter, > > Peter Dolding wrote: > >> [email protected] Fedora forbin list is only for items that status is 100 >> percent sure to be legally doomed use it risk dieing inside days. Redhat >> enterprise forbin list include suspect. Also its like other codecs and >> times in the Fedora distributions where you require licenses to use that >> do >> not appear in redhat enterprise at all. >> > Umm,... I'm not sure why my mail id is there. I'm guessing you meant > me to pay some attention to the matter. So here's what I've got to say. > > I'm aware of the situation in Fedora and their position regarding Mono. > I happen to stay close to Fedora matters, and in this matter I actually > happen to agree their stance. > > If you ask me what's my stance about this matter with regards to > MeeGo is, I happen to agree with what David Greaves said [1] on the > other thread. There are many things to consider. However as a project > we can't just casually ignore the concerns and hope for the best. While > I'm also not a "rabid anti-Mono" person, I'm not particularly comfortable > about the legal background either. > > The best part and one of the key points David mentions was about > how to proceed with this matter. I'd like to request you to consider > it too, specially as a person involved with FOSS project. :) Let me > quote David here: > "Maybe the most professional solution would be to continue to > provide polite and reasonable responses to polite and reasonable > questions? However tedious that may feel."[1]
That is the main thing I am after. Number one was the issue though about if not we better now. If it means getting legal advice from FSF and others. Prevention beats cure. I am not rabit anti-mono every time I ask for these legal side issues to be addressed I must be anti-mono or a troll in mono people eyes.(I get sick of it) Sorry I would love to be pro mono but not getting legal answers blocks me. I know the system issues of using JVM's in low memory environments point that out also get called anti-mono. Forget to take note that I have request effective AOT building of mono to avoid the JVM memory issue. I have pulled mono people up on miss measuring memory. Ie saying mono programs use less memory than native. Issue native ends up using less memory that needs to be swapped out. Sad part is most cases when you compare mono to native code version mono is heavy. Tomboy vs Gnote and so on. Targeting embedded market every bit of extra memory required is extra cost to make the device. So care has to be taken on what we include. Even including Java or python base applications should be though about carefully. Yes lower the memory sample disk can use to work the better. If someone wants to use a copy acquired through direct supply paths from Novell so covered by the MS Novell agreement I have no problems I know the limitations of that agreement. Big thing I forgot to say I came to the mailing list in a hope of getting a fast answer that everything was fine and intel or nokia had it covered. That way I could have cut of boycottnovel/techrights doing bad PR about meego its not what a starting out project needs. I did get the article delayed by 24 hours that the novell personal spoted that little message of mine got a 24 hour delay. Defensive requires eyes in the locations that could fire off bad PR to try to stop it before it happens where we can. But to stop it I need paperwork in order. Yes if I am anything I am an anti-troll. If able I will make sure meego only gets good PR. Peter Dolding _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
