[Buildroot] More maintainers

[Avraham Shukron]

On Thu, Sep 3, 2020, 01:20 Christian Stewart <christian at paral.in> wrote:

> Discoverability is a problem right now, there's too many patches and
> no way to subscribe to a given series for further updates (similar to
> Pull Requests on GitHub), unless the submitter happens to add you to
> the CC list - which, by the way, usually happens if you add a review.
>
> Today, probably the best approach is to hunt through the backlog
> (sorted by reviewed-by priority order) and cherry-pick some of these
> series into downstream, more "experimental" repositories. Then, once
> they've been tested there, you can submit a Reviewed-By back upstream
> to indicate that it was useful and worth merging more urgently.
>

For what it's worth I think that the mail-based contribution process is
part of the problem.
With a decent Git server like GitHub/GitLab patches could be reviewed more
easily.
A CI pipeline could run tests that will give immediate feedback for any
pull request.
More importantly, it'll dramatically reduce the barrier for new and young
contributors.

Buildroot is all about using simple and familiar tools like make and
Kconfig, and I personally think that this principle should also be applied
to the contribution process and right now buildroot is one of the last
active open source projects using the mailing list approach.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200903/c57da135/attachment.html>