From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] On the way Devrel is constituted
Date: Thu, 20 Jun 2013 11:50:34 +0100 [thread overview]
Message-ID: <CAG2jQ8jov=ZQ1EuJD-0H+XyXJr9ARN6a0xgQ-1t4G7jG1DBNGw@mail.gmail.com> (raw)
In-Reply-To: <51C2DD11.7050007@gentoo.org>
On 20 June 2013 11:44, Sean Amoss <ackle@gentoo.org> wrote:
> On 06/19/2013 11:17 PM, Alexis Ballier wrote:
> [...]
>>
>> I could give you a few names I would certainly like to see on council
>> because they have a very good overview of the technical issues council
>> usually discusses but whom I wouldn't see in devrel matters :)
>>
>> Alexis.
>>
>
> Agreed. These two duties require two completely different skill sets and
> yet have a lot of control and impact on the direction of the distribution.
Correct.
>
> One thing I have not seen mentioned yet is the possibility of separating
> these functions out to two individual, high-level, groups: a
> council/board that ONLY handles technical decisions and a devrel that
> handles the social issues and direction of Gentoo; both elected by
> developers.
>
> We need a group that not only reacts to devrel issues, but will actively
> steer the Gentoo culture to create an accountable group of developers
> and a better experience for all.
>
> Sean
>
I agree to everything you said. I am perfectly fine to have DevRel/QA
appointed by the Council.
The council could use these teams to delegate social and technical problems.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
next prev parent reply other threads:[~2013-06-20 10:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 20:18 [gentoo-project] On the way Devrel is constituted hasufell
2013-06-19 20:43 ` Petteri Räty
2013-06-19 21:41 ` hasufell
2013-06-19 22:19 ` William Hubbs
2013-06-20 0:50 ` Alexis Ballier
2013-06-20 2:00 ` Rich Freeman
2013-06-20 3:17 ` Alexis Ballier
2013-06-20 10:44 ` Sean Amoss
2013-06-20 10:50 ` Markos Chandras [this message]
2013-06-20 11:25 ` Douglas Dunn
2013-06-20 11:30 ` Douglas Dunn
2013-06-20 19:03 ` William Hubbs
2013-06-20 19:32 ` Alexis Ballier
2013-06-20 19:33 ` Rich Freeman
2013-06-20 20:07 ` Chí-Thanh Christopher Nguyễn
2013-06-20 20:20 ` William Hubbs
2013-06-20 11:03 ` hasufell
2013-06-20 2:03 ` Rich Freeman
2013-06-20 5:19 ` Samuli Suominen
2013-06-20 7:33 ` Thomas Raschbacher (Gentoo)
2013-06-20 10:41 ` Anthony G. Basile
2013-06-20 8:52 ` Roy Bamford
2013-06-20 11:59 ` Michał Górny
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='CAG2jQ8jov=ZQ1EuJD-0H+XyXJr9ARN6a0xgQ-1t4G7jG1DBNGw@mail.gmail.com' \
--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