public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council appointed leaders for QA and DevRel
Date: Sun, 14 Aug 2011 16:43:03 +0100	[thread overview]
Message-ID: <4E47ED07.7030103@gentoo.org> (raw)
In-Reply-To: <1313336101.2962.2@NeddySeagoon>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/14/2011 04:35 PM, Roy Bamford wrote:
> On 2011.08.14 14:38, Markos Chandras wrote:
> 
> [snip]
>> Bringing council to the game, ensures that these projects will be 
>> active and managed at a senior level. Right now, there is no
>> recovery plan if these teams do not function properly.
> 
> What's the recovery plan if other projects don't function properly? 
> e.g. Documentation. The install guides still describe setting up 
> baselayout-1, three months after baselayout-2 was stabilised. See 
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=1
>  Code Listing 1.2: Examples for /etc/conf.d/net
> 
> Hmm. maybe thats a bug as 
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8
> is correct for baselayout-2.
> 
> Anyway, I'm sure you get the idea.
> 
> Will the council fix these things too ? Josh, this is just one
> example I'm familiar with. not a poke at you being the entire docs
> team.
> 
> Why are devrel and QA special?
> 
> To continue with my example, I would suggest that docs are much more
>  important as they are first point of contact for new users and
> without users Gentoo will die.
> 
Yes but like I said, many project keep their documentation in their
project pages. Like openrc does for baselayout-2 migration guide.
I don't disagree with you and yes maybe more team need to be
managed/monitor at a senior level. The thing is that something HAS to
change.

I like your idea about the authority team (though  this introduces
another layer of bureaucracy). It would be nice to have a team
monitoring all the projects and poking council to take action when
needed. But this team looks like similar to QA doesn't it? What if this
team is formed by Council members (2-3)? This team will gather feedback
from the community ( "Hey devs, which teams need urgent attention?" ),
design solutions and bring them to the Council agenda?

- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJOR+0HAAoJEPqDWhW0r/LChQ8P/3ImyvreN5dWFuASkqT5pVbc
X/7UacYVy1ubwduixViAjHffn8fE1rCfk8wSOFpKFoJ0vfRqGuR15zCEdyPSYUAh
bFxvRVyC0Ii+uw+7kU6hXboCAy4SSREtt1KgUx3RZ7bfI4Ut2oI0svuc3WTgOeV9
WytZkwWSCJJ+DuXKG+YfgpQPCvrH4QJjwa7MJFm7DLq9n+R5Xr3fctLlR/i4WfQ4
BmNVnFdAWPMJ/kFBW9EBOY1WIAev+b6Rx/XLiIL0AGWyjxEb+ShRZJPZQgbS6w0U
yGXWc+t/kjdLmtic1LwCa3pIjSiYt4GkkhdvSHWgFYRtAdOCyeNwtuAZ7auSSOGW
Zol+45Ry7GN43ismUwvFEUfFUmLkfGCKNI0Ff57fQBc+BE7+t6fYImAh5aIWlat5
aZVkNEaNfT4Kmn4orfGokkemTYKawAtv8Wq6MbswbwE7rfKMdxyc0g0RQMEURn90
oNUuSSDTVIzTHPbXKE1EedHRVNjUv5zD0WkFLRDEmNag3kMpirpK6QsFFEjwkoEV
F5SQ4rOZSYw1oYENmXibvRKUAwL0Fd/dxeQNn6QmB/YhmEbxLJNBHmB9AUq3CqeG
l+bOe1rYro4ZxEZLEThWhz32TjuQidyJdPhmR+YstMz8EzSHQxzJdnLQirsPtYRh
l7aVehMIEydOzGYl0FXl
=ynAf
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-08-14 15:44 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 [this message]
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
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=4E47ED07.7030103@gentoo.org \
    --to=hwoarang@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