Andre Klapper | 1 Jan 20:02 2010
Picon
Picon

Annual GNOME Bugzilla statistics for 2009

Ladies and Gentlemen,

once again it's time to take a look at GNOME Bugzilla activity in 2009
though no scripts were run yet to provide more information because they
probably have not been ported to Bugzilla 3.4. Anyway, the basic info
exists.

Please keep in mind to not draw too many conclusions from these values,
especially because some of them might be wrong. :-P

Overall statistics:
                                2009    2008    2007
  Open reports at the end(*):   40527  37180    33967
  Opened in that year:          39403  59309   114043
  Closed in that year:          40280  56546   108807
    (*): Excludes reports marked as enhancements
    [A valuable number of reports had also been blocked by
     GNOME Bugzilla's auto-reject feature until 08/2009 or 
     went to crash.gnome.org which is down.]

The following people closed more than 700 bugs in 2009:
  2434       Akhil Laddha
  1784       Fabio Durán Verdugo
  1471       André Klapper
   939       Bastien Nocera
   782       Milan Crha
   762       Matthew Barnes
   746       Tobias Mueller

The following people reported more than 300 bugs in 2009:
(Continue reading)

Javier Jardón | 4 Jan 18:53 2010
Picon

New propossed GnomeGoal: Add code coverage support

Hello,

The objective of the GnomeGoal is to add code coverage of your code
with GCOV [1]
You can take a look to the GnomeGoal page here: [2] (There are also
examples to add GCOV support to json-glib and libgdata)

As a side effect, the idea is encourage devels to:
 - Use the new Glib and GTK+ test frameworks [3] and [4]
 - Use build.gnome.org service. For example, take a look to Glib coverage [5]

All the info is available in the GnomeGoal/AddCodeCoverage page.

Comments / suggestions welcomed.

[1] http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
[2] http://live.gnome.org/GnomeGoals/AddCodeCoverage
[3] http://library.gnome.org/devel/glib/stable/glib-Testing.html
[4] http://library.gnome.org/devel/gtk/stable/gtk-Testing.html
[5] http://fixed.gnome.org/coverage/glib/lcov/
--

-- 
Javier Jardón Cabezas
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Christophe Fergeau | 5 Jan 11:24 2010
Picon

Re: Call for Talks - FOSDEM 2010 (GNOME devroom)

Hi, best wishes for 2010!


2009/12/13 Christophe Fergeau <cfergeau <at> gmail.com>
Hi everyone,

As for the last few years, we'll have a GNOME devroom next year at FOSDEM (6/7
feb in Brussels), and as always, we want *YOU* to give a talk about
the cool project you are hacking on in this devroom
...

Please send your talk proposals before Friday 8th January. With the end of year
holidays, this deadline will come *really* quickly, so the sooner you send a proposal,
the better (before the holidays is great ;).


Just a reminder, the deadline is coming in quickly :) Thanks to all of those who already sent talk proposals, if you want to talk in the devroom, don't wait any longer :)

Thanks,

Christophe
 

_______________________________________________
gtk-devel-list mailing list
gtk-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
Javier Jardón | 7 Jan 20:57 2010
Picon

Session management support, really necessary?

Hello all,

I'd like to discuss about Session Management support [1], and if it's
really necessary.

Lot of modules are replacing GnomeClient with EggSMClient [2], but
some people maintain GnomeClient can be destroyed (or converted to a
"logging out
now" notification) instead of replaced.
Indeed, seems that "if there had never been a GnomeClient, anyone
would want to add EggSMClient or add XSMP to GTK+".

Read Havoc's comment here for a great resume: [3]

How all this fit in the Gnome 3 approach?

Comments?

[1] https://bugzilla.gnome.org/show_bug.cgi?id=79285
[2] http://live.gnome.org/SessionManagement/EggSMClient
[3] https://bugzilla.gnome.org/show_bug.cgi?id=79285#c30
--

-- 
Javier Jardón Cabezas
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Bastien Nocera | 8 Jan 14:46 2010
Picon

totem-pl-parser branched for 2.28

SSIA

Cheers
Max | 9 Jan 12:58 2010

Fwd: Linux Express Desktop *LED*

Hello
as LED seems to be based on GNOME, I forward the mail here.
Maybe it is possible to regard LED as a THEME for Gnome, so that Gnome
can integrate it or adjust itself more to the given layout of Linux
Express Desktop of ylmp.org

btw. is someone working on the online desktop? dooble.sf.net has a
desktop integrated in the browser, maybe it is of interest to add the
online desktop in a browser tab? If someone can discuss and send info
about that, please contact directly.

Thanks for a feedback, if someone starts to realize this LED Theme or
3. Desktop Layout.
Max

---------- Forwarded message ----------
From: Max <petersonmaxx <at> googlemail.com>
Date: 2010/1/9
Subject: Linux Express Desktop *LED*
To: dooble-team <Dooble-team <at> lists.sourceforge.net>, Ubuntu Developers
<ubuntu-devel <at> lists.ubuntu.com>
Cc: Jonathan Riddell <riddell <at> gmail.com>, Michał Zając <michal.zajac <at> gmail.com>

Hello
there is a new Linux XP desktop available for Ubuntu,
The website is here http://ylmf.org/
http://translate.google.com/translate?u=http%3A%2F%2Fylmf.org%2F&sl=zh-CN&tl=en&hl=&ie=UTF-8

You can download the ISO and run the Live Desktop.
Here you find in the Menu the option to Install, not from the CD, but
in the Desktop you can choose to install it in English.

Install it in english as a parallel system
After the installation, please go to language settings> System, Admin,
Lanuage Support
and Remove the Chinese Language.

Voila, you have the english version of the linux XP.
Screenshot> http://img96.imageshack.us/img96/7716/screenshotlx.png

It seems to be an 64 bit operating system, as the web browser dooble
is not installable, which might be a deb. of 32 bit ?

I want to suggest, that the unbuntu developers integrate that
 <at> Express <at>  Desktop, called LED,  as well next to KDE and GNOME.
Would that be possible for the next release? If someone is interested
to do that, please send me a notice for a further idea to discuss.

Thanks Max
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Stefan Kost | 9 Jan 23:01 2010
Picon

Re: New propossed GnomeGoal: Add code coverage support

Am 04.01.2010 19:53, schrieb Javier Jardón:
> Hello,
> 
> The objective of the GnomeGoal is to add code coverage of your code
> with GCOV [1]

Good goal! I wonder how many of the gnome projects even have a test suite, which
is the prerequisite :)

