public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Colleen Josephson <cjoseph@mit.edu>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Looking for a mentor for a Portage SOC Project
Date: Wed, 30 Mar 2011 15:22:47 -0500	[thread overview]
Message-ID: <AANLkTi=un9Gmqs23LGUV1i6NSyzbTGqJv=1779oi-KpY@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]

I'm interested in expanding the Portage "tags" idea listed on the wiki.
To make it SOC-worthy, it obviously needs to be expanded.

I have thought of a few possibilities:
-Integrate eix into Portage as a replacement to search
-Add a Debian-apt style autocomplete
-Add a flag to force the removal of config files when removing a package, if
desired
-Add a feature that lists which commands were installed after merging a
package
e.g. after installing net-tools successfully, emerge would say:
"Commands in net-tools: arp, hostname, ifconfig, ipmaddr, iptunnel,
mii-tool, nameif, netstat, plipconfig, rarp, route and slattach"
For packages that install something in /etc/init.d, it would list how to
start it: e.g. "To start service, run '/etc/init.d/servicename start'"
It would also be nice to have the ability to look this up to see the
commands associated with an already installed package:
e.g. "emerge --list-commands packagename" or something similar.

I am trying to determine whether or not these features are enough to fill a
summer, or if I need more.
There are 14 weeks in SOC, 13 weeks of coding if I leave the last week for
polishing things.
I'm thinking: 3 weeks for eix integration, 1-2 weeks for tags, 1 week for
the --remove-config flag, 2-3 weeks for the autocomplete, and 4 weeks for
the "commands installed" feature.
It looks like I need 1 more "agenda item" to fill the summer. Any
suggestions?

Do these timeframes sound reasonable? I have 3-4 years of coding experience,
with 2 years of Python.

I'm in need of a mentor ASAP so I can get feedback while writing up my
proposal, and have somebody point me to a good bugfix to do.

--
Colleen Josephson
Dept. of Electrical Engineering and Computer Science
Massachusetts Institute of Technology
Class of 2013

[-- Attachment #2: Type: text/html, Size: 1956 bytes --]

             reply	other threads:[~2011-03-30 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 20:22 Colleen Josephson [this message]
2011-03-30 20:57 ` [gentoo-soc] Looking for a mentor for a Portage SOC Project Jeremy Olexa
2011-03-30 21:15   ` Colleen Josephson
2011-03-30 21:34 ` Donnie Berkholz
2011-03-30 22:26   ` Colleen Josephson
2011-03-31  1:24     ` Donnie Berkholz
2011-03-31  1:42 ` Brian Dolbec
2011-04-01  2:20 ` Zac Medico
2011-04-03  3:30   ` Colleen Josephson
2011-04-04 18:31     ` Zac Medico

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='AANLkTi=un9Gmqs23LGUV1i6NSyzbTGqJv=1779oi-KpY@mail.gmail.com' \
    --to=cjoseph@mit.edu \
    --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