> From: Carsten Munk > Sent: 23 March, 2011 18:09 > I think this discussion and (passive?) agressiveness has gone on for > too long. I would propose that if you have a problem with decisions > made, present a dispute to the TSG stating your exact objections, > potential solutions to the issue and let it be evaluated and let the > answer to the dispute from TSG be the final word. It is a role of the > TSG to solve these kind of disputes. > > We can't be bogged down with flamewars forever and we do need to make > sure that when a decision is made by people nominated in roles where > they should make the hard decisions, it is followed. Or we'll go > nowhere with MeeGo. > > Before any of you point out that Imad from Intel is the only person in > TSG at the moment, that TSG meetings are public and that decisions made > are public record. I personally trust that Imad will be objective and > resolve the dispute properly.
Hello, Thank you for stepping in with this proposal. This is the way to solve it and it should have been applied already earlier. I perfectly agree with you. Since lot of time was anyway lost on the subject, and it's an important subject, perhaps it would make sense to consecrate a wiki page to it, including the main use cases to be solved, the solutions proposed, the test data sets involved, test cases used for measuring the solutions (in production type of environment and background load), and then measurements for each solution (eventually on separate pages). This work anyway needs to be done, actually a lot has already been done, so it is not waste of time. It does not need to happen entirely (including all test cases) before Imad's decision, just a few. If you don't like this, just use email or whatever way you want. But let's set a deadline for this preparation until Monday, so that Imad makes a decision on Monday. Meanwhile the work doesn't have to stop. I am only indirectly involved in the issue, sorry for making too much noise and taking your time away. Basically we can do either way with more or less trouble, just need to make sure it is the right solution, and give chance to the other solution(s) to improve against known requirements. Best regards, Zoltan Kis -- Senior Architect, People Experience (Telephony, VoIP, Instant Messaging, Presence) Meego Devices, Nokia
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