GCov has the drawback that one needs to rebuild the package with coverage flags
enabled. Just a few days ago I found
http://sourceforge.net/projects/bcov/
which does not needs that. I also produces (almost) same results reports like
lcov. I has some missing feature and drawback though. I plan to have a look at
some of the shortcommings.

>
> You can take a look to the GnomeGoal page here: [2] (There are also
> examples to add GCOV support to json-glib and libgdata)
>

Also in the lgo page you gave this commit as an example:
http://git.gnome.org/browse/json-glib/commit/?id=5b4186eb60e953ddbaadcd53b1996d28b06d4a97

I don't think it is a good one. In the configure check it does:
+       GCOV_CFLAGS="$CFLAGS -fprofile-arcs -ftest-coverage"
+       GCOV_LDFLAGS="$LDFLAGS -fprofile-arcs -ftest-coverage"

which should be

+       GCOV_CFLAGS="$CFLAGS -O0 -g -fprofile-arcs -ftest-coverage"
+       GCOV_LDFLAG="$LDFLAGS -lgcov"

Ideally we agree on a name for the target and for the configure flag. Especialy
the configure flag is needed so that it works in build.gnome.org.

Stefan

> As a side effect, the idea is encourage devels to:
>  - Use the new Glib and GTK+ test frameworks [3] and [4]
>  - Use build.gnome.org service. For example, take a look to Glib coverage [5]
> 
> All the info is available in the GnomeGoal/AddCodeCoverage page.
> 
> Comments / suggestions welcomed.
> 
> [1] http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
> [2] http://live.gnome.org/GnomeGoals/AddCodeCoverage
> [3] http://library.gnome.org/devel/glib/stable/glib-Testing.html
> [4] http://library.gnome.org/devel/gtk/stable/gtk-Testing.html
> [5] http://fixed.gnome.org/coverage/glib/lcov/

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Emmanuele Bassi | 10 Jan 10:58 2010
Picon

Re: New propossed GnomeGoal: Add code coverage support

On Sun, 2010-01-10 at 00:01 +0200, Stefan Kost wrote:

> Also in the lgo page you gave this commit as an example:
> http://git.gnome.org/browse/json-glib/commit/?id=5b4186eb60e953ddbaadcd53b1996d28b06d4a97
> 
> I don't think it is a good one. In the configure check it does:
> +       GCOV_CFLAGS="$CFLAGS -fprofile-arcs -ftest-coverage"
> +       GCOV_LDFLAGS="$LDFLAGS -fprofile-arcs -ftest-coverage"
> 
> which should be
> 
> +       GCOV_CFLAGS="$CFLAGS -O0 -g -fprofile-arcs -ftest-coverage"
> +       GCOV_LDFLAG="$LDFLAGS -lgcov"

thanks; I did copy the commit from libgdata, but probably made a copy
and paste thinko.

ciao,
 Emmanuele.
krishna kumar | 10 Jan 16:28 2010
Picon

subscription

hi
pl enroll
--

-- 
krishnakumar T.R
Frederic Crozat | 11 Jan 11:54 2010

TARBALLS DUE: GNOME 2.29.5 Development Release (also: String and UI change announcement)

Hello all,

(Sorry for the delay in sending this email)

Tarballs are due on *today*, Monday January 11th, before 23:59 UTC
for the GNOME 2.29.5 Development Release, which will be delivered on
Wednesday.

Please make sure that your tarballs will be uploaded before Monday
23:59 UTC: tarballs uploaded later than that will probably be too late
to get in 2.29.5. If you are not able to make a tarball before this
deadline or if you think you'll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!

We'd like also to remind you we are entering in :
* String Change Announcement Period : After the GNOME 2.29.5 release, 
string changes must be announced to gnome-doc-list and gnome-i18n.

* UI Change Announcement Period : After the GNOME 2.29.5 release, UI 
changes must be announced to gnome-doc-list.

For more informations about 2.29, the full schedule, the official
module lists and the proposed module lists, please see our colorful
2.29 page on the wiki:
    http://live.gnome.org/TwoPointTwentynine

For a quick overview of the GNOME schedule, please see:
    http://live.gnome.org/Schedule

-- 
Frederic Crozat
Mandriva
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/devel-announce-list


Gmane