From: Devan Franchini <oot153@gmail.com>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Subject: [gentoo-soc] Layman Improvements -- introductory report
Date: Mon, 19 May 2014 14:44:54 -0400 [thread overview]
Message-ID: <CA+UEbAiF5sxpPtuU8_qVy3i+UW4FsEeo-q6PsdKFiBFCiGNUHg@mail.gmail.com> (raw)
Hello Gentoo community!
For this GSoC 2014 I've been accepted by the Gentoo Foundation to work on
improvements to the Gentoo tool, Layman. I will have two mentors[1] the official
one on my Google melange is Matthew Summers (quantumsummers)[2], and Brian
Dolbec (dol-sen).
Throughout the summer I hope to expand the available repo types supported along
with adding new features such as:
* Repo URL updating
* Syncing overlays through portage
* A utility script for creating layman XML definitions
* Per repo branch user settings.
To list a few.
Source Code:
next reply other threads:[~2014-05-19 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 18:44 Devan Franchini [this message]
2014-05-19 19:37 ` [gentoo-soc] Layman Improvements -- introductory report Anthony G. Basile
2014-05-19 19:58 ` Brian Dolbec
2014-05-19 20:57 ` EBo
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=CA+UEbAiF5sxpPtuU8_qVy3i+UW4FsEeo-q6PsdKFiBFCiGNUHg@mail.gmail.com \
--to=oot153@gmail.com \
--cc=gentoo-soc@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