From: Charles Bailey <charles@hashpling.org>
To: git@vger.kernel.org
Subject: Git hackathon London 8th/9th July - call for mentors
Date: Mon, 5 Jun 2017 15:13:35 +0100 [thread overview]
Message-ID: <20170605141335.GA12502@hashpling.org> (raw)
As some of you may have inferred, we had to postpone our plans for a
hackathon event last month but we are now moving ahead with plans for
one in London in July. Thank you to everyone who expressed interest in
being a mentor after my last request.
So, similar to last time...
Bloomberg going to host a Git hackathon over a weekend in London on the
weekend of 8th-9th July 2017.
Crucial to the success of the weekend will be having mentors available
in both locations who can guide people on the project. Mentors should
have some experience with developing for Git and should be familiar with
the process and guidelines around contributing.
If you are interested in being a mentor or have further questions, then
please get in contact with me via email (either to this address or to
cbailey32@bloomberg.net).
Also, whether or not you are able to be at the weekend now would be a
great time to think about any projects which you would like tackled at
this event. Obviously, projects should be completable by small teams
inside of a weekend.
Charles.
---
Git was the first project for which we hosted an "Open Source Day" and
since then we've learned a lot and would like to revisit Git again.
The event will involve volunteers who are usually competent programmers
but who don't necessarily have experience with contributing to Git,
working to contribute to the project over two days. Typically the type
of tasks tackled would include documentation improvements, test case
improvements and very simple bug fixes that have previously been
identified as "low hanging fruit".
reply other threads:[~2017-06-05 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170605141335.GA12502@hashpling.org \
--to=charles@hashpling.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).