From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Tue, 26 Jun 2018 17:13:25 -0700 [thread overview]
Message-ID: <1588852.P9pr4OxNOe@reaper> (raw)
In-Reply-To: <12571636.4vNX6njMDV@monkey>
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
On Tuesday, June 26, 2018 4:31:01 PM PDT Aaron Bauman wrote:
> [...]
> I do believe there are efforts to address this coming from our own
> developers.
>
> One such example is Michał's (mgorny) efforts with Github as the conduit.
> His automation, CI bot, and personal involvement has shown fruit in the
> form of new developers (sbraz as an example). Such avenues like this can
> be exploited to bridge the gap of "getting involved" within Gentoo. The
> ease of contribution, abiity to review, and ultimately incorporate the
> changes offered by users is conducive to public satisfaction and positive
> PR.
> [...]
> -Aaron
I strongly agree. That's how I became a dev recently =)
And I we have another batch of solid contributors going thru recruitment and
doing quizzes right now, most started as github<->proxy-maint collaborators.
Canonical (bugzilla) way of contributing ebuilds works as well, but is clunky
and less visible, and some contributions are ignored for years and years.
proxy-maint team is pretty strict, but friendly and it usually takes not more
than a week to get a new ebuild accepted given it's decent quality but needs
some polish. Sometimes it takes longer, but hey.
Simple or important bumps can be merged within hours, especially if the
contributor is on IRC and knows when and how to ping the right people.
Even if people contribute to non-proxied ebuilds, members of proxy-maint know
how to communicate it to the right people who are less exposed to github and
the contributions are not ignored and get acknowledged and merged.
Also, contributors learn A LOT while following the review process, both
technical and political details of gentoo.
This is a really good way of attracting and educating `fresh blood`.
Source: fresh blood.
--
Best regards,
Georgy Yakovlev
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-27 0:13 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 [this message]
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
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=1588852.P9pr4OxNOe@reaper \
--to=gyakovlev@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