mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
Subject: Re: [PATCH 0/1] Applying barebox for Google Summer of Code 2022
Date: Sun, 6 Mar 2022 20:19:36 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 21.02.22 14:52, Ahmad Fatoum wrote:
> On 17.02.22 09:27, Ahmad Fatoum wrote:
>> I'll submit the GSoC proposal over the weekend. Sorry for the short
>> notice, but patches to the project ideas can still follow afterwards.
> Just submitted the proposal:

"Thank you for applying to be a Google Summer of Code 2022 mentor organization.
Sadly, we were unable to accept barebox this year. We had many more applications
than available slots. We hope you will apply again in the future!"

We might try again next year. Till then, if you want to tackle a task,
feel free to reach out. :-)


>> Why does your organization want to participate in Google Summer of Code?
> Firmware development is on the lesser accessible end of software projects: It often requires
> special hardware, resources are not very beginner-friendly and while there are established
> open source projects, the majority of contributions is company-sponsored, making it
> harder for interested individuals to get started on their own.
> Since 2009, the barebox project has been working to lessen this gap: By aligning itself with
> Linux code and convention, it provides a more familiar UNIX-like interface to the low-level
> details, which many users are already acquainted with.
> Besides improving its documentation, in recent years, barebox has also considerably improved
> its support for virtualized platforms, so development can happen in user-mode without dedicated
> hardware, for example the web demo at
> We are confident that this will make on-boarding process easier. It will teach contributors the ropes of
> low level programming and empower them to dive deeper, both inside barebox and outside
> in other low-level projects, like the Linux kernel, which barebox shares a lot of code with.
> We hope to not only benefit from the code produced, but to involve motivated individuals with
> (a newly-found?) low-level affinity, who may continue to use and improve barebox while
> exploring more of the world; be it kernel, runtime firmware or system software.
>> What would your organization consider to be a successful GSoC program?
> The program results should be upstreamed into barebox and it should be reusable
> for further work, e.g. a GSoC contributor adding support for their WLAN router not only
> serves their immediate use case, but also makes future ports of similar hardware easier.
> There are a number of project ideas collected here:
> which contributors can base their proposals on.
>> How will you keep mentors engaged with their GSoC contributors?
> Mentors and contributors will agree on pre-scheduled meetings to synchronize.
> We expect mentors to give advance notice if the schedule can't be observed.
> There will be a fallback mentor for each program should a mentor not have the time
> to continue.
> We will encourage students to use the existing communication channels to get
> feedback from the community at large and to get involved in it.
> If GSoC is approved for more than one applicant, mentors and contributors can
> organize discussions  in a group setting, where common problems are discussed
> and approached for solving them and to see how to tackle them at
> an organizational level if applicable.
>> How will you keep GSoC contributors on schedule to complete their projects?
> In the beginning, individual goals and milestones will be set according to the contributors
> experience and to their project.
> Weekly/Bi-Weekly meeting will be held to discuss progress. Contributors are expected to
> publicly publish code, even prior to upstreaming. Contributors should maintain a blog
> to document their journey. In case unexpected problems arise, mentors will try to steer projects
> to make the most out of contributor time.
>> How will you get your GSoC contributors involved in your community during GSoC?
> Collaboration currently happens via the mailing list and the IRC/Matrix channel. Mentors
> will guide contributors on how to get a working setup for mailing list collaboration. Contributors
> will be encouraged to discuss their questions in the real-time chat.
> Let's see if it works out. :-)
> Cheers,
> Ahmad

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

barebox mailing list

      reply	other threads:[~2022-03-06 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:27 Ahmad Fatoum
2022-02-17  8:27 ` [PATCH 1/1] Documentation: devel: add new project ideas section Ahmad Fatoum
2022-02-18 21:25   ` Antony Pavlov
2022-02-21 13:54     ` Ahmad Fatoum
2022-02-21 13:52 ` [PATCH 0/1] Applying barebox for Google Summer of Code 2022 Ahmad Fatoum
2022-03-06 19:19   ` Ahmad Fatoum [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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