public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council manifesto of sping
Date: Mon, 21 Jun 2010 23:07:33 +0200	[thread overview]
Message-ID: <4C1FD495.7070105@gentoo.org> (raw)
In-Reply-To: <4C1FAD5E.9030906@gentoo.org>

Petteri,


On 06/21/10 20:20, Petteri Räty wrote:
>> My manifesto up here now:
>> http://dev.gentoo.org/~sping/council-manifesto-2010-sping.txt
> 
>> - Building sites
>>   - Active Council
>>   - More direct democracy
>>   - New conflict resolution team (reforming DevRel)
>>   - Ownership and territories
>>   - The two sides of infra
>>   - The Git migration
>>   - Opening up documentation
>>   - Gentoo PR: Database and frequent news
>>   - Internal news (i.e. increasing transparency)
>>   - (Paid external) website re-design
>>   - Introducing templates (e.g. for bug replies)
>>   - Tone and attitude in Gentoo
>>   - Other (minor) things
> 
> How many hours do you expect to use weekly to accomplish all these goals?

I will not be able to do this alone - I need the rest of the council and
Gentoo to team up with me on this, no doubt.

A diploma thesis is coming up soon - that will take time away.  Apart
from that Gentoo is among my top 5 focuses.  The numbers of hours I put
into Gentoo per day will range from 0 to 16 hours.


>> To my understanding the conflict resolution part of DevRel is currently not working effectively.
> 
> If we are not working effectively it's not because of how we are
> organized but due to needing more man power.

As I have mentioned before I respectfully disagree with this statement.


> The good thing is that
> people have offered to help and I am slowly training us new members.

I would be interested in details on how DevRel is training people.

Best,



Sebastian



  reply	other threads:[~2010-06-21 21:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` [gentoo-dev] Manifesto for council election Tony "Chainsaw" Vroon
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20   ` Petteri Räty
2010-06-21 21:07     ` Sebastian Pipping [this message]
2010-06-21 19:25   ` Arun Raghavan
2010-06-21 21:36     ` Sebastian Pipping
2010-06-22  1:46       ` Brian Harring
2010-06-22  2:37         ` Sebastian Pipping
2010-06-22  5:13       ` Arun Raghavan
2010-06-22 10:02         ` [gentoo-dev] " Duncan
2010-06-22 10:24           ` Arun Raghavan
2010-06-30  0:45         ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23           ` Arun Raghavan
2010-07-02 15:50             ` Sebastian Pipping
2010-07-02 17:30               ` Nirbheek Chauhan
2010-06-22  5:15       ` Arun Raghavan
2010-06-22  2:37   ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15   ` Arun Raghavan
2010-06-21 19:27     ` Mark Loeser
2010-06-21 19:30       ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford

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=4C1FD495.7070105@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@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