public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council appointed leaders for QA and DevRel
Date: Sun, 14 Aug 2011 19:54:44 +0200	[thread overview]
Message-ID: <4E480BE4.80907@gentoo.org> (raw)
In-Reply-To: <4E47F5A4.4000305@gentoo.org>

On 08/14/11 18:19, Markos Chandras wrote:
[snip]

>  This goes a bit OT, but if a project is dead the council MUST find a
> solution to that problem. 

How do you think council will magically do that?
You're saying "this group of a few devs will do magic that fixes problems"

I think that's a very misguided idea, what should happen is that
*everyone* gets more involved. Which means ...
- blog more so people know what you are doing
- recruit people so there are less "single points of failure" - you
going on vacation should not stop all progress on KDE
- figure out problem areas and make them prettier, even if that's not as
much fun. I resurrected a few packages that were neglected, and suddenly
users popped up to take care of them. And were immediately recruited :)
- lead by example. Want package signing? Figure out prior discussion,
provide constructive criticism and then prepare everything so people
just have to agree to it



> Creating activity is not the only solution.
It's the only one with relevant results ;)

Take care,

Patrick



  parent reply	other threads:[~2011-08-14 17:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 11:06 [gentoo-project] Council appointed leaders for QA and DevRel Markos Chandras
2011-08-14 11:19 ` Fabian Groffen
2011-08-14 11:22   ` Markos Chandras
2011-08-14 11:31     ` Fabian Groffen
2011-08-14 11:36       ` Markos Chandras
2011-08-14 11:52         ` Rich Freeman
2011-08-14 11:58           ` Fabian Groffen
2011-08-14 11:35 ` Rich Freeman
2011-08-14 11:41   ` Markos Chandras
2011-08-17 16:26   ` Markos Chandras
2011-08-17 18:16     ` Rich Freeman
2011-08-17 18:47       ` Markos Chandras
2011-08-14 12:15 ` Thomas Sachau
2011-08-14 12:24   ` Markos Chandras
2011-08-14 13:07     ` Thomas Sachau
2011-08-14 13:38       ` Markos Chandras
2011-08-14 15:35         ` Roy Bamford
2011-08-14 15:43           ` Markos Chandras
2011-08-14 16:40             ` Roy Bamford
2011-08-14 17:27             ` Roy Bamford
2011-08-18  1:41             ` Jorge Manuel B. S. Vicetto
2011-08-14 16:07         ` Thomas Sachau
2011-08-14 16:19           ` Markos Chandras
2011-08-14 16:48             ` Thomas Sachau
2011-08-14 16:56               ` Markos Chandras
2011-08-14 18:03                 ` Roy Bamford
2011-08-14 18:50                   ` Markos Chandras
2011-08-14 17:54             ` Patrick Lauer [this message]
2011-08-14 14:19 ` Roy Bamford
2011-08-14 14:35   ` Petteri Räty
2011-08-14 16:31     ` Roy Bamford
2011-08-15 19:30       ` Petteri Räty
2011-08-14 14:36   ` Markos Chandras
2011-08-14 14:39   ` Rich Freeman
2011-08-14 14:39   ` Markos Chandras
2011-08-14 16:12     ` Roy Bamford
2011-08-14 16:22       ` Markos Chandras
2011-08-15 19:29       ` Petteri Räty
2011-08-18  1:56         ` Jorge Manuel B. S. Vicetto
2011-08-18  2:18 ` Jorge Manuel B. S. Vicetto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E480BE4.80907@gentoo.org \
    --to=patrick@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox