From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] My council manifesto
Date: Mon, 21 Jun 2010 15:27:08 -0400 [thread overview]
Message-ID: <20100621192708.GB25835@halcy0n.com> (raw)
In-Reply-To: <AANLkTim1sh59pJjnRrDkygKuVw7-Iwn1VHHIQVcAjQtc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
Arun Raghavan <ford_prefect@gentoo.org> said:
> On 22 June 2010 00:40, Mark Loeser <halcy0n@gentoo.org> wrote:
> > Its quite simple. I want to get innovation starting in Gentoo again. I
> > am tired of seeing pointless arguments and threads that don't actually
> > make Gentoo any better. Improving QA, improving our documentation,
> > making it easier for people to recognize how they can contribute, and
> > improving Gentoo as a whole, are all things that the Council should be
> > taking an active role in, and I want to be a part of making that happen.
>
> Do you have any concrete ideas on how you will be doing these things?
We already have some people very active in QA working on tinderboxing.
I'd like to continue to have their work done, and try to expand on the
work they are doing to have it run on other architectures. I've already
successfully got an ia64 donated for this.
We clearly have people that are interested in working on documentation,
but in wiki format. I want to learn more why they are invested in that
format, and if there is some middle ground we can work on.
Its been a long standing problem that it seems people don't understand
how to become part of Gentoo. I'd like to see the Staffing Needs page
better advertised, and update the How to Become a Developer guide to
help direct people to possible mentors. Having a team of people outside
of the recruiters that are interested in mentoring new people, and how
these new people can get in touch with them would be cool.
I just think that the Council should take a somewhat active role in
trying to keep things moving. There is a lot of good work going on, and
people seem to feel they are blocked for some reason in a lot of cases.
The Council should be there so we can keep progress moving forward in
whatever way we can. Our devs do a lot of good work, and I want to do
my part to make sure they never feel they are hindered from doing that
work, and if they are, figure out how to address that issue.
Hope that helps,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-06-21 19:27 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
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 [this message]
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=20100621192708.GB25835@halcy0n.com \
--to=halcy0n@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