Formal signoff on moblin-meego change?

[Peter Robinson]

On Fri, Oct 15, 2010 at 4:49 PM, Paul W. Frields <stickster at gmail.com> wrote:
> On Thu, Oct 14, 2010 at 11:19:11PM +0100, Peter Robinson wrote:
>> On Thu, Oct 14, 2010 at 8:37 PM, Paul W. Frields <stickster at gmail.com> wrote:
>> > On Thu, Oct 14, 2010 at 10:26:57AM -0500, Bruno Wolff III wrote:
>> >> On Thu, Oct 14, 2010 at 10:37:35 -0400,
>> >>   "Jared K. Smith" <jsmith at fedoraproject.org> wrote:
>> >> >
>> >> > In talking with Peter Robinson, it seems like we're headed down the
>> >> > "pick another name not using the MeeGo mark" road.  I'm assuming we're
>> >> > going to to call the spin something like the "Fedora Mobility" spin.
>> >> > I'm copying Peter on this, so that he can help fill us in on his
>> >> > plans.
>> >>
>> >> If anything still needs to change to the spin to make this happen we are
>> >> getting very late in the game. I would expect if anything further was
>> >> needed from the design team it would also be pretty late.
>> >> The wiki has a bit more slack time, but if it needs to change, I'd rather
>> >> know sooner than later so I don't have to do a fire drill right before
>> >> some deadline.
>> >
>> > Peter had earlier proposed stripping the MeeGo logo (since we wouldn't
>> > want to trip over their trademarks) and using a standard Fedora logo.
>> > I'm not sure any technical changes need to made other than that, and
>> > it might in fact be done already.
>> >
>> > Calling it the Mobility spin would cause a content changed on the
>> > spins.fp.o website, but that also seems like it's not a ton of work,
>> > although Peter might want a Design person to rework the graphics for
>> > that page.
>>
>> I would like to call it Fedora Mobility Netbook but the spin isn't
>> ready so I think we can just drop it all together for this release.
>> Lately it seems there's a lot of contention upstream and there's other
>> code related things that are causing problems and over the last couple
>> of months I've just not had the time to dedicate to it.
>>
>> So for F-14 the spin formally known as MeeGo can be forgotten (very
>> unfortunately), I hope to get a remix at some point but that will
>> remain to be seen.
>
> Peter -- sorry to hear that.  A couple points I wanted to make:
>
> * We have a talking point currently listed for the Mobility spin.  It
>  makes sense to me for the Marketing team to change that to simply
>  mention inclusion of some software from the MeeGo project in Fedora,
>  without reference to a spin at this time.

Sounds good. I'm hoping to get it workable before long. Work and other
commitments killed it unfortunately because I just didn't have the
time I needed to dig down to fix the issues I was seeing. I hope to do
a remix instead within a month or so of the official F-14 release,
possibly even with MeeGo 1.1

> * Are you interested in using the upcoming FUDCon in Tempe to
>  evangelize for Mobility, Sugar, etc.?  I think it'd be a good
>  opportunity since we'll have student attendees from ASU.

Yes, we ran a mobility session at Zurich as well and it looks like
there's going to be at least 3-4 Sugar people at Tempe as well as a
lot of people that are interested in MeeGo so hopefully we'll be able
to ramp it up further there.

> * Are there specific tasks laid out somewhere that the Board and
>  contributors like myself could point out to someone who wanted to
>  help, like a blocker bug list, wiki page, or something like that?
>  I'd love to bring some more hands in to help, and it's super-helpful
>  if I can point them to a list like that.

Not really as yet. There's a tracker bug for both MeeGo 1.0 [1] and
1.1 [2] as well as a general Mobility one [3] but I really need to
finish migrating the Mini stuff to Mobility and put in wiki redirects
where necessary so if there's someone that's more of a wiki genius
that I am (not hard!) it would be great to get that cleaned up so all
the old Mini/Moblin/MeeGo links redirect to the central
https://fedoraproject.org/wiki/Mobility page

Peter

[1] https://bugzilla.redhat.com/show_bug.cgi?id=538447
[2] https://bugzilla.redhat.com/show_bug.cgi?id=620175
[3] https://bugzilla.redhat.com/show_bug.cgi?id=462851