From: Aaron Bauman <bman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Sun, 01 Jul 2018 16:25:47 -0400 [thread overview]
Message-ID: <4682100.PWCtmfFfC1@monkey> (raw)
In-Reply-To: <1530473876.735.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Sunday, July 1, 2018 3:37:56 PM EDT Michał Górny wrote:
> W dniu wto, 26.06.2018 o godzinie 09∶11 +0200, użytkownik Michał Górny
>
> napisał:
> > To improve readability of the thread, I'll ask my question in reply to
> > myself ;-).
>
> Next question from me, given the recent affairs.
>
> - How do you feel about Gentoo's use of GitHub? Do you support Gentoo
> providing resources for our users on GitHub? Or are you opposed to
> using GitHub at all?
As stated in previous emails, I absolutely support our use of Github as a
mirror only and allowing our users a familiar and easy way to contribute.
This has beared fruit in the form of new developers as well. I cannot
empirically prove it, but I would suggest that the current uptick in new
developers is due to Github providing a platform for them to contribute.
Regarding the events that occured, I think this is a lesson learned. While
embarrasing for our distro it was not impacting at a code level due to the
deployment model (mirror only). Many individuals have begun addressing the
areas that could be improved to ensure it does not happen again.
-Aaron
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-01 20:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 7:11 [gentoo-project] Gentoo Council nominee 2018/19 questions Michał Górny
2018-06-26 7:12 ` Michał Górny
2018-06-26 16:27 ` Kristian Fiskerstrand
2018-06-26 16:54 ` Matthew Thode
2018-06-26 16:56 ` Michał Górny
2018-06-26 17:14 ` Matthew Thode
2018-06-26 17:00 ` Kristian Fiskerstrand
2018-06-26 17:20 ` Matthew Thode
2018-06-26 17:29 ` Kristian Fiskerstrand
2018-06-26 18:11 ` Matthew Thode
2018-06-26 23:02 ` Aaron Bauman
2018-06-26 23:07 ` M. J. Everitt
2018-06-27 5:35 ` Ulrich Mueller
2018-06-29 2:12 ` William Hubbs
2018-06-26 14:37 ` Christopher Díaz Riveros
2018-06-26 16:40 ` Kristian Fiskerstrand
2018-06-26 23:31 ` Aaron Bauman
2018-06-27 0:13 ` Georgy Yakovlev
2018-06-26 22:17 ` Aaron Bauman
2018-06-26 22:25 ` Kristian Fiskerstrand
2018-06-26 22:43 ` Kristian Fiskerstrand
2018-06-27 6:41 ` Michał Górny
2018-06-27 8:25 ` Michał Górny
2018-06-27 21:13 ` Aaron Bauman
2018-06-27 21:50 ` Thomas Deutschmann
2018-06-28 8:23 ` Kristian Fiskerstrand
2018-06-28 9:27 ` Ulrich Mueller
2018-07-02 15:03 ` William Hubbs
2018-07-11 14:35 ` Mart Raudsepp
2018-06-29 5:15 ` Eray Aslan
2018-06-29 13:13 ` Mart Raudsepp
2018-06-29 18:25 ` Kristian Fiskerstrand
2018-07-01 0:15 ` William Hubbs
2018-07-01 20:58 ` Aaron Bauman
2018-07-01 19:37 ` Michał Górny
2018-07-01 20:25 ` Aaron Bauman [this message]
2018-07-01 23:24 ` Mart Raudsepp
2018-07-02 15:38 ` William Hubbs
2018-07-01 21:04 ` Matthias Maier
2018-07-01 21:11 ` Matthias Maier
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 3:48 M. J. Everitt
2018-07-03 0:37 ` Aaron Bauman
2018-07-11 13:13 ` Mart Raudsepp
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=4682100.PWCtmfFfC1@monkey \
--to=bman@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