Re: Module proposal: Mutter

2010-04-01 Thread Stefan Kost
Pat Suwalski wrote:
 On 30/03/10 07:17 PM, Owen Taylor wrote:
   Mutter packages exist for most major Linux distributions as part of
   packaging GNOME Shell. Mutter is also key component of the Moblin 2.0
   and 2.1 releases.

 With the uncertain future of Moblin, is this appropriate?

 Will Meego continue with Mutter? What is the relation of Meego going
 forward and GTK; is Meego going to turn into a large multi-toolkit
 monster?
This might be valid concerns for MeeGo, but imho not for GNOME. Please
also be aware that qt will be the reference UI for mobile device
category. Don't extrapolate :)

Stefan

 Not that my opinion matters, but I think these are all good questions.

 --Pat
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/desktop-devel-list

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Module proposal: Mutter

2010-03-31 Thread Pat Suwalski

On 30/03/10 07:17 PM, Owen Taylor wrote:

  Mutter packages exist for most major Linux distributions as part of
  packaging GNOME Shell. Mutter is also key component of the Moblin 2.0
  and 2.1 releases.


With the uncertain future of Moblin, is this appropriate?

Will Meego continue with Mutter? What is the relation of Meego going 
forward and GTK; is Meego going to turn into a large multi-toolkit monster?


Not that my opinion matters, but I think these are all good questions.

--Pat
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Module proposal: Mutter

2010-03-31 Thread Emmanuele Bassi
On Wed, 2010-03-31 at 10:39 -0400, Pat Suwalski wrote:
 On 30/03/10 07:17 PM, Owen Taylor wrote:
Mutter packages exist for most major Linux distributions as part of
packaging GNOME Shell. Mutter is also key component of the Moblin 2.0
and 2.1 releases.
 
 With the uncertain future of Moblin, is this appropriate?
 
 Will Meego continue with Mutter? What is the relation of Meego going 
 forward and GTK; is Meego going to turn into a large multi-toolkit monster?

MeeGo for Netbooks 1.0 will definitely ship (and develop) Mutter and
Clutter, and it is going to do so for the foreseeable future releases of
MeeGo for Netbooks.

Mutter is maintained on git.gnome.org, and under the governance of
members of the GNOME community, so MeeGo has no direct influence on
Mutter - not any more than MeeGo has influence on, say, Nautilus[0].

as a side, I'm personally trying to get Clutter's governance and
contributions more open, and resolve the contributors agreement issue
that has been raised by the Foundation; I might have an announcement on
this regard soon.

 Not that my opinion matters, but I think these are all good questions.

I agree, that's why I wanted to give an authoritative answer with my
MeeGo developer/Intel employee hat on.

ciao,
 Emmanuele.

[0] just like with Nautilus, MeeGo ships Mutter with
distribution-specific patches, especially considering the fairly
different user experience we're trying to convey. whenever it makes
sense, we upstream those patches as soon as we possibly can.

-- 
W: http://www.emmanuelebassi.name
B: http://blogs.gnome.org/ebassi

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Module proposal: Mutter

2010-03-30 Thread Owen Taylor
Purpose: 
 Mutter is a window and compositing manager that displays and manages
 your desktop via OpenGL. Mutter combines a sophisticated display engine
 using the Clutter toolkit with solid window-management logic inherited
 from the Metacity window manager.

 While Mutter can be used stand-alone, it is primarily intended to be
 used as the display core of a larger system such as gnome-shell or
 Moblin. For this reason, Mutter is very extensible via plugins, which
 are used both to add fancy visual effects and to rework the window
 management behaviors to meet the needs of the environment.

Target: Desktop Release Set

Dependencies:
 No dependencies beyond current GNOME modules and external dependencies.
 
 Note that Mutter currently depends on Metacity being installed for 
 GConf schemas and other data files.

Resource usage:
 tarballs:http://ftp.gnome.org/pub/GNOME/sources/mutter
 source control:  git://git.gnome.org/mutter
 bugzilla:http://bugzilla.gnome.org, mutter product
 
Adoption:
 Mutter packages exist for most major Linux distributions as part of
 packaging GNOME Shell. Mutter is also key component of the Moblin 2.0
 and 2.1 releases.

GNOME-ness / community: 
 Since Mutter is derived from the Metacity code base, it should interact
 ideally with existing GNOME components and takes advantage of many years
 of bug fixing and development.


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list