[MeeGo-dev] Invitation to connect on LinkedIn
LinkedIn Bradley Smith requested to add you as a connection on LinkedIn: -- Gibran, I'd like to add you to my professional network on LinkedIn. - Bradley Accept invitation from Bradley Smith http://www.linkedin.com/e/-2agdob-gkc39m2w-43/qDd9BOisaO1VpiFh_kzD4R9s3f1P9UK/blk/I1137311543_3/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYPnPcQdj4NcPsPcj59bQhHoldErn9MbP4VejwTc30ScP8LrCBxbOYWrSlI/EML_comm_afe/ View invitation from Bradley Smith http://www.linkedin.com/e/-2agdob-gkc39m2w-43/qDd9BOisaO1VpiFh_kzD4R9s3f1P9UK/blk/I1137311543_3/3dvcPgRcj4PdPcNckALqnpPbOYWrSlI/svi/ -- DID YOU KNOW you can be the first to know when a trusted member of your network changes jobs? With Network Updates on your LinkedIn home page, you'll be notified as members of your network change their current position. Be the first to know and reach out! http://www.linkedin.com/ -- (c) 2011, LinkedIn Corporation___ 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 Bugs Access Denied
I don't want to be rude here, but I feel that I need to interject. (So no rudeness or just shooting messengers intended) On Thu, Oct 28, 2010 at 8:31 PM, eric.le-r...@nokia.com wrote: We are working on making these defects visible again as soon as possible. There's a chance that the number still grows in the coming days yet the situation should come back to normal quite soon. No, just no. This is an open project. You cannot just say that you will open them up (basically) when you feel like doing it and then furthermore say that more bugs will happen like this - closed off from the open. You need to be presenting a darn good reason why bugs are not being shown to everyone. This is not Nokia where things are closed first, opened on a case-by-case basis. This is an open project, where things should be open unless there are extreme circumstances and reasoning that would allow that bug to be closed (eg. major security bug). Even if there are closed off bugs, there should be a process in order to be able to view these bugs. People are trying to do the best job they can within the MeeGo project, without them getting access to these bugs, they will get blamed for it being missed out on - but they can't even view it! It is hindering their progress. Now you mention that more unexplained closed off bugs will come. Unacceptable. Seriously, sometimes I need to slap myself across the face a couple of times to remember whether this is an open project or a marketing scheme with Nokia and Intel puppeteers. But then I remember it is an open project, with a lot of people acting in the manner they should but it seems like not everyone has crossed the bridge yet to realizing and remembering to participate in the open. BR, Eric Cheers, Bradley Smith IRC: Termana ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Kernel Process Changed
On Fri, May 28, 2010 at 8:22 AM, adhyas.avas...@nokia.com wrote: The wiki at http://wiki.meego.com/Kernel_Process that it is obsolete now. What is the location of the new wiki that talks about the kernel process, if any? So I asked some people the same question. The answer I got was there is no kernel process. Basically, instead of fixing the process, the kernel maintainers killed the process. Thanks, Adhyas Cheers, Bradley Smith IRC/Twitter: Termana ___ 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 Thu, May 27, 2010 at 11:19 PM, Foster, Dawn M dawn.m.fos...@intel.com wrote: 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. What is there to resolve for the TSG? The TSG already agreed on the project licensing AFAIK. The legacy documentation is something that needs to be sorted out license-wise with Nokia/other third-parties - it shouldn't affect MeeGo licensing. If legacy documentation wants to be used then its appropriate to put effort into relicensing the documentation, rather than change licenses for the project IMO, unless its a last resort and the legacy documentation simply cannot be relicensed. Dawn Cheers, Bradley Smith IRC/Twitter: Termana ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Kernel Process Changed
On Fri, May 28, 2010 at 9:22 AM, Greg KH gre...@suse.de wrote:
{sigh}
This isn't acceptable.
No it probably isn't too acceptable, but I'm sure its just temporary.
Should we just delete the wiki page?
I don't think so, there is still useful information. Maybe the
information needs to be moved to another page and then delete the
kernel process page until some sort of actual process has been laid
out for everyone to see.
Who at Intel is responsible for the kernel these days? What happened to
the proceedures they said would be put into place?
I don't know the answer to either of these questions. I have CC'ed
Arjan as he seemed to have an idea what was happening the last time
the kernel process came into question, though I don't think he
specifically deals with maintaining the MeeGo kernel - but we haven't
really been told the maintainers publicly AFAIK so I can't CC them.
greg k-h
Cheers,
Bradley Smith
IRC/Twitter: Termana
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo IRC Meetings
On Wed, May 12, 2010 at 7:26 AM, Ryan Abel rabe...@gmail.com wrote: People should note, of course, that there's no reason people couldn't use a separate #meego-meeting channel (say, #meego-meeting2) if there's a scheduling collision. Just be sure to inform your potential attendees of the proper gathering place. How well is that going to work for people wanting to attend meetings that have colliding times? Some people may find it hard enough to keep up with one meeting if there is enough activity, let alone two. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Btrfs as default file system
On Thu, May 13, 2010 at 7:29 AM, Greg KH gre...@suse.de wrote: And note, if the handheld devices do not use btrfs, some of the features being provided here (snapshot rollback, etc.) will just not work, which might not be good. But if btrfs is the standard filesystem, what will happen if btrfs becomes apart of the compliance rules to use the name MeeGo? Devices it may not be suitable for will be excluded from using the MeeGo brand. Maybe its something that needs to be discussed when it comes around for decision on what requirements must be met to use the MeeGo brand, rather than here, but I thought it was a valid point to bring up. Also, feel free to point me towards the requirements if they have been decided on, but AFAIK, no published list of requirements to use the brand have been made. thanks, greg k-h Cheers, Bradley Smith ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Kernel process comment
On Thu, Apr 29, 2010 at 1:41 AM, Greg KH gre...@suse.de wrote: Um, since when did they not? That is obviously a way of avoiding the original question. Where was any decision made by the community or the TSG that Intel was suppose to take sole responsibility of the MeeGo kernel? How are things supposed to be here? Seriously, have you looked at the owners of the packages on the MeeGo system? Just in case you haven't noticed, MeeGo intends to be an open project, maintained openly. I don't understand how you could see that a single company maintaining the kernel tree and Intel having a veto power translates into anything open. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
