Re: [MeeGo-dev] [MeeGo-community] MeeGo as a vehicle for Qt-based products?
On Oct 1, 2011, at 11:28 AM, Kok, Auke-jan H wrote: Snip I've been asking the same questions as everyone else. If I get answers back that I can share, I most certainly will. For now, I'd like to ask everyone to submit questions to Dawn Foster, and keep asking. Answers will come - be patient. Please no :) I really do read all of the mailing list posts here, so continue to use this is as the place for questions and discussion. Sending it to me individually makes it less likely that you will get an answer, not more likely. Right now, there are still many unanswered questions because we just don't have answers to many of the technical questions yet. People are very focused on getting the code out into the repos so that we can start having productive discussions about the project based on the code. Right now, we'd be guessing along with everyone else on many of the questions. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Call for Participation for LinuxCon Brazil ends on July 22
On Jul 22, 2011, at 1:20 PM, Vinícius Costa Gomes wrote: Hi Dawn, On Wed, Jul 20, 2011 at 2:35 PM, Foster, Dawn M dawn.m.fos...@intel.com wrote: We will be having MeeGo Mini-Summits at the LinuxCon events this year in Vancouver (August 17 - 19), Prague (Oct 26 - 28) and Brazil (Nov 17 - 18). The Mini-Summits are basically a MeeGo track with 4-5 sessions at each of the events. If you want to present at these events, you need to submit a session through the normal Call for Participation process. The Call for Participation for Brazil ends on July 22: http://events.linuxfoundation.org/events/linuxcon-brazil/cfp From the site: All submissions must be received before midnight September 1, 2011 PDT. Ah, yes. They changed the deadline, so no hurry on submissions :) Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Call for Participation for LinuxCon Brazil ends on July 22
We will be having MeeGo Mini-Summits at the LinuxCon events this year in Vancouver (August 17 - 19), Prague (Oct 26 - 28) and Brazil (Nov 17 - 18). The Mini-Summits are basically a MeeGo track with 4-5 sessions at each of the events. If you want to present at these events, you need to submit a session through the normal Call for Participation process. The Call for Participation for Brazil ends on July 22: http://events.linuxfoundation.org/events/linuxcon-brazil/cfp The audience for these events includes Software Developers, Linux IT Professionals, Corporate End Users, Senior Business Executives, IT Operations Experts, System Administrators, Students, Media and anyone else with an interest in the Linux ecosystem. I encourage anyone to submit a session! Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] LinuxCon Brazil Prague: Submit MeeGo Sessions by July 8!
On Jun 14, 2011, at 12:16 PM, Foster, Dawn M wrote: We will be having MeeGo Mini-Summits at the LinuxCon events this year in Vancouver (August 17 - 19), Prague (Oct 26 - 28) and Brazil (Nov 17 - 18). The Mini-Summits are basically a MeeGo track with 4-5 sessions at each of the events. If you want to present at these events, you need to submit a session through the normal Call for Participation process. Note that the call for participation for Vancouver is closed and talks should be selected / announced in the next few days. The Call for Participation for Prague ends July 8: http://events.linuxfoundation.org/events/linuxcon-europe/cfp The Call for Participation for Brazil ends on July 22: http://events.linuxfoundation.org/events/linuxcon-brazil/cfp The audience for these events includes Software Developers, Linux IT Professionals, Corporate End Users, Senior Business Executives, IT Operations Experts, System Administrators, Students, Media and anyone else with an interest in the Linux ecosystem. I encourage anyone to submit a session to either of these events! Just a friendly reminder that MeeGo session proposals for LinuxCon in Prague must be submitted by July 8. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] LinuxCon Brazil Prague: Submit MeeGo Sessions by July 8!
On Jun 14, 2011, at 12:16 PM, Foster, Dawn M wrote: We will be having MeeGo Mini-Summits at the LinuxCon events this year in Vancouver (August 17 - 19), Prague (Oct 26 - 28) and Brazil (Nov 17 - 18). The Mini-Summits are basically a MeeGo track with 4-5 sessions at each of the events. If you want to present at these events, you need to submit a session through the normal Call for Participation process. Note that the call for participation for Vancouver is closed and talks should be selected / announced in the next few days. The Call for Participation for Prague ends July 8: http://events.linuxfoundation.org/events/linuxcon-europe/cfp The Call for Participation for Brazil ends on July 22: http://events.linuxfoundation.org/events/linuxcon-brazil/cfp The audience for these events includes Software Developers, Linux IT Professionals, Corporate End Users, Senior Business Executives, IT Operations Experts, System Administrators, Students, Media and anyone else with an interest in the Linux ecosystem. I encourage anyone to submit a session to either of these events! Just a friendly reminder that MeeGo session proposals for LinuxCon in Prague must be submitted by July 8. On Jul 7, 2011, at 1:22 PM, Randall Arnold wrote: Are you just looking for developer sessions, or could this be shared as an FYI to meego-community list? Given the audience, I think technical sessions are probably the focus. Anyone can submit a session, but I thought that the dev list was the best choice for this particular event. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] LinuxCon Brazil Prague: Submit MeeGo Sessions by July 8!
We will be having MeeGo Mini-Summits at the LinuxCon events this year in Vancouver (August 17 - 19), Prague (Oct 26 - 28) and Brazil (Nov 17 - 18). The Mini-Summits are basically a MeeGo track with 4-5 sessions at each of the events. If you want to present at these events, you need to submit a session through the normal Call for Participation process. Note that the call for participation for Vancouver is closed and talks should be selected / announced in the next few days. The Call for Participation for Prague ends July 8: http://events.linuxfoundation.org/events/linuxcon-europe/cfp The Call for Participation for Brazil ends on July 22: http://events.linuxfoundation.org/events/linuxcon-brazil/cfp The audience for these events includes Software Developers, Linux IT Professionals, Corporate End Users, Senior Business Executives, IT Operations Experts, System Administrators, Students, Media and anyone else with an interest in the Linux ecosystem. I encourage anyone to submit a session to either of these events! Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] (not) refocusing meego-dev, was: Re: Howto lock screen orientation in MeeGo/Tablet 1.2 ?
On May 10, 2011, at 1:16 PM, Attila Csipa wrote: On Monday 09 May 2011 18:22:17 you wrote: This has been discussed - and agreed before - but the changes never seemed to happen :-( The suggestion to rename the mailing lists was discussed but never agreed to. I, for one, don't believe that renaming the list will solve the Just out of curiosity, who exactly needs to agree (or, to put it another way, who disagreed) ? I kind of recall pretty much everybody either agreeing or at least liking the idea at some point (see http://lists.meego.com/pipermail/meego-dev/2010-August/005082.html ) but then the whole thing seem to have taken a U turn somewhere off-list between that moment and the message you linked to. Mailing list creation, naming, etc. falls under the community office, so I typically make the final decision on mailing list changes. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Howto lock screen orientation in MeeGo/Tablet 1.2 ?
On May 7, 2011, at 2:33 AM, Andrew Flegg wrote: On Sat, May 7, 2011 at 05:56, Randall Arnold tex...@ovi.com wrote: On Fri, 2011-05-06 at 16:31 +0200, Cornelius Hald wrote: On Fri, 2011-05-06 at 07:20 -0700, Foster, Dawn M wrote: Please post future application development questions to meego-sdk. Ah sorry. I thought meego-sdk is for the development of the SDK... I think I made that mistake before. Somehow the name is not very intuitive :) I have to agree with Conny. Maybe a rename to meego-app would make more sense... This has been discussed - and agreed before - but the changes never seemed to happen :-( The suggestion to rename the mailing lists was discussed but never agreed to. I, for one, don't believe that renaming the list will solve the problem for reasons already discussed. To refresh your memory :) http://lists.meego.com/pipermail/meego-community/2010-December/002922.html Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Howto lock screen orientation in MeeGo/Tablet 1.2 ?
On May 6, 2011, at 6:36 AM, Cornelius Hald wrote: On Fri, 2011-05-06 at 15:21 +0200, Thiago Macieira wrote: Em Friday, 6 de May de 2011, às 15:16:32, Cornelius Hald escreveu: On Fri, 2011-05-06 at 15:05 +0200, Thiago Macieira wrote: Em Friday, 6 de May de 2011, às 14:46:15, Cornelius Hald escreveu: I thought I'll try a workaround and use MTF only for rotation. Unfortunately it looks like that's not that easy since MWindow and QWidget are not quite compatible. I really hope we get some framework support for that. You're using QWidget? I'm using QDeclarativeView as my root widget, which is a QWidget. How else could I use QML? Can I somehow use QML without QDeclarativeView? Ah, no problem then. But you need to get the sensors information from the Mobility Sensors and apply the transform yourself and animate however you want. Components (both of them) do it for you. Wouldn't a work-around be to rotate my root QML item? If yes, where do I get the physical orientation of the device from? Is there Qt API for that? Yes, use the Sensors. Alright. I'll look into this over the weekend. Let's see how I can do that in a way compatible with Maemo5 and Symbian. Quick reminder that meego-dev is for questions about development of the MeeGo distribution, not application development. Application development questions should be in meego-sdk, which is where the people working on the sdk, apis and other application development participate. Please post future application development questions to meego-sdk. Also see: http://wiki.meego.com/Community_communication http://wiki.meego.com/Mailing_list_guidelines Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] How to create account on build.meego.com
On May 4, 2011, at 5:28 PM, Yuan, Feng wrote: Rudolf, Thanks so much, The url http://wiki.meego.com/Build_Infrastructure/Packagers_Developers#How_to_get_started is much helpful. First thing to do is file a bug at MeeGo bugzilla , then ask lbt/X-fade on IRC at irc.freenode.net #meego This may not be the right solution for you depending on what you need to build (unfortunately, your original email didn't have enough details about *why* you needed the account). If you need an account on our main build system (build.meego.com) because you are working on building images related to work on the MeeGo distribution, they you probably need to talk to Anas Nashif about getting your account on build.meego.com. If you need to create other images, you may need an account on the community OBS, which is where most of the unofficial images and some apps live. lbt / x-fade manage the community OBS infrastructure. Obviously, we need to clean up the wiki documentation, which right now is a bit of a mess when it comes to OBS / build systems, since the community OBS information is mixed with the details about build.meego.com. We need to make it easier for people to understand which OBS access they need and then clearly delineate the instructions / policies for each of the 2 systems, which are very different in some areas. Right now, things seem jumbled together with community OBS instructions mixed with build.meego.com. We seen several people confused by this documentation lately, so we need to work to clean it up. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego garage garage_data.xml is not there, redirect by 301 permanently?
On May 3, 2011, at 8:25 PM, Deng, Ying An wrote: Bonjour, Garage failed to start, and the garage_data.xml downloaded from server says it was moved 301 permanently? Can anybody help? I think Bob Spencer is looking into this issue. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] LinuxCon CFP Deadline is April 22 - Need MeeGo Submissions
On Apr 15, 2011, at 2:33 PM, Foster, Dawn M wrote: The Call for Participation (CFP) deadline for LinuxCon North America is April 22, 2011. We are planning to have a MeeGo track at the event, but we need you to submit sessions talking about MeeGo! Please go to http://events.linuxfoundation.org/events/linuxcon/cfp to learn more about the conference and submit your session. Just a friendly reminder that submissions are due tomorrow (April 22). I'd love to see a big MeeGo presence at LinuxCon North America. Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] LinuxCon CFP Deadline is April 22 - Need MeeGo Submissions
The Call for Participation (CFP) deadline for LinuxCon North America is April 22, 2011. We are planning to have a MeeGo track at the event, but we need you to submit sessions talking about MeeGo! Please go to http://events.linuxfoundation.org/events/linuxcon/cfp to learn more about the conference and submit your session. Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [MeeGo-community] Travel sponsorships to Spring 2011 MeeGo Conference in San Francisco
On Apr 13, 2011, at 10:13 AM, Dan Leinir Turthra Jensen wrote: On Wednesday 13 Apr 2011 18:09:10 Brian Warner wrote: Hi everyone, If you plan to apply for a travel sponsorship to the May conference in San Francisco, *please register for the conference by this Friday, April 15.* Please note, applications will only be accepted through the conference registration process. We will know fairly soon which travel has been approved, and will send out notifications then. Best, Brian As some people who propose talks are waiting to hear back about that before registering (i know i'm not alone in this), what would you suggest we do? Speaker announcements will go out today or tomorrow, so you'll still have time to register for sponsored travel before the deadline. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] FW: execute MTF application by command line error
On Apr 11, 2011, at 12:57 AM, Pai, Cary wrote: Hi, I have a simple MTF application, I want to get the error message from this application, so I want to launch the application from command line, and I can easily get the error message from command line, but after I launch the MTF application, I get error message about : “ERROR : No DBUS session bus found, Exiting now. Please make sure that a dbus session bus is running…….”, BTW if I launch the application by the desktop ICON(create the desktop icon by myself), it can be run successfully. Quick reminder about mailing list policies, since this question should have been posted to meego-sdk, not meego-dev. MeeGo-Dev: Development on the MeeGo distribution - not for application development or user level questions MeeGo-sdk: MeeGo application development - using the SDK / APIs and developing applications for MeeGo. More details about our mailing lists policies: http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
On Apr 5, 2011, at 7:36 AM, Rusty Lynch rusty.ly...@intel.commailto:rusty.ly...@intel.com wrote: On 04/05/2011 01:40 AM, 陈鲍孜 wrote: Aha, the mouse can work even though there is no cursor. So, to support my touch screen, does the work relate to device driver or userspace library outside kernel. I’d like to help if possible. You need a fix for the device driver... specifically the driver needs to support XInput2 So, the best way to contribute a fix for this is to submit a patch for the driver? Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Technical Steering Group Meeting: New Day / Time
On Apr 2, 2011, at 6:53 AM, Jeremiah Foster wrote: On Fri, Apr 1, 2011 at 8:31 PM, Foster, Dawn M dawn.m.fos...@intel.com wrote: I wanted to let everyone know that we have a new time for our Technical Steering Group meetings. While the 20:00 UTC meetings were convenient for the Americas and Europe, it was very difficult for people in Asia to participate. Can you explain the decision making process behind this decision? Here's the logic ... Needless to say, scheduling global meetings is challenging, and the time will be inconvenient for some set of people in order to be able able to include a majority of time zones. Clearly, our previous TSG meeting time, 20:00 UTC, Noon Pacific and 2:00 / 3:00 am in eastern Asia was making it nearly impossible for people from Asia to attend, and the TSG had been receiving requests to move the meeting to a time that was more Asia-friendly. I sat down with a spreadsheet marked with times for US west coast, western Europe and eastern Asia, which seems to be where most of the people working on MeeGo are located, so I tried to optimize for these 3 locations. I put standard working hours in green, yellow for times 2 hours outside of working times and red for everything else. Since we've (U.S. west coast) had the meeting in the middle of our workday up to now, we thought it was only fair to give us the red time (now 11PM), western Europe was yellow / green (6am / 8am for most people) and green for Asia (2pm / 3pm for most). The other time we considered, based on the red / yellow / green chart, was 6am pacific, 2pm / 4pm western Europe and 9pm / 10pm in eastern Asia. In this scenario, Asia would again get the most inconvenient time, which did not seem fair to me. I see this not as something that gets decided once and never changed. I expect these meetings to move around in time to share the burden of early / late meetings and to adapt to locations where we have people working on MeeGo. Naturally MeeGo needs to have times that are friendly to all regions but this decision seems to have been made without any consultation whatsoever with MeeGo developers. In all fairness, I did post this new time to the mailing lists almost 2 weeks in advance of the first meeting to give people time to ask questions or voice objections. If you have a better time that works for more people than the current time, I encourage you to propose it. Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Technical Steering Group Meeting: New Day / Time
I wanted to let everyone know that we have a new time for our Technical Steering Group meetings. While the 20:00 UTC meetings were convenient for the Americas and Europe, it was very difficult for people in Asia to participate. The new TSG meetings will be on Thursdays at 06:00 UTC (Wednesday at 11PM Pacific), which puts the meetings in the early morning for Europe, late evening for the US and the middle of the day for Asia. The first meeting will be on April 14 at 06:00 UTC (April 13 11PM Pacific). You can view the meeting in your time zone here: http://www.timeanddate.com/worldclock/fixedtime.html?month=4day=13year=2011hour=23min=0sec=0p1=202 More TSG meeting details can be found here: http://wiki.meego.com/Technical_Steering_Group_meetings Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [PATCH] Fix orientation to match change QML orientation fixes.
On Mar 28, 2011, at 7:45 AM, Rusty Lynch wrote: On Friday I pushed all the UX related source repositories to gitorious @ https://meego.gitorious.org/meego-ux, with the plan of taking advantage of the merge request mechanism for reviewing/accepting incoming patches. Please convert this (and the other related patches) to merge request and give me a chance to try out the merge request mechanism. Hi Rusty, We should talk about this. We have a process that people are being asked to follow for patches that doesn't include merge requests. http://meego.com/about/contribution-guidelines If we need to change the process, I'm ok with it, but we need to talk about this across the entire meego project and figure out when we want merge requests vs. patch submissions. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Idle hands are the devil's tools, aka the MeeGo SDK installer
On Mar 25, 2011, at 11:31 AM, Attila Csipa wrote: Warning. Agitated rant ahead. In a moment of Friday afternoon boredom following a tweet about a certain competition I decided to check out the state of the 'official' offering and got the Linux install from http://appdeveloper.intel.com/en-us/meego-sdk-suite. Smallish thing, an installer I think to myself, okay... Are you sure ? Of course I'm sure. It says it wants sudo and stuff... well, okay, I would have preferred to do the apt-getting myself if that's what it does anyway... I know, what kind of idiot sudos some random installer from the Internet... Well, I did happen to have a previous install on my otherwise bog-standard Lucid hack-machine and the installer happily offers to remove 6-7 packages from that. Says continue with existing not recommended, well, okay, then proceed with remove... And yes, I know, that's a double fail, I asked for it (cue laugh). As it turns out, the eager beaver installer apt-get bloody *force* removed pretty much all of my Kubuntu install, all the way down to kdm. WTF ? B ut you said just 6-7 packages... (haha, sucker !). But a fail is a fail only if you don't learn from it, so let's see what we can learn from this incident (apart from saying 'no thanks' to stupid sudo-requiring installers even if they come from official sources). Checking out the installer script you can see what caused the meltdown: echo MeeGo SDK components found. echo $PKGS setFontColor red echo -e The following packages are installed and will be uninstalled\n \ prior to installing the MeeGo SDK: echo$PKGS setFontColor blue echo -e Would you like to uninstall all previously \ installed MeeGo SDK components now?\n \ \t(u)ninstall now\n \ \t(s)kip uninstall and proceed (not recommended)\n \ \t(e)xit installation read -p Select option (u/s/e): setFontColor default if [ $REPLY == u ] [ $REPLY != U ]; then if [ $OS == Ubuntu ]; then apt-get autoremove -y $PKGS \(is this safe / necessary ?) I don't know who asked that there, but let me answer. I don't know if it's necessary, but it's VERY not safe (I'll refrain from using derogatory terms this time). You display the packages YOU want to uninstall and then tell apt to remove whatever IT thinks is right (along with, you know, dependencies). What the frack happened to apt-get --just-print (dry-run) and then proceeding ? And I thought the QtSDK is sometimes a bit rough around the edges and people are sometimes too heavy criticizing error-prone SDK setups... but that's peanuts compared to this monster-fail, seeing apt kill your install was not a pleasant sight (now I know how people accidentlaly typing rm -rf / feel). Not. Frackin'. Funny. At. All. Sorry about the agitated mail, now I have the weekend fun of a devel machine to setup, instead of doing something productive like the initial idea from an hour ago of publishing something to AppUp developer challenge by using the official tools in the process. I guess yo u can call that learning the hard way. End of rant. And have a nice day. I'm looking into this now to get that installer pulled off of the website and fixed. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Idle hands are the devil's tools, aka the MeeGo SDK installer
On Mar 25, 2011, at 12:31 PM, Attila Csipa wrote: Please do. I would also recommend a *thorough* review for the whole script. Absolutely. The Linux SDK has been removed from the website, and we're doing a thorough review of the code now. The team was already in the process of re-writing that code anyway (unaware of this particular bug) to make other improvements. We hope to have a new version out next week (assuming QA goes well on this new code), and you can be sure we're testing some additional use cases to make sure we don't have a repeat of your issues. Thanks for all of your detailed descriptions about the problems. They were very helpful in narrowing down the issue! Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Session/BoF Proposals for MeeGo Conference due in 9 hours
This is your final reminder that session proposals and Birds of a Feather (BoF) proposals are due today at 23:59 PST (in just 9.5 hours). http://sf2011.meego.com/program/call-session-proposals Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] updated MeeGo compliance spec available for review
On Feb 4, 2011, at 11:32 AM, Bernd Stramm wrote: On Fri, 04 Feb 2011 21:21:04 +0200 Antti Kaijanmäki antti.kaijanm...@nomovok.com wrote: On Fri, 2011-02-04 at 11:57 -0700, Wichmann, Mats D wrote: Antti Kaijanmäki wrote: ... last someone talked about kernels, there was a plan to list manadatory parts of the kernel config in the next spec (1.2), although not in this one. is that good enough? I think IPv6 is mandatory for any product that comes out these days. Even more importantly now that the IPv4 address pool has finally been completely depleted. So yes I think MeeGo 1.1 compliance spec should mention at least even vaguely that IPv6 is required if you don't want to specify any mandatory kernel configuration at this time. On the other hand if you think nobody is going to release MeeGo 1.1 product then this can wait to 1.2 ;) Kernels have supported IPv6 for years, unless they are specifically configured not to. It would be nice if key core applications would also support it. :Like ConnMan for example. Currently the ConnMan applet blissfully ignores IPv6 even if you are connected: https://bugs.meego.com/show_bug.cgi?id=10878 ConnMan actually supports ipv6 now, and they are working to make the implementation better. As you said, the applet on the MeeGo netbook unfortunately doesn't give people the options needed for ipv6. So, this is more of a user interface issue, rather than a core application deficiency. This doesn't reduce the need to get it fixed, but it should be relatively easy to add support in the interface for ipv6, since it is already supported in ConnMan. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Source code location of Meego Netbook Contact application
On Feb 2, 2011, at 6:17 AM, rajeevranjan.ku...@wipro.com rajeevranjan.ku...@wipro.com wrote: Hi I am planning to add some enhancement to Meego netbook contact application. Please help me to find the source code on Meego. Form where i can download the source code. I found this application on my Meego netbook under below link: Applications-office-Contacts. The source files can be found in the repository. For example: http://repo.meego.com/MeeGo/releases/1.1/netbook/repos/source/ Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] QT creator stuck at Cleaning up remote leftovers first
On Jan 5, 2011, at 1:10 PM, reddweb wrote: I am trying to compile imagegestures example from QT SDK examples, and launch on a real netbook, which has meego/sdk working. This is a bit off-topic for meego-dev, so I recommend posting your question on meego-sdk, instead. You can get more details about our various mailing lists here: http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo migration path?
On Dec 14, 2010, at 8:45 AM, Jechlitschek, Christoph wrote: Hi all, I was wondering if there exists a migration path from MeeGo 1.0 to MeeGo 1.1 and later to MeeGo 1.2. This is very interesting for companies that have devices in the field and want to push an upgrade to the next higher version (instead of just an update within a version). Is it just a zypper dist-upgrade with new repositories? We have some additional instructions (and cautions) here: http://wiki.meego.com/Upgrading_MeeGo_Versions Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] New idea about Meego SDK with Xephyr
On Dec 6, 2010, at 9:14 PM, tang.xin...@byd.com tang.xin...@byd.com wrote: Because performance of MeeGo OS in QEMU is slow,Animation and screen changes is slow , need VT . and There are not many devices runs MeeGo OS. so, for easy, i hava a new idea is mixed QT-Creator and Xephyr. Qt-Creator and Xephyr both are independence running on linux host,Xehpyr is seen as what QEMU,Detailed steps,see the following: Quick reminder that we discourage cross posting in the MeeGo mailing lists. This topic clearly falls in the meego-sdk mailing list, and there is no reason to also copy meego-dev. For more about our mailing list guidelines, read: http://wiki.meego.com/Mailing_list_guidelines For more details about which mailing lists should be used for which topics, please read: http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Audio problem when connecting to internet in IVI
On Dec 3, 2010, at 7:36 PM, Manoj Cr wrote: Hi , Am working on Meego IVI on Intel Atom. We have been developing an application which has an audio playback using ALSA.I works well initaillay but the moment i connect my board to internet , audio gets automatically disabled.Has anybody faced this issue ??Is it because some update happens to alsa drivers when i connect to internet and it gets corrupted. Please help. Quick reminder that these types of questions should be posted in the MeeGo-IVI mailing list, instead of MeeGo-Dev: http://lists.meego.com/listinfo/meego-ivi More info on all of our mailing lists, including which ones are appropriate for different types of questions can be found here: http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [MeeGo-community] Nudging the Community Device Program
On Dec 2, 2010, at 5:11 PM, Randall Arnold wrote: - Original message - From: a.gra...@gmail.com a.gra...@gmail.com To: Randall Arnold tex...@ovi.com cc: MeeGo community meego-commun...@meego.com, MeeGo Dev List meego-dev@meego.com Subject: Re: [MeeGo-community] Nudging the Community Device Program Date: Fri, 3 Dec 2010 02:03:24 +0100 Hi, On 3 December 2010 00:40, Randall Arnold tex...@ovi.com wrote: Now that we have a nice offer from TI to get Pandaboards into the hands of developers [1] it's time as Quim suggested to get serious about the Community Device Program [2]. I will repost some of the wiki content here followed by my thoughts and questions: maybe I' missing something... if TI is going to provide these Pandaboards, why are you talking about budget from Nokia/Intel/LinuxFoundation? I think you did miss something, Andrea-- that's exactly MY question for the wiki page. ;) I can try to rephrase if it's really that unclear… The vision for this program is to put together a framework that makes it very easy for anyone to contribute devices and have them go to the most qualified community members in exchange for some commitment to do something cool with the device. The idea is that we put together one program administered by the Linux Foundation that many companies can contribute devices to. Intel and Nokia will, of course, want to put some budget together to contribute our devices into the program :) I'm guessing the Linux Foundation won't need to contribute any budget, but they might need to administer some of it. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] meego security
On Nov 9, 2010, at 11:57 PM, sam sam wrote: Hi, Is there any information on the kind of security features expected in MeeGo 1.2. Just a quick reminder that we have a meego-security-discussions mailing list for these types of questions. Security questions should be posted to that list, instead of meego-dev. http://lists.meego.com/listinfo/meego-security-discussion Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Coding guidelines doc
On Nov 10, 2010, at 2:13 AM, Thilaga wrote: Hi All, Is there any Meego Coding guidelines document. You might want to try a more specific question. Are you talking about contributing code to the MeeGo distribution? http://meego.com/about/contribution-guidelines Or are you looking for application developer documentation? http://meego.com/developers If your question is about developing applications for MeeGo, you should post a more specific question in our application developer mailing list with details about the type of documentation you need: http://lists.meego.com/listinfo/meego-sdk Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Allowing non-subscribers to post on the mailing lists
On Oct 22, 2010, at 10:17 AM, Dave Neary wrote: Moderation also has some problems because the moderator is taking the responsibilty for deciding what the user meant to do. The way we have it set up now, we're putting the decision in the users' hands, which seems fair to me. It's impossible to protect people from themselves. Some people will sign up to the list, and 6 months later will accidentally send something confidential to the list - but they're members so it goes straight through. Oops! I agree that you can't protect users from themselves, but you can put the decision solely in their hands. If they subscribe to a list and then forget what it is, this becomes their mistake. If a moderator lets it through or if we let people who aren't subscribed post to the list, it takes the decision out of the user's hands. I prefer to let each user make their own decision and then be accountable for it. By requiring subscription and email confirmation, you can be certain that at some point each user made a conscious decision to join the list. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Search Meego mailing list
On Oct 19, 2010, at 6:36 AM, Bob Lin wrote: Dear all Sorry, I don't know how/where to search whold meego mailing list by keyword. Could anyone told me where/how to do the search? Just an quick reminder that the Community Communications document (linked from every mailing list description) also has tips for searching our mailing lists and other community tools. http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo on 'Generic' or otherwise-branded phone hardware
On Oct 10, 2010, at 3:35 PM, Shuang han wrote: Hi everyone! We are students in Royal Institute of Technology in Sweden. And we are researching on the market potential of the wearable technology products in the coming ten years, especially in European area. If possible, please help us do this investigation. Thank you very much. --Shuang Han Arash Ameli This is not an appropriate use of this mailing list. For guidelines about which mailing lists / forums are appropriate for a given topic, please refer to http://wiki.meego.com/Community_communication Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Patch reviews on this mailinglist? [was: Backend Error handling]
On Sep 30, 2010, at 7:18 AM, Andre Klapper wrote: Am Donnerstag, den 30.09.2010, 17:10 +0300 schrieb ext-arun.1.ravindran: Currently, if backend fails to send message, there is no note of this to user. This patch added the handling of the error. General question: Can somebody clarify if this list is meant to also be a patch posting/review list? I would have expected a bug report in bugs.meego.com and a patch attached there, but maybe I am wrong? We let the submitter choose whether to include it as part of a bug report or to send it to the list. The process is documented here: http://meego.com/about/contribution-guidelines Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Recovering MeeGo Grub bootloader after reinstalling Windows on seperate partition
On Sep 29, 2010, at 2:29 AM, Radi, Rami wrote: Hi all, I have a netbook, and installed Windows 7 on a partition, and after that installed MeeGo on another partition, and had dualboot functioning properly. Then while I was testing several things on Windows 7, I messed up several things, and system restore isn’t helping, so I had to reinstall it on the same partition (without touching MeeGo’s partition), but of course I lost the MeeGo grub bootloader. Does anyone know how to recover my MeeGo bootloader, so that I don’t have to reinstall MeeGo and my custom apps, etc? Questions about using MeeGo and installation should be posted to the MeeGo forums. I know this question has been answered previously in the forum: http://forum.meego.com More details about using the MeeGo mailing lists, forums and other communication can be found here: http://wiki.meego.com/Community_communication Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Refocusing mailing lists, was: Re: A note SIGSEGV pop up when using QToolBar
On Sep 27, 2010, at 10:42 AM, Andrew Flegg wrote: On Mon, 27 Sep 2010, 18:08:17 BST, Foster, Dawn M dawn.m.fos...@intel.com wrote: We're also in the process of moving a bunch of infrastructure to OSU, so if we do decide to rename some lists, I would rather wait to do it until after we finish moving everything. Is there really an optimisation in renaming a list when moving the infrastructure? As an occasional mailman admin, I would've thought that the too were independent and - indeed - that trying to reduce the number of changes between the two systems would make a smoother migration. This is more of a resource issue - the people with access to the servers to make this change are all busy with the migration. And the issue is that we can't give additional people access to the servers until we get things moved to OSU, so yes, this is a blocker for many things right now. I'll let someone more intimately involved in the migration comment on the timeline for getting everything moved. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [announce] MeeGo Security Discussion List
On Sep 24, 2010, at 2:38 PM, Yves-Alexis Perez wrote: On mer., 2010-09-22 at 15:34 -0700, Ryan Ware wrote: All, Like Arjan did for the kernel mail list, I would like to announce the creation/existence of the MeeGo Security Discussion list and would like to invite any and all who are interested in various parts of MeeGo security (generic OS configuration, security framework, infrastructure security, etc.) The mailman interface for this list is at http://lists.meego.com/listinfo/meego-security-discussion If you have any questions/concerns, please feel free to voice them here or email me directly. As always, if you feel you have found a security issue with meego, please report it to secur...@meego.com. Is there a reason why those list aren't (yet?) advertised in meego.com account setup? We need to reorganize the meego.com list page to accommodate the new lists now that we have close to 20 lists with a few more on the way. The page needs a little work to make it easy for people to find and get subscribed to the right lists. For now, people can subscribe using the mailman interface and we should have them added to the meego.com accounts page in the next 2 weeks after we redesign the page. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo Porting Guide available for reading
On Sep 13, 2010, at 9:30 AM, Foster, Dawn M wrote: On Sep 13, 2010, at 3:18 AM, jari.paloja...@nokia.com jari.paloja...@nokia.com wrote: In my opinion, a meego-porting mailing list would be a good idea. Dawn (and others) – any thoughts about this? We're getting a lot of porting questions, so I think it's probably a good time to create a specific list for it. I'll try to have it available at the end of this week or early next week. Jari - would you be the primary contact for this new list? The new meego-porting list has been created. More details: http://lists.meego.com/listinfo/meego-porting Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Upstart in MeeGo?
On Sep 18, 2010, at 2:51 AM, Andrew Flegg wrote: On Fri, Sep 17, 2010 at 17:37, Quim Gil quim@nokia.com wrote: Now there is a meego-architecture list devoted to discuss topics like future technology selections. http://lists.meego.com/listinfo/meego-architecture Please continue this thread there. Thank you! There was discussion on meego-community about them *going* to be set up, but I seem to have missed the announcement about what new mailing lists *have* been established (both on the web and cross-posted to all the current lists, I'd've said). Sorry, Quim's post was incorrect. Yes, that mailing list has been created but I have not yet finished configuring it, and none of the architects are subscribed yet. Please continue architecture discussions here until you see an announcement from me that the list is ready to use. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Creating a Python project for MeeGo (was: pyside in repo.meego.com?)
On Sep 20, 2010, at 2:03 PM, Sivan Greenberg wrote: On Mon, Sep 20, 2010 at 5:59 PM, Matti Airas matti.p.ai...@nokia.com wrote: On 20.09.2010 17:41, ext Per Åstrand wrote: Hi! I've been checking the repositories for python support. AFAICT the compliance doc at http://www.pyside.org/2010/09/meegotouch-bindings-alpha-available/ requires an application to only use packages in the officail repos to be meego compliant IMHO it makes sense to also include python bindings for QT (pyside) to be able to write meego compliant applications in python. pyside project seems to be tracking QT and meego well (http://www.pyside.org/2010/09/meegotouch-bindings-alpha-available/). Also kind of strange that bindings for gtk is in the repo, but not for QT... Hi Per, We (as in the PySide team) are definitely planning on providing the PySide packages on MeeGo in the near future. However, since we're just ramping up our MeeGo activities (still waiting for the OBS accounts to be created, etc), I have to say I've been rather ignorant about the details of the contribution process. In particular, I'm interested about the proper channels for contributing to the existing Python distribution. What is the formal project the current Python packages live in? Should we contribute there or should we make a proposal to the TSG to create a proper MeeGo Python project which could act as an umbrella for all Python-related activities in MeeGo? Matti, maybe we can ask Dawn to add this item for tomorrow's TSG meeting so it can be discussed and agreed upon already? I don't think this is a TSG decision item. Only project-wide decisions or things that need to be escalated should go all the way to the TSG for a decision. I'm guessing that this is something that the architecture team along with the SDK / application development team can address. Links with contact info: http://wiki.meego.com/SDK http://meego.com/about/governance/distribution-development Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] A 'red thread' through MeeGo Conference proposals
On Sep 4, 2010, at 2:09 PM, Carsten Munk wrote: 2010/9/4 Randall Arnold tex...@ovi.com: Sorry, I forgot to address this: actually the system *does* allow editing. In fact I updated mine already to add another panelist recently (before closure), and I see that the edit function still works now. Maybe that should be temporarily disabled during consideration, tand then re-enabled when you request consolidations? If we do request consolidations we'll see how we go about it. But, eep. Dawn, any reason for the editing still being active? Best regards, Carsten Munk We decided to let people continue to edit their proposals after the deadline with the idea that they could make minor tweaks after submitting - correct typos, add additional information, etc. This gives the selection committee some leeway to request that people update proposals if you have questions or something isn't quite clear in the proposal. We were pretty clear about the deadline, and any changes made after the deadline may or may not be considered, since the program committee has already started the evaluation / selection process. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [PATCH 1/2] fixed seg fault when ofono isn't running
On Aug 26, 2010, at 4:44 PM, Shane Bryan wrote: On Thu, 26 Aug 2010 16:20:51 -0700 Foster, Dawn M dawn.m.fos...@intel.com wrote: On Aug 26, 2010, at 4:17 PM, Shane Bryan wrote: On Thu, 26 Aug 2010 15:56:38 -0700 James jketr...@linux.intel.com wrote: On 08/26/2010 03:53 PM, James wrote: On 08/26/2010 03:42 PM, Shane Bryan wrote: On Thu, 26 Aug 2010 22:56:24 +0200 Dave Nearydne...@maemo.org wrote: ... I just checked, and I did reply to all. Kevron hadn't included you in the CC list for the mail sent to the mailing list. Not sure what happened then, because the original headers[1] from Kevron's initial post had me CC'd in them, but your reply did not[2], so I assumed it was intentional. My apologies for making that assumption. I noticed something similar the other day when I had to keep manually adding people to the CC: list in an email thread. The meego-dev list configuration may be stripping CC: recipients that are already subscribed to the mailing list. Confirmed. The above email was: To: Shane From: James Cc: Dave, meego-dev But coming from the mailing list, I now have: To: Shane From: James Cc: meego-dev Cool, thanks for confirming this James and Dave. I'll initiate a new thread on this to see what we can do to fix this. Actually, can you file it as a bug? Easier to track. Seems there already is one[1] BMC #5567, filed last Wednesday Shane... [1]http://bugs.meego.com/show_bug.cgi?id=5567 It looks like this is a user configurable option in mailman: http://www.list.org/mailman-member/node21.html that people need to tweak. I have mine set to not receive duplicates, and this looks like the right way to handle the issue, since some users want this and others probably don't. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [PATCH 5/5] fixed seg faulting when no ofono is running
On Aug 25, 2010, at 4:37 PM, Michael Leibowitz wrote: what does Signed-off-by mean ? You're signing WHAT ? http://kerneltrap.org/files/Jeremy/DCO.txt ;) We've adopted a formal process for this - exactly like the kernel process (approved in the TSG on May 26, 2010): http://meego.com/about/contribution-guidelines/signed-process Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Guidelines for contributing code to MeeGo
On Aug 23, 2010, at 4:55 PM, Foster, Dawn M wrote: I tried to incorporate a couple of changes that seemed to have some agreement (CC'ing maintainers for example), so here is the now official policy for contributing code to MeeGo. We'll still continue to make changes as we see what does / does not work. http://meego.com/about/contribution-guidelines Regards, Dawn I've also been looking into other ways to make this process better over time, and a couple of people (Alan Cox John Hawley) suggested that we look into implementing Patchwork: http://ozlabs.org/~jk/projects/patchwork/ The goal is to make it easier to find and manage patches to avoid them getting lost in the shuffle. It's used by kernel.org, for example: https://patchwork.kernel.org/ Any thoughts? Good idea? Bad Idea? Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] security?
On Aug 20, 2010, at 11:53 PM, § सोनाली § wrote: As I am studying MeeGo OS as my seminar Topic I have some basic question. 1. As everyone is saying meego is completely open source and fully Linux the how it provides security? And how it is safe from hackers and intruders? 2. Which are the processor MeeGo supports to? 3. Is there is meaning to word Meego or it is abbreviation of something? ATT1..txt This question isn't appropriate for this mailing list. For more details about why it isn't appropriate, see http://wiki.meego.com/Refocusing_meego-dev Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] MeeGo Conference Session Proposal Deadline Extended to August 27 at 11:59PM Pacific Time
We've had a great response to the MeeGo Call for Proposals with over 150 sessions submitted as of a few minutes ago, and I expect we'll see more today from the procrastinators who waited until the last day to submit. However, we've noticed a few gaps in content, and there have been a few questions about the BOF process, so we are extending the deadline by a few days to give people a little more time to address these gaps. BOFs: If you would like to lead a Birds of a Feather session (BOF) at the MeeGo conference, please submit it now as part of the call for proposals process. There will not be a separate BOF submission process. Preface the session title line with 'BOF:' to let us know you are proposing a BOF, instead of a regular session. You can see several examples of BOFs that have already been submitted. In-Vehicle Infotainment (IVI): While we have quite a few sessions on handsets and other vertical products, we have few sessions devoted to IVI technologies. This is a hot topic, and if you are working on IVI, I recommend that you submit a talk. Middleware: We aren't seeing quite as many middleware session proposals as we would like, so please think about additional middleware talks. You can get a full list of middleware components from the MeeGo Architecture diagram: http://meego.com/developers/meego-architecture Project Leadership: Quite a few of the people with key roles in the MeeGo governance have not yet submitted sessions. As project leaders / maintainers of key components of the MeeGo distribution, we would expect to see more session submissions from the people leading the project. A full session or even a Meet the Team BOF would be a good way for people to meet those of you in key positions. Visit the Call for Session Proposals page to submit your proposal: http://conference2010.meego.com/program/call-session-proposals Please take a minute to browse the session submissions (http://conference2010.meego.com/program), and if you see any other gaps, please respond to this thread to let us know. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Guidelines for contributing code to MeeGo
On Aug 20, 2010, at 9:30 AM, Foster, Dawn M wrote: Someone recently pointed out the we have a mostly empty contribution guidelines page on the website: http://meego.com/about/contribution-guidelines I've also had several people recently tell me that they were confused about the process for contributing code to MeeGo and another person who has submitted several patches into bugzilla, but no one has responded to them. So, I thought it was time to put together better guidelines for how to contribute code to MeeGo, and I've added an escalation process that I will monitor for when patches slip through the cracks to make sure that someone responds when a community member takes the time to write a patch. The draft guidelines are here on this wiki page: http://wiki.meego.com/Contributing_code_to_MeeGo Please feel free to discuss any issues or ask questions here. If you have minor changes, you can make those changes directly to the wiki page. Since this is really just a written summary of what we seem to be doing now and not really a policy change, if I don't hear any big objections, I'll post this as an official policy on the MeeGo website on Monday. I tried to incorporate a couple of changes that seemed to have some agreement (CC'ing maintainers for example), so here is the now official policy for contributing code to MeeGo. We'll still continue to make changes as we see what does / does not work. http://meego.com/about/contribution-guidelines Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Refocusing meego-dev
On Aug 20, 2010, at 12:16 AM, Patrick Ohly wrote: On Thu, 2010-08-19 at 21:46 +0100, Andrew Flegg wrote: On Thu, Aug 19, 2010 at 21:36, Attila Csipa me...@csipa.in.rs wrote: I'm thinking that maybe the naming of the lists has something to do with it. I did a quick poll among colleagues and (while not obviously the most scientific method) discovered that without additional information, they too would have posted application issues in meego-dev and platform/sdk related issues in meego-sdk. Indeed, I've asked a developer here and they answered similarly. Agreed. meego-sys-dev and meego-app-dev if long names are a problem? Because, conceivably we may want meego-sdk-dev (or similar) to discuss the development of the SDK, rather than the use of it (SDK development, across multiple platforms, being a notably hoary subject). +1 from me on meego-sys-dev, meego-app-dev, meego-sdk-dev. But these are just name changes, the definition of the lists wouldn't change. I actually like the idea of renaming meego-dev to meego-sys-dev and meego-sdk to meego-app-dev (we can probably do sdk dev conversations along with app dev conversations). However, I've never tried to rename a mailing list. We'd probably need to set up some forwards, and I'm curious if there are any other technical gotchas in renaming a mailing list? So let's be more specific and use the Buteo thread as example. Is that something for meego-dev (regardless whether it gets renamed to meego-sys-dev)? The part about choosing MeeGo is clearly off-topic. But Buteo is part of the MeeGo distribution, the code that goes into the MeeGo distribution download as the MeeGo open source project. Therefore discussing its design and implementation here is on-topic. But there's a slippery slope between Buteo design (on-topic) and feature proposals (off-topic, meego-community/talk?). How to use Buteo in a GUI is also a grey area. We are working on a GUI for it which will ship with the MeeGo distribution, so my questions about how to use service profiles in such a GUI are on-topic. A developer who wants to use Buteo in an application however would have to ask the same questions on meego-sdk/meego-app-dev. I personally find that separation unfortunate because a) it is confusing and b) demotivating for non-core developers who (after all) might one day contribute patches to the core software. But I don't have a better proposal which satisfies the goals of keeping traffic low enough on meego-dev for it to be useful and avoids fragmentation of the core development. Dawn, does this interpretation match your understanding of the lists? This sounds about right, and as you pointed out, there are certainly a lot of grey areas where certain topics, like Buteo, overlap. In general, architectural decisions are probably best suited to meego-dev and implementation within an application is probably meego-sdk (or meego-app-dev). Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [meego-packaging] [meego-commits] MeeGo-commits ... reply-to to MeeGo dev ?
On Aug 19, 2010, at 1:30 AM, Anas Nashif wrote: Yeah, that was the original intent, but we are evolving, we probably need to change the description now. Anas On 2010-08-18, at 3:12 PM, Ville M. Vainio wrote: On Wed, Aug 18, 2010 at 9:50 AM, Alexander Kanevskiy k...@kad.name wrote: agree, let's use -packaging, as -dev too much traffic to find out important thigns. But note the description of -packaging: http://lists.meego.com/listinfo/meego-packaging This list is dedicated to communication about packaging for MeeGo and build system related information and announcements. It is not a discussion list, so please take discussions to the meego-dev or meego-community mailing lists as appropriate. Perhaps that description should be updated if the role is different from what was initially planned? -- I've changed the description for the meego-packaging mailing list to: Short description: Communication about packaging and the build system (discussion list) Long description: This list is dedicated to communication about packaging for MeeGo and build system related information, discussion and announcements. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [meego-packaging] [meego-commits] MeeGo-commits ... reply-to to MeeGo dev ?
On Aug 19, 2010, at 6:47 AM, David Woodhouse wrote: On Thu, 2010-08-19 at 06:30 -0700, Foster, Dawn M wrote: I've changed the description for the meego-packaging mailing list... Thanks. I note you haven't yet dropped the abusive 'Reply-To:' header from the lists (other than -commits as discussed)… Good catch. I had fixed it for meego-dev, meego-community and other lists, but it looks like I missed meego-packaging in my first pass. meego-packaging is now set with reply-to poster, instead of reply-to list. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Refocusing meego-dev
The meego-dev mailing list is intended for people who are doing development on the meego distribution itself. However, the number of off-topic conversations on meego-dev in recent months is making it difficult for people to make progress on the project, and people have been requesting new lists primarily to avoid having to use meego-dev for their work. Rather than create a bunch of random lists, I would like to try to make meego-dev more useful for people, but this is where I need your help. Rather than responding to off-topic discussions here, I need your help in nicely redirecting people to the appropriate mailing list or forum for their discussion. Answering off-topic questions only increases the noise level and makes it more difficult for people to follow the right conversations. Nicely pointing them to the right place to get an answer helps make sure that people get the right answer and helps put conversations into the right places. Here's how the mailing lists break down right now to help you point people to the right place. meego-dev mailing list: Development on the MeeGo distribution (patches, etc.) - this is the code that goes into the MeeGo distribution download as the MeeGo open source project (core, netbook, handset, ivi, etc.) meego-sdk mailing list: SDK, APIs and other application development - All application developer questions should be posted in meego-sdk. If you are doing any development that isn't a patch or commit into the MeeGo distribution, your developer questions probably belong in meego-sdk. meego-community mailing list: This should be the catch all mailing list for things that don't fit cleanly into the other lists. Questions about community, general operations, openness, events and other general interest questions should be posted to meego-community. meego-il10n mailing list: Any localization or translation discussions. meego-packaging mailing list: OSB, RPM and other packaging discussions. meego-touch-dev mailing list: Discussions about the MeeGo Touch Framework. bugzilla: If someone posts a question that is clearly about a bug, point them to bugs.meego.com to file the bug and continue any discussion about that bug in bugzilla where we can track it in one place. forum.meego.com: All user questions and user level discussions should be posted in the forums. Questions involving user visible components, issues with a particular platform, installing apps / codecs / drivers and other general questions about using MeeGo. In general, if you have a MeeGo question that doesn't involve writing code and can be seen in the interface, the best place for these questions is in the forum. I know this is a little complicated, but I would rather solve the current issues with meego-dev than create new issues by adding a bunch of new developer lists that we probably don't really need. This isn't to say that we won't create new lists (we will), but there needs to a compelling reason for new development lists that isn't a variant of I need a new list because I don't like meego-dev. Does this sound like a reasonable approach to people? Regards, Dawn Reference Links: Mailing lists: http://meego.com/community/mailing-lists Forums: http://forum.meego.com/ Bugs: http://bugs.meego.com/ ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] TSG Meeting on August 18 at 19:00 UTC
On Aug 17, 2010, at 12:49 PM, Foster, Dawn M wrote: I wanted to remind everyone that we have Technical Steering Group (TSG) meetings every other Wednesday at 19:00 UTC, and the next meeting is on August 18. The meetings are held in IRC and anyone is welcome to attend. You can find more details about the logistics and the current agenda by visiting http://wiki.meego.com/Technical_Steering_Group_meetings Agenda for August 18: * MeeGo Compliance Program update - Mark Skarpness * SuSE MeeGo trademark exception request - Ibrahim Haddad * IVI release update - Margie Foster * Project nominations * All other business (Open Items and General Questions) Minutes from this meeting (full log linked from the minutes): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-18-18.58.html Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] TSG Meeting on August 18 at 19:00 UTC
I wanted to remind everyone that we have Technical Steering Group (TSG) meetings every other Wednesday at 19:00 UTC, and the next meeting is on August 18. The meetings are held in IRC and anyone is welcome to attend. You can find more details about the logistics and the current agenda by visiting http://wiki.meego.com/Technical_Steering_Group_meetings Agenda for August 18: * MeeGo Compliance Program update - Mark Skarpness * SuSE MeeGo trademark exception request - Ibrahim Haddad * IVI release update - Margie Foster * Project nominations * All other business (Open Items and General Questions) Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Stop Reply-To munging
On Aug 11, 2010, at 10:53 AM, Foster, Dawn M wrote: On Aug 11, 2010, at 10:13 AM, David Woodhouse wrote: On Wed, 2010-08-11 at 15:34 +0300, Felipe Contreras wrote: Hi, Normally when a person replies to a mail sent by the mailing list, the original author is in the To field, the mailing list is in the Cc list, and the remainder of the Cc list is kept intact. However, this mailing list munges the Reply-To header, which accustoms people (wrongly) to hit reply to sender instead of reply to all. This brings many disadvantages like: 1) Personal level indicators don't work 2) Searches by recipient don't work (to:me) 3) The Cc list is not kept properly (which hurts cross-posting) This is evil and broken and should be fixed, I agree. The lists were originally configured with reply-to author as the default, but I was asked to change the mailing lists to reply-to list by several key people in the project. I've had several requests like this one, and I agree with changing them back to reply-to author, instead of reply-to list. I'll make this change (reply-to author) in about 24 hours unless someone can convince me otherwise. The MeeGo mailing lists, including this one, are now set to reply to poster, instead of reply to list. You may need to remember to reply to the list, instead of the poster, but it should cut down on accidental postings and maintain appropriate Cc lists, etc. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Only one week left to submit MeeGo Conference session proposals
I just wanted to post a quick reminder that you only have 1 week left to submit a session proposal for the MeeGo conference on November 15 - 17 in Dublin. *Everyone* who wants to speak (including Intel, Nokia, LinuxFoundation, others, etc.) has to submit a proposal before August 23rd. You can submit a proposal, register to attend or get more details here: http://conference2010.meego.com/ Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] MeeGo Conference 2010 Call for Session Proposals
Do you want to speak at the MeeGo Conference in Dublin, Ireland on November 15 - 17? The call for session proposals has started, and anyone who wants to speak at the conference must submit a proposal. Proposals from community members, Intel, Nokia, the Linux Foundation and others will all be given equal consideration. Expected topics include: * Hardware support * Platform development * Application development * MeeGo project, process and progress * and any other MeeGo related topics The call for sessions closes August 23rd, and you will receive an email on whether or not your session is approved by September 24, 2010. Registration for the event should be available soon, so don't forget to check the site again later to register for the event. More details: http://conference2010.meego.com/ Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo for IVI v1.0.1 Released Today
On Aug 3, 2010, at 3:16 PM, quim@nokia.com wrote: Hi, Robin wrote: Question: where is the IVI UX being developed? http://meego.gitorious.org/meego-ivi-ux looks very ..spartan.. :) Please file bugs about any issues you find related to MeeGo open development and project transparency, and make them blockers of MeeGo openness meta-bug http://bugs.meego.com/show_bug.cgi?id=4898 Actually, I think this is less of an openness issue and more of a not being able to find it issue. The ivi code isn't in the MeeGo gitorious project. It's located here for historical reasons, I think: http://gitorious.org/ivi Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo for IVI v1.0.1 Released Today
On Aug 3, 2010, at 3:44 PM, Robin Burchell wrote: Excerpts from Foster, Dawn M's message of Tue Aug 03 23:33:15 +0100 2010: Actually, I think this is less of an openness issue and more of a not being able to find it issue. The ivi code isn't in the MeeGo gitorious project. It's located here for historical reasons, I think: http://gitorious.org/ivi Looks right, thanks. Should I file a bug requesting a move? I filed the bug, since I wanted to make sure that the right people were on the cc list to give them time to object before we move anything: http://bugs.meego.com/show_bug.cgi?id=4899 Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [Connman] [N900]: Very flaky connman behaviour regarding wifi, debug log linked
On Jul 14, 2010, at 2:16 AM, Changming Sun wrote: Sorry,where can I found some document for connman? It's rare. You can get more information, source code, recent release, etc. here: http://connman.net/ Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Simulator events
On Jul 13, 2010, at 9:42 PM, Vincent Yau wrote: Dear All: Is there a way to simulate certain kinds of user events inside Meego Simulator that comes with the SDK? One example of events I want to simulate is the touch events on a touch-screen. Just a quick reminder that questions about the SDK or application development should be posted to the meego-sdk mailing list, instead of meego-dev. http://lists.meego.com/listinfo/meego-sdk Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Suggestions to Meego site Administrators / Developers
On Jul 14, 2010, at 1:06 PM, Auke Kok wrote: 2) Please update the page for downloading Meego with Chrome browser ( http://goo.gl/9uAp ), it needs a MD5 sum: field like the page without Chrome browser( http://goo.gl/zNFg ) 3) Please add links to the md5sum at http://goo.gl/9IVZ , and write something there to make it easier for everybody to verify the integrity of the .img file. The location of that .md5sum file is IMO *obscure*. I searched for it more than 10 minutes after finally discovered the magic place http://goo.gl/F0GO (I later discovered it on the Meego for Netbooks page, i.e. the one without Chrome) this should be fixed I think, we can certainly add inobtrusive md5sum links in the release notes. We should definitely have the checksums in a place where normal human beings can find them without excessive digging. I've filed a bug for this request: http://bugs.meego.com/show_bug.cgi?id=3871 Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] QA guys: Wiki clutter?
On Jul 13, 2010, at 9:13 AM, Dave Neary wrote: I would suggest creating a Testing team page which could be used to collect report templates, document the testing team and its processes, and also collect all the test reports. Something like Testing team Testing team/Test report template ... We should probably use Quality Assurance or QA instead of testing team to keep things consistent with the naming of teams on the governance page: http://meego.com/about/governance/quality-assurance etc In general, if the testing team are going to be generating weekly test reports, then unless there is historical interest in keeping old test reports around, I would suggest that they be archived somewhere, and that only the latest test reports (and, perhaps, the last test results from a release to compare for regressions) be kept around. This is a very good suggestion. Keep in mind that since the wiki keeps a history of previous edits, you might be able to keep your reports grouped on a single page. Here's an example: Title: QA/Core testing reports Subheadings for each week's report: Core testing report 20100709 You could keep the most recent 5 reports on that page, and just delete the older ones from the page. The deleted content would still exist in the history for viewing. The you would have fewer pages, and it would be easier to find the information. Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] meego-dev or meego-sdk?
On Jul 9, 2010, at 2:43 AM, Jeremiah Foster wrote: On Jul 9, 2010, at 00:42, Foster, Dawn M wrote: We've been seeing quite a few application developer emails on the MeeGo-Dev mailing list that would more appropriately posted on MeeGo-sdk. As a quick reminder, here is how we're using these 2 mailing lists. MeeGo-Dev: The MeeGo-Dev list is mainly for development of the core MeeGo platform and development of the related UXs. MeeGo-SDK: Application development, SDK, API, Xephyr / chroot environments, virtualization and related discussions should posted on the MeeGo-sdk mailing list (or application developer forum if you prefer forums http://forum.meego.com/forumdisplay.php?f=3) Is the omission of the MeeGo Packaging list conscious? Right now, we have 8 mailing lists. You can find the list here: http://meego.com/community/mailing-lists I only highlighted these 2 because there seems to be a bit of confusion about what to post on these lists. We've had a significant number of SDK and application developer questions posted to meego-dev over the past month, so I wanted to remind people that we should be having those application development discussions in the SDK list. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] meego-dev or meego-sdk?
We've been seeing quite a few application developer emails on the MeeGo-Dev mailing list that would more appropriately posted on MeeGo-sdk. As a quick reminder, here is how we're using these 2 mailing lists. MeeGo-Dev: The MeeGo-Dev list is mainly for development of the core MeeGo platform and development of the related UXs. MeeGo-SDK: Application development, SDK, API, Xephyr / chroot environments, virtualization and related discussions should posted on the MeeGo-sdk mailing list (or application developer forum if you prefer forums http://forum.meego.com/forumdisplay.php?f=3) Regards, Dawn PS: To head off the inevitable question ... Yes, I remember that we still need to provide mail / forum integration. We're working on moving the servers to OSU OSL now, which will free up the server resources needed to implement the mail / forum integration. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] MeeGo 1.0 Update for Netbooks
This announcement is being cross-posted to a couple of the major mailing lists. In the future we will avoid cross-posting, so please subscribe to meego-annou...@meego.com if you want to receive these types of updates. You can subscribe by visiting your meego.com account page under mailing lists or subscribe directly at http://lists.meego.com/listinfo/meego-announce. Now, on with the announcement! Today, we are announcing our first update for the MeeGo v1.0 Core Software Platform Netbook User Experience project release, originally announced on May 25th. Many of you were quick to install our recent release of MeeGo v1.0 on your netbook. We appreciate all of the community help from those of you who tested our release and filed bugs. In fact, this update has over 100 bug fixes and is recommended for all users running MeeGo 1.0 for Netbooks. This update includes general operating system fixes that enhance the stability, compatibility, and security of your devices, as well as: * Updated to the 2.6.33.5 kernel * Faster usb storage finding time down from 5 seconds to 1 * Improved 3D performance * Many enhancements in the web browser * Resolution for several email client issues * Enhanced netbook window manager * Greatly enhanced visuals * Full support for GNOME proxy configuration in the media player * More control over DNS settings To get a full list of bug fixes you can visit the release update pages: http://meego.com/downloads/releases/updates/meego-v1.0.1-core-os-update http://meego.com/downloads/releases/updates/meego-v1.0.1-netbook-update If you run into any issues or have additional questions about the update, you can post them in our MeeGo Netbook Forum: http://forum.meego.com/forumdisplay.php?f=6 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] After handset day one - a plea for openness
On Jul 6, 2010, at 1:04 PM, Randall Arnold wrote: Here's where I'll beat my own dead horse: open project management. Not ad hoc, but supported by the right tool. There are some that plug into bugzilla and I provided recommendations to Quim and Dawn. Anyway, a web-based project manager usable by both internal and external contributors is a necessity IMO. Randy, I think you are the only person who has requested a formal project management tool. In my experience, installing a tool won't make people use it; however, if multiple people see this as a critical gap and are ready to use a project management tool, then we can look at implementing something based on the requirements coming from the project teams and project owners. Project management tools are tricky beasts, since every project manager seems to have a favorite tool along with deep hatred for other project management tools, so I've found it difficult in the past to standardize on a single tool. In general, I'd rather implement something based on requirements than perceived potential need that may or may not materialize. If it's something needed by only a couple of people, there are many project management tools outside of the MeeGo infrastructure that people can use. My question to the people leading projects within MeeGo - is this something you need to have implemented as part of the meego.comhttp://meego.com infrastructure? Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] After handset day one - a plea for openness
On Jul 6, 2010, at 4:48 PM, Randall Arnold wrote: - Original message - From: Dirk Hohndel dirk.hohn...@intel.com To: Nicola Mfb nicola@gmail.com, Development for the MeeGo Project (discussion list) meego-dev@meego.com Subject: Re: [MeeGo-dev] After handset day one - a plea for openness Date: Tue, 06 Jul 2010 16:32:54 -0700 * not official support of meego on some hardware is community driven? Again, the default builds that we provide are optimized for Atom - I don't think there's anything wrong with that. It's fairly straight forward to build for other platforms if you need that, but I think it is not a reasonable request that we shouldn't optimize for our platform. I guess this is one part I don't quite get, so forgive my ignorance. Given the eventual breadth of MeeGo, shouldn't the default be agnostic to vendor-specific optimizations? Then of course there would be an Atom-optimized build from Intel... ARM-specific from others... et al... Thanks for any clarification. This is a common approach for open source software. The person or people who write the first version of the software select a subset of hardware to get the project started. For example, the first version of the Linux kernel available to the public only ran on a 386 with AT drives, because that was what Linus Torvalds had at the time. If the open source project is successful (as Linux has been) more and more people will begin contributing ports of the software to additional hardware platforms. Linux now supports many different hardware configurations because people were willing to put in the time to add them. MeeGo will eventually support a broader set of hardware, but it will take time and contributions from the community to make it happen. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [MeeGo-community] Agenda for Technical Steering Group Meeting on 30 June 2010
On Jun 29, 2010, at 1:02 PM, Foster, Dawn M wrote: The next Technical Steering Group (TSG) meeting is scheduled for Wednesday, 30 June 2010, 19:00:00 UTC. Agenda: * MeeGo Handset (update): Pierre Blouin presenting * Release Process (for ratification) - Alexander Kanevskiy presenting * All other business (Open Items and General Questions) The agenda, logistics, past meeting minutes and more can be found here: http://wiki.meego.com/Technical_Steering_Group_meetings The minutes for the meeting can be found here: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-30-18.59.html Click on the link to the full logs for the details. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Agenda for Technical Steering Group Meeting on 30 June 2010
The next Technical Steering Group (TSG) meeting is scheduled for Wednesday, 30 June 2010, 19:00:00 UTC. Agenda: * MeeGo Handset (update): Pierre Blouin presenting * Release Process (for ratification) - Alexander Kanevskiy presenting * All other business (Open Items and General Questions) The agenda, logistics, past meeting minutes and more can be found here: http://wiki.meego.com/Technical_Steering_Group_meetings Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] New MeeGo Announcement Mailing Lists
I wanted to let everyone know that we've created 2 new mailing lists to be used for MeeGo announcements: * meego-announce will be used to announce major project releases[1] * meego-security will be used to broadcast official MeeGo security announcements[2] Both of these are low volume mailing lists, and posting to these lists is restricted to a few people who are responsible for official project communications. These lists are a good way to keep up with major announcements for people who aren't involved in the day to day development of MeeGo. To subscribe to a mailing list, you can log into your account on MeeGo.com. You can then manage your subscription to the mailing lists from the My Account link at the top of the page. Dawn [1] http://lists.meego.com/listinfo/meego-announce [2] http://lists.meego.com/listinfo/meego-security ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Annoying behavior with current way to answer a phone call on Maemo, hope for improvement for N900.
On Jun 17, 2010, at 8:54 AM, Sivan Greenberg wrote: Dear List, I hope this is a proper forum to bring this up - but I have been annoyed with the fact that once a phone call is arriving in N900 (currently with Maemo Fremantle) there is a rather large room for error when you need to take the device out of a pocket or a backpack's drawer. Usability / user facing issues should be posted in the MeeGo forums. http://forum.meego.com/ This list is for development of the meego platform. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Technical Steering Group Meeting 9 June 2010 at 19:00 UTC
I wanted to remind everyone that we have a Technical Steering Group Meeting (TSG) scheduled for tomorrow, 9 June 2010 at 19:00 UTC in #meego-meeting on IRC. For more details and meeting logistics, you can visit http://wiki.meego.com/Technical_Steering_Group_meetings Agenda: * MeeGo Project Structure / Roles Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Forum / mail integration (was MeeGo Summit - Structured brainstorming...)
On Jun 3, 2010, at 6:16 AM, quim@nokia.com quim@nokia.com wrote: Reggie said that Forum/Mail integration would require more server power and proposed to wait until the meego.com infra is hosted at OSU OSL. forum.meego.com is not in OSU OSL yet and this is the main reason why we are stuck in this forum/mail integration. PS: yes, you are busy. No, you are not the only one. Yes, it's a good idea to have some respect for tho work others are doing. A while back, we made the discussion to move the community office discussions to the forum. After living with that decision for a month or so, I'm starting to think that the discussions should be moved back to meego-community. The community discussions have just been too disconnected from the developers (who love their mailing lists). Right now, the developers form the base of the MeeGo community, and the reality is that the mailing lists are the best way to keep the developers connected to the broader community efforts (MeeGo conference, etc.) What I don't want to have is official community office discussions happening in both places, so I would like to pick one place for the community discussions. I propose moving those discussions back to meego-community. The forums have been a great way for end users to get engaged with the project and ask questions, and I think that we should keep the end user discussions in the forum. This would give us a more clean split: * Mailing lists: MeeGo project discussions, developer discussions, community office, etc. * Forums: End user questions, installation / troubleshooting, using MeeGo, etc. Thoughts, issues, questions, flame wars? Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Forums and User Help for MeeGo 1.0
On May 27, 2010, at 12:34 PM, Foster, Dawn M wrote: With the new release of MeeGo 1.0 that was announced yesterday, we have many new users. The good news is that people are excited and are using MeeGo; however, they have many questions and issues getting started. Here's how we are organized from a community perspective: Developer questions: Mailing lists User questions: Forums http://forum.meego.com If you have some extra time, we would appreciate any help you can offer by answering a few user questions in the forums. Also, if you see people asking user questions here on the developer mailing lists, please kindly encourage them to visit the forums. Keep in mind that some of these users may not be used to interacting on mailing lists and many don't have the tough skin that we have developed by working in open source communities over the years, so please be kind and helpful when pointing them to the forums :) I know, I know. I've had several people tell me that it's just too much work to wade through the forums to answer user questions. To make it easier on all of you, I'm trying to keep a list compiled of forum threads that require answers: http://wiki.meego.com/Netbook_Forum_Triage Feel free to answer a few questions and remove them from the list. Any help would be appreciated. Right now we have close to 50 unanswered threads related to running MeeGo on netbooks with more threads being added all the time. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] m4a/AAC playback
On Jun 1, 2010, at 6:08 AM, James Abernathy wrote: I'm evaluating Meego 1.0 on an Aspire One 532h in the lab and want to test the media capabilities of the O/S on the platform. Where can you get the normal non-DRM codecs for the Meego player to play mp3 and lossless AAC/m4a audio? This is probably a better question for the user forums, rather than the developer mailing list. Specifically, this forum thread has information on where to find additional codecs: http://forum.meego.com/showthread.php?t=238 Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego in two Acers
On May 27, 2010, at 10:30 PM, Martti J Lumme wrote: Hi If anyone interested, where Meego runs, here is one report. Installation was done with 2G-usbstick made on MacPro on the following two Acer notebooks. The installation with usb was easy, only relevant questions were asked. Both work with wlan, sound, ethernet. These devices have no bluetooth. Instructions http://meego.com/devices/netbook/installing-meego-your-netbook Be patient the following copy will last significantly long time. sudo dd if=/path/to/downloaded.img of=/dev/diskN bs=1024 1) Bottom Label: Acer Aspire One Model ZG5 Receipt: Acer Aspire One A110-A/8.9/512MB/8GB/Linpus Linux www.verkkokauppa.comhttp://www.verkkokauppa.com/ Sep 2008, 199.90€ 2) Botton Label: Acer eMachines 250-01G16i Model KAV60 Receipt: Acer eMachines 250 / 10.1 / N270 / 1 GB / 160 GB www.verkkokauppa.comhttp://www.verkkokauppa.com/ May 2010, 225.00€ Thanks for writing this report! We're also gathering a list of supported platforms here: http://wiki.meego.com/Devices I've added these two systems, and everyone should feel free to add systems they have tested. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Not getting web browser choices
On May 28, 2010, at 7:24 AM, Markus wrote: Am Freitag 28 Mai 2010, 16:02:01 schrieb Roger WANG: Did you see any program in the release loading QtWebKit, or you just post here before you actually get it running? Dude, seriously. I was just asking why no QtWebKit browser is used by default. If you don't want to answer that simple question or don't know the answer, then OK, but don't be a bitch who makes fun of people who ask very simple questions. OK, let's be nice here. Please avoid personal attacks and name calling. This is not appropriate behavior for this mailing list. Please stay focused on the attacking the problem, not the people. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Technical Steering Group Meeting 26 May 2010 at 19:00 UTC
On May 27, 2010, at 4:21 AM, Dave Neary wrote: Hi, Foster, Dawn M wrote: If you missed the meeting or want to review the decisions, you can get the minutes and full IRC log from the meeting here: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-26-19.02.html I let everyone know last week (at the abortive meeting) that I wouldn't be able to attend, but I did ask that the issue of licencing incompatibility with existing Nokia documentation be brought up - I wanted the TSG to be aware of the licencing incompatibility with Maemo documentation, and set wheels in motion to resolve the incompatibility. I actually don't think this needs to go to the TSG. The TSG has provided direction on the final license, and you should just work with Quim / Nokia to resolve any legacy licensing / relicensing issues required to re-use any relevant Maemo documentation. It's important to remember that the TSG provides overall project direction and is an escalation point for anything that can't be resolved at a lower level in the MeeGo project, but we need to try to resolve this ourselves and only take it to the TSG if we can't resolve it. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] How can I start developing application for Meego.
On May 27, 2010, at 7:17 AM, Arjan van de Ven wrote: On 5/27/2010 5:20, Abdul Mateen wrote: Hi, How can I start development, I am from strong Android background Developer, is there any SDK available for download, that includes the toolchains / tools to setup. and I can start developing Meego Applications. OR that is planned in June ? \ there's a bunch of things, various items are put on the website already, and there's a qtcreator package with the basic QT development environment… If you haven't found the information already, here are a couple of links to get you started: http://wiki.meego.com/Getting_started_with_the_MeeGo_SDK_for_Linux http://wiki.meego.com/Developer_Guide http://meego.com/developers Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Forums and User Help for MeeGo 1.0
With the new release of MeeGo 1.0 that was announced yesterday, we have many new users. The good news is that people are excited and are using MeeGo; however, they have many questions and issues getting started. Here's how we are organized from a community perspective: Developer questions: Mailing lists User questions: Forums http://forum.meego.com If you have some extra time, we would appreciate any help you can offer by answering a few user questions in the forums. Also, if you see people asking user questions here on the developer mailing lists, please kindly encourage them to visit the forums. Keep in mind that some of these users may not be used to interacting on mailing lists and many don't have the tough skin that we have developed by working in open source communities over the years, so please be kind and helpful when pointing them to the forums :) Right now, we have many questions in the forums, so we would appreciate any assistance helping people troubleshoot their problems and helping them file new bugs or update existing bugs with additional information. I should also point out that we have written extensive user help for the MeeGo 1.0 release, so for really novice how do I use feature x in MeeGo questions, you can also point people to specific help topics found at http://help.meego.com/ Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo v1.0 Core Software Platform Netbook User Experience project release
On May 26, 2010, at 10:04 AM, ivarela wrote: Watching the languages, I see that all languages with 99% or 100% has been included in the release. So I think (IMHO) that Asturian language must be included: http://translate.moblin.org/collections/c/meego/r/1x/ This is probably a better discussion for the meego-il10n mailing list. I think this list of languages was picked based on the status of the translation when we froze development over a week ago to give us time for QA on the languages. Additional languages will be added in the future, and that discussion is happening in meego-il10n. Hopefully someone on that list can provide a more detailed update on the process for adding new languages as updates to releases. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Technical Steering Group Meeting 26 May 2010 at 19:00 UTC
On May 25, 2010, at 2:46 PM, Foster, Dawn M wrote: I wanted to remind everyone that we have a Technical Steering Group Meeting scheduled for tomorrow, 26 May 2010 at 19:00 UTC in #meego-meeting on IRC. If you missed the meeting or want to review the decisions, you can get the minutes and full IRC log from the meeting here: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-26-19.02.html The next TSG will be on June 9 at 19:00 TSG. Details and logistics: http://wiki.meego.com/Technical_Steering_Group_meetings Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Technical Steering Group Meeting 26 May 2010 at 19:00 UTC
I wanted to remind everyone that we have a Technical Steering Group Meeting scheduled for tomorrow, 26 May 2010 at 19:00 UTC in #meego-meeting on IRC. For more details and meeting logistics, you can visit http://wiki.meego.com/Technical_Steering_Group_meetings Agenda * Document Licensing Proposal * Contribution Sign-Off Process Proposal * MeeGo 1.0 Discussion Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Changing Intel specific things in kernel-source
On May 11, 2010, at 6:02 AM, Ameya Palande wrote: Hi, Can we change following text and code snippet? 1. File: kernel-source/scripts/patch-tag-template # Here all the valid metadata tags for MeeGo patches are recorded. # Patches in the MeeGo kernel repository must have a Subject tag, and # there must be a intel email address in a From:, Signed-off-by: or # Acked-by: tag. 2. File: kernel-source/scripts/check-patch Function check_patch() contains code for checking patch is from intel domain. Ameya, Can you file this as a bug or add it as part of this similar bug: http://bugs.meego.com/show_bug.cgi?id=1459 Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] MeeGo IRC Meetings
With more and more IRC meetings being held in #meego-meeting, we need to have some way to schedule meetings to avoid conflicts with using the channel. Right now, I've put together a very simple process: if you want to use #meego-meeting, add your meeting to this wiki page: http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule Yes, I know this isn't the most elegant or long-term solution, but it should be enough to get us started. If some ambitious person would like to help implement a better scheduling tool for the IRC channel, please propose some ideas in the Community Matters Forum thread on this topic: http://forum.meego.com/showthread.php?p=1249 Thanks, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] TSG Meeting on May 5th at 19:00 UTC
On May 4, 2010, at 10:00 AM, Foster, Dawn M wrote: I wanted to remind everyone that we have weekly Technical Steering Group (TSG) meetings every Wednesday at 19:00 UTC, and the next meeting is on May 5th. The meetings are held in IRC and anyone is welcome to attend. You can find more details about the logistics and the current agenda by visiting http://wiki.meego.com/Technical_Steering_Group_meetings For anyone who missed the meeting, here are the minutes: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-05-05-18.58.html Our next TSG meeting will be May 12 at 19:00 UTC. The agenda will posted at http://wiki.meego.com/Technical_Steering_Group_meetings Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] TSG Meeting on May 5th at 19:00 UTC
I wanted to remind everyone that we have weekly Technical Steering Group (TSG) meetings every Wednesday at 19:00 UTC, and the next meeting is on May 5th. The meetings are held in IRC and anyone is welcome to attend. You can find more details about the logistics and the current agenda by visiting http://wiki.meego.com/Technical_Steering_Group_meetings Here is the May 5th Agenda: * Meeting Process * Introductions * MeeGo Project Structure and Working Groups * Upcoming Release * All other business (Open Items and General Questions) Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] presentation from MeeGo workgroup?
On Apr 16, 2010, at 6:46 AM, Dengyi Wang wrote: Hi If you present on the MeeGo workgroup from Linux Foundation Collaboration Summit yesterday, is it possible for you to upload your presentation/moive/demo/... to http://meego.com/community/events/presentations I just published a blog post summarizing the MeeGo activity at the Collaboration Summit. It has links to all of the presentation materials, the videos from Ari and Imad's keynote presentations along with other information from the Collaboration Summit. Keep in mind that only 3 of the presentations in the MeeGo Workgroup used slides - the rest were open discussions or QAs. http://meego.com/community/blogs/dawnfoster/2010/meego-presentations-linux-foundation-collaboration-summit Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Missing Messages Issues posting to this list
On Apr 19, 2010, at 11:56 AM, Foster, Dawn M wrote: We're having an issue with some people's messages never making it to this list, and I'm trying to track down the problem. In some cases (Randall) it seems to be intermittent - some messages from machines with certain configurations are getting through, but others are disappearing before they make it to the list. Since this only happens with certain people, my working theory is that we have an overly aggressive content filter of some kind, but I don't see anything that looks too aggressive. OK, I think we've corrected the issue. If anyone is still having problems, please let me know. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] how i can cancel my meego account? plz
On Apr 23, 2010, at 9:48 AM, Milos Mandaric wrote: Can somebody ban this person? This is pure spam. Done. I took care of this a couple of hours ago. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Missing Messages Issues posting to this list
We're having an issue with some people's messages never making it to this list, and I'm trying to track down the problem. In some cases (Randall) it seems to be intermittent - some messages from machines with certain configurations are getting through, but others are disappearing before they make it to the list. Since this only happens with certain people, my working theory is that we have an overly aggressive content filter of some kind, but I don't see anything that looks too aggressive. If you are having problems, please email me directly (off-list) with the following information: * email address that is subscribed * the text of any bounce-back messages * description of any pattern or other information that might help me diagnose the issue. Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] No TSG Meeting on April 14
Our regularly scheduled Technical Steering Committee[1] meeting this week conflicts with the Linux Foundation Collaboration Summit. With so many of us at the CollabSummit for the MeeGo track[2], we decided that we would cancel the April 14th TSG and hold the next one on April 21. Thanks, Dawn [1] TSG meeting info: http://wiki.meego.com/index.php?title=Technical_Steering_Group_meetings [2] Agenda for CollabSummit MeeGo track: http://events.linuxfoundation.org/lfcs2010/meego-workgroup ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
