public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Cc: ikelos@gentoo.org, bugday@gentoo.org, zmedico@gentoo.org,
	 ruby@gentoo.org, beandog@gentoo.org, damage@devloop.de,
	 mikevalstar@gmail.com, ycarus@zugaina.org, flameeyes@gentoo.org
Subject: [gentoo-soc] Your part on ideas/issues for Google Summer of Code 2010
Date: Thu, 04 Mar 2010 01:03:38 +0100	[thread overview]
Message-ID: <4B8EF8DA.6080609@gentoo.org> (raw)

Hello there!


GSOC 2010 isn't too far away anymore, quite close actually.
I noticed that the list of current GSOC'10 ideas [1] is more or less
the list of last year...

As GSOC is a big chance for Gentoo to get real needs filled by
people who actually have time (and no excuses ;-)) ..

   it is extra important in my eyes to have stuff in
   that list that really makes a difference

to a larger group of people, i.e. any subset of Gentoo users and/or
developers.

Therefore I would like to start an extra round of brainstorming.

   Please ask yourself:

   1. What current Gentoo-related projects of yours
      have "outsourcable" tasks to fill?

   2. What other needs in Gentoo with need for manpower
      are "outsourcable" but not in the current list of ideas?

A list of things I thought of can be found at the bottom of this mail.
That list is the reason why you're all in CC, if you're still wondering:

No please have a look at that list and talk back to us.



Sebastian


[1] http://en.gentoo-wiki.com/wiki/Google_Summer_of_Code_2010_ideas

===========================================================================

@all
"upstream release tracker"  (brought up by ikelos on g-core recently)
potential resources:
- oswatershed
  - http://oswatershed.org/
  - http://github.com/tannewt/open-source-watershed
- Debian watch files
  - http://wiki.debian.org/DEHS
  - http://manpages.debian.net/cgi-bin/man.cgi?query=uscan&sektion=1


@all
"overlay clean-up website"
a website helping overlay maintainers to detect cruft and errors:
- ebuilds with newer versions in other trees
- ebuilds with critical repoman failures


@bugday  (i.e. @deathwing00 + @gurligebis)
re-write bugday website
(unless you want to do it all yourself)


@zmedico
implement a bunch of repoman checks
http://bugs.gentoo.org/buglist.cgi?quicksearch=repoman


@zmedico
Native Portage Multilib Support?
http://bugs.gentoo.org/show_bug.cgi?id=145737


@ruby
wasn't there some bigger ruby-task for an earlier gsoc
that never got implemented though a good proposal was
posted?  anything you would like to "give away"?


Notable "external" services
  @beandog
    - http://znurt.org/
  @damage
    - http://portagefilelist.de/
  @mikevalstar
    - http://gentoo-portage.com/
  @ycarus
    - http://gpo.zugaina.org/
    - http://gentoo-portage.zugaina.org/
  <more here>


Another reminder (repetition is king :-)):

   1. What current Gentoo-related projects of yours
      have "outsourcable" tasks to fill?

   2. What other needs in Gentoo with need for manpower
      are "outsourcable" but not in the current list of ideas?



             reply	other threads:[~2010-03-04  0:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  0:03 Sebastian Pipping [this message]
2010-03-04  7:13 ` [gentoo-soc] Re: Your part on ideas/issues for Google Summer of Code 2010 Hans de Graaff
2010-03-26 22:18   ` Sebastian Pipping
2010-03-04  7:17 ` [gentoo-soc] " Arun Raghavan
2010-03-04  7:52   ` Nirbheek Chauhan
2010-03-05  0:21     ` Sebastian Pipping
2010-03-05  0:22   ` Sebastian Pipping
2010-03-05  6:21     ` Nirbheek Chauhan
2010-03-05  6:26       ` Nirbheek Chauhan
2010-03-28 18:15   ` Hans de Graaff
2010-03-05  5:20 ` [gentoo-soc] " Zac Medico
2010-03-05 15:43   ` Sebastian Pipping
2010-03-06  0:51     ` 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=4B8EF8DA.6080609@gentoo.org \
    --to=sping@gentoo.org \
    --cc=beandog@gentoo.org \
    --cc=bugday@gentoo.org \
    --cc=damage@devloop.de \
    --cc=flameeyes@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=ikelos@gentoo.org \
    --cc=mikevalstar@gmail.com \
    --cc=ruby@gentoo.org \
    --cc=ycarus@zugaina.org \
    --cc=zmedico@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