Re: fresh blood

On Mon, 2014-06-16 at 14:57 +0200, Frederic Peters wrote:
We exchanged a few lines with Matthias a few days ago as we both noted
that we were all burned out recently, and Andre told us he had the
same kind of conversation with Allan during GNOME.Asia.

We need to act on this, we have a release team BoF planned for GUADEC
already, but we also think it would be a good idea to invite people to
join early on, so they can think things over for a few weeks before.

My idea would be to send a short email to desktop-devel-list, and
individually we could follow up to whoever we feel should really

This also might be something to mention in the 5min team presentation on
Saturday (is that on anybody's todo list?)

Trying to identify what we've done in the last 12 months and mixing this
with topics to potentially discuss in our BoF:

* 3.10 and 3.12 releases; usual nagging and reminding of tasks
* unexpected breakage by renaming gnome-icon-theme to adwaita-icon-theme
* not much going on though we're supposed to lead more on having
discussions about platform decisions and being more active in setting
direction; need fresh blood - join the BoF
* do we followup on blockers? See remaining ones for 3.12 here:;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO
* does our schedule (e.g. feature proposals) really make sense?

Personally I've set to
3.14 (Modal password boxes prevent users from looking up or generating
passwords) as it's been a constant source of duplicates and complaints,
but I have no idea how to make things actually happen and which venue to
have a dedicated discussion with the design team. I guess there are more
examples of this.

If we make a public call for fresh blood, what would be useful criteria
for a self-check of a potential release team member wannabe?

andre (damn busy until October)


  Subject: Want to join the release team?

  Hi all,

  You know the release team as the senders of those pesky "tarballs
  due" emails and indeed defining and maintaining a release schedule
  is one part of the job, but there's way more to do and often you'll
  hear regrets that the release team doesn't involve itself more in
  certain matters.

  Truth is we all have been doing the job for a few years now, we were
  there when we got GNOME 3.0 out, and we are quite burned out those
  days (some old timers will say release team members were in a
  similar state a few releases after GNOME 2.0).

  And so we are turning to you, with this wide call to join the
  release team, there's no definite set of requirements, familiarity
  with the various modules, the tools, and of course the community,
  helps, but most of it happens along the way, so don't let anything
  stop you.

  Think about it, mail us or join #release-team if you have questions,
  and we will have a BoF during GUADEC to decide things for real.

  See you,


release-team gnome org
Release-team lurker? Do NOT participate in discussions.

Andre Klapper  |  ak-47 gmx net

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]