Re: DRAFT Agenda for GNOME Mobile meeting in Austin

[Sankarshan Mukhopadhyay <foss mailinglists gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Neary wrote:

| I'm phrasing the agenda in terms of objectives, rather than topics.
| There's a reason for that - the topics can be quite loose and lend
| themselves to talking without concrete results for a couple of hours, I
| am hoping that by having solid objectives, and some meat on the bones,
| that we can make some decent progress during the meeting.

I have a small query here - in terms of objectives what does GNOME
Mobile want to do ? I ask this in the perspective of the fact that
"mobile" across various projects in companies seem to be working on
integrating parts that are already in the GNOME tree. So, is the GNOME
Mobile initiative an effort to be a SIG within the GNOME framework
towards ensuring that the bits that are important to "mobile" are
present and in proper shape ? Or, is it something more, like a standards
and frameworks effort specifically for mobile and GNOME ?

This question may be irrelevant to your current mail, but l.g.o doesn't
seem to offer much by the way of information, objective or tasks.

| The one thing which risks being a little bit more vague is the
| discussion on mid- and long-term goals. We can make these concrete, eg
| "Create a virtualised sample GNOME Mobile platform people can play with,
| and publicise and distribute it", or vague, eg "Ensure GNOME Mobile is
| the platform of choice for mobile application writers". I would prefer
| us to keep things as concrete as possible. Also, to help with over-run
| prevention, I put this before lunch :)

Keeping them concrete would probably allow one to measure after a year
as to where the initiative has progressed.


| Generate a list of features and patches which are being maintained
| out-of-tree, and identify resources to get them integrated, where
| relevant, into the upstream project.
|
| Examples:
|  - EDS DBus back-end
|  - Gconf DBus back-end
|  - GTK+/glib patches

Suggestion: The list be generated earlier to the meeting and the meeting
used to discussion on the "what to do now" aspects.


| Identify 1 or 2 mid- and long-term goals for GNOME Mobile. Define a
| strategy for attaining them. Discuss again strategy for communication,
| as on the previous call. Include certification programs in discussion.

Can you elaborate a bit on "certification" please ?

| Define the packages to be included in the GNOME Mobile release package,
| and the short-term goals running up to 2.24 and 2.26.
| Briefly discuss candidate technologies.

Would this require distribution specific feedback as well ?

| Ramping up mobile collaboration: Identify features in the mobile
| platform which is missing, and workgroups to collaborate on building
| them. Goal: A short list of specific features, matches to names of
| people who will commit resources and commit to collaborating within GNOME.

The "meat" of the meeting :)

~sankarshan



- --

http://www.gutenberg.net - Fine literature digitally re-published
http://www.plos.org - Public Library of Science
http://www.creativecommons.org - Flexible copyright for creative work


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFH4k0YXQZpNTcrCzMRArQHAJ4iRFpgzvX/nXoNtWUgHmfoHSgUewCgtL9u
7WCUjP7c11ENCyucJQCf8tU=
=hI8Q
-----END PGP SIGNATURE-----