From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Metastructure: reorganization (Was: Call for agenda items - Council meeting 2013-11-12)
Date: Tue, 29 Oct 2013 23:48:43 +0100 [thread overview]
Message-ID: <201310292348.43755.dilfridge@gentoo.org> (raw)
In-Reply-To: <21104.13201.654027.432888@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: Text/Plain, Size: 2391 bytes --]
Am Dienstag, 29. Oktober 2013, 23:15:45 schrieb Ulrich Mueller:
> >>>>> On Tue, 29 Oct 2013, Andreas K Huettel wrote:
> > If you look at our metastructure page, it's a bit of a mess. Some
> > careful rearrangement might make sense... How about this:
> >
> > 1) top level project "Gentoo Programming Resources"
> >
> > - title in table is wrong, should be (according to project page)
> >
> > "Gentoo Resources for Programming Languages", or just "Programming
> > Languages"
> >
> > - has subprojects ada, haskell, ruby
> >
> > proposed action: move java, lisp, perl, php, python in there as
> > additional subprojects
>
> GLEP 39 defines a project as "a group of developers working towards a
> goal".
>
> I don't see what we would gain by collecting several unrelated
> projects under an umbrella TLP. Are there any resources that can be
> shared, or is there a large overlap between devs working in the
> different language projects? In short, what problem are you trying to
> solve?
Actually for asking this question you've picked the best example...
Imagine the poor KDE guys sorting out the language bindings for Ruby, Python,
Java, and C#. Each comes with its own approach to solve the same problems, and
with its own completely disjunct eclass syntax.
Imagine updating your system after a while and then remembering that you need
to run python-cleaner and perl-updater (and what was the syntax there again?).
Maybe there isn't too much overlap right now, but people talking to each other
would certainly help, and the problems are certainly related.
This is the most important thing, and similar ideas also apply to the two
other proposals. (PR, CoC enforcement and Ops are certainly related tasks?)
There's two additional motivations from my side.
One is my stereotypical German preference for cleanlyness and order. Or maybe
it's just that part of leaving a professional impression is also that you
don't just have a messy list of unordered projects.
The other one is that on the long run we might reconsider the role of umbrella
project leads. I'm not so sure yet what we should do there though...
Strengthen, give them tasks? some loose oversight that subprojects follow
formalities? Abandon?
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-10-29 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1701685.NthhqudeZE@kailua>
2013-10-29 21:50 ` [gentoo-project] Metastructure: Dead projects (was: Call for agenda items - Council meeting 2013-11-12) Andreas K. Huettel
2013-10-29 21:55 ` [gentoo-project] Metastructure: reorganization (Was: " Andreas K. Huettel
2013-10-29 22:15 ` Ulrich Mueller
2013-10-29 22:48 ` Andreas K. Huettel [this message]
2013-10-30 6:46 ` [gentoo-project] Metastructure: reorganization Ulrich Mueller
2013-10-30 7:36 ` Rich Freeman
2013-10-30 13:00 ` Panagiotis Christopoulos
2013-10-30 0:33 ` [gentoo-project] Re: [gentoo-dev-announce] Call for agenda items - pgp key handling Patrick Lauer
2013-10-30 5:35 ` Brian Dolbec
2013-10-30 5:55 ` Rich Freeman
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=201310292348.43755.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@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