From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council 2015 / 2016 election
Date: Thu, 2 Jul 2015 06:06:55 -0400 [thread overview]
Message-ID: <CAGfcS_n8AQ3pXmKyF7N8ptiOep-=bhgWvbW+zmJ1pwyVmuAbaw@mail.gmail.com> (raw)
In-Reply-To: <5594E082.4010301@gentoo.org>
On Thu, Jul 2, 2015 at 2:56 AM, Justin (jlec) <jlec@gentoo.org> wrote:
> On 02/07/15 08:44, "Paweł Hajdan, Jr." wrote:
>> On 7/1/15 8:13 AM, Justin (jlec) wrote:
>>> I will give my full support as a member of the council to infra so that the git
>>> migration may happen this year. We will help to overcome all non-technical
>>> issues so that it's only a matter of setting it up.
>>
>> I like your manifesto.
>>
>> Curious: what are the non-technical issues for git migration?
>
> Hosting for example. That is something typical where the council as official
> representatives of Gentoo could approach potential companies and try to find
> solutions. Of course, that is also be done by infra who most probably have the
> better connections. Nonetheless, this is what I would like to push to support
> infra's work.
>
This is a bit off-topic for this thread, but the last I had heard we
already had the hardware and it just needed somebody to set it up.
That was a few months ago so that could be stale.
I am concerned that infra is fairly overworked, and the nature of it
makes it harder to bring new people in to help. It isn't like anybody
can just pick up a server and start admining it the way they can work
on a package. Stuff like this is probably why github seems to be
slowly taking over the world.
--
Rich
next prev parent reply other threads:[~2015-07-02 10:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 2:50 [gentoo-project] Gentoo Council 2015 / 2016 election Jorge Manuel B. S. Vicetto
2015-06-13 7:09 ` [gentoo-project] Re: [gentoo-dev-announce] " Daniel "zlg" Campbell
2015-06-13 20:38 ` [gentoo-project] " Daniel "zlg" Campbell
2015-06-14 18:46 ` Pacho Ramos
2015-06-16 23:10 ` William Hubbs
2015-06-26 19:47 ` Markos Chandras
2015-06-16 17:54 ` Ulrich Mueller
2015-06-14 14:21 ` Mikle Kolyada
2015-06-14 15:07 ` grozin
2015-06-19 8:19 ` Justin (jlec)
2015-06-16 22:10 ` Andreas K. Huettel
2015-06-14 16:22 ` Andrew Savchenko
2015-06-14 20:48 ` Kristian Fiskerstrand
2015-06-20 19:32 ` Zac Medico
2015-06-24 10:37 ` Rich Freeman
2015-06-15 7:43 ` Alexander Berntsen
2015-06-24 13:08 ` Brian Dolbec
2015-06-16 1:00 ` Jorge Manuel B. S. Vicetto
2015-06-17 4:15 ` Ben de Groot
2015-06-17 11:33 ` Patrick Lauer
2015-06-17 12:56 ` [gentoo-project] " Michael Palimaka
2015-06-24 2:54 ` NP-Hardass
2015-06-27 20:49 ` [gentoo-project] " Luca Barbato
2015-06-19 21:38 ` Wulf C. Krueger
2015-06-25 15:27 ` Denis Dupeyron
2015-06-25 4:23 ` [gentoo-project] Gentoo Council 2015 / 2016 election - < 48 hours for nominations Jorge Manuel B. S. Vicetto
2015-06-25 13:11 ` Andreas K. Huettel
2015-06-25 22:11 ` Alex Legler
2015-06-26 3:14 ` Jorge Manuel B. S. Vicetto
2015-06-28 0:02 ` [gentoo-project] Gentoo Council 2015 / 2016 election Jorge Manuel B. S. Vicetto
2015-06-28 18:15 ` Jorge Manuel B. S. Vicetto
2015-07-01 6:13 ` Justin (jlec)
2015-07-02 6:44 ` "Paweł Hajdan, Jr."
2015-07-02 6:56 ` Justin (jlec)
2015-07-02 10:06 ` Rich Freeman [this message]
2015-07-02 11:42 ` Andreas K. Huettel
2015-07-04 0:06 ` Rich Freeman
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='CAGfcS_n8AQ3pXmKyF7N8ptiOep-=bhgWvbW+zmJ1pwyVmuAbaw@mail.gmail.com' \
--to=rich0@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