On 25/02/11, James Ausmus wrote: > The QML code is clearly marked as being Apache 2.0 > licensed.
Right, not BSD, but close. > As far as whether I would be personally offended if > you forked my code - I'd certainly appreciate taking > a look at any patches you would want to send my way, > but I won't be upset (I'd even understand!) if you > decide that's an untenable method of contributing > and decide to fork. My concept of "fork" is to push the QML code to my Github account so I can keep working on it in a sane open way. Of course you, or anyone, would be more than welcome to pull whatever my input may, or may not, be. My concern is that I am really keen to start "fiddling" with that kind of interface (excellent job btw) but it's a waste of time if it's not in some open coordinated repo and I obviously don't have write perms to Intels internal repo so Github is the next best. This is great, from my POV we have some potential progress with the essence of what all the future MeeGo UXs should consist of, different QML views of a Qt backend foundation. --markc _______________________________________________ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
