From: Sebastian Pipping <webmaster@hartwork.org>
To: Robert Buchholz <rbu@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org,
"PackageKit users and developers list"
<packagekit@lists.freedesktop.org>, "Paul Wise" <pabs@debian.org>,
"Petteri Räty" <betelgeuse@gentoo.org>
Subject: Re: [packagekit] [gentoo-dev] Inviting you to project "PackageMap"
Date: Mon, 15 Jun 2009 19:04:08 +0200 [thread overview]
Message-ID: <4A367F08.3050209@hartwork.org> (raw)
In-Reply-To: <200906151552.08793.rbu@gentoo.org>
Robert Buchholz wrote:
> On Saturday 13 June 2009, Sebastian Pipping wrote:
>> One of the stronger points for collaborating at the source is that
>> poeple who are not Gentoo devs (yet) and therefore have no write
>> access to the Gentoo tree can still extend and fix the Gentoo
>> packagemap entries. Doing it downstream would hurt the whole project
>> in several ways.
>
> To drive the project forward and find cross-distro acceptance, the
> packagemap repo/server has to be the authorative source of information
> for distributions that participate.
>
> However, I see advantages in a distributed model to collect the
> information. Gentoo developers could feed <cpe> tags into the
> metadata.xml of the tree and do not need to sign up to commit to the
> third-party packagemap repository. Synchronizing changed tags to the
> packagemap repository should be easy to automate. Changes in the
> repository could be propagated back to the tree by a designated team of
> Gentoo developers interested in the packagemap project.
>
> I have a feeling other distributions might also favor a model where they
> have more control about the data without giving all their devs access
> to one big repo.
Paul Wise of Debian also articulated interest in doing database building
at distro level, so that's one more point /for/ your feeling.
However there are a few more things to take into account,
please have a look at my reply to Paul:
http://lists.alioth.debian.org/pipermail/popcon-developers/2009-June/001759.html
Sorry for not CC'ing you, I should have though of that.
Thinking the other way around: Is there anything we could do
to make the central place approach work and feel better for everybody?
Sebastian
next prev parent reply other threads:[~2009-06-15 17:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 7:42 [gentoo-dev] Inviting you to project "PackageMap" Sebastian Pipping
[not found] ` <15e53e180906120130md68cd94nba61fa5560c73eb4@mail.gmail.com>
2009-06-12 9:54 ` [gentoo-dev] Re: [packagekit] " Sebastian Pipping
2009-06-17 12:08 ` Tiziano Müller
2009-06-12 13:00 ` [gentoo-dev] " Steven J Long
2009-06-13 3:55 ` Sebastian Pipping
2009-07-11 21:38 ` [gentoo-dev] " Steven J Long
2009-06-12 18:27 ` [gentoo-dev] " Petteri Räty
2009-06-12 21:43 ` [packagekit] " Sebastian Pipping
2009-06-13 15:53 ` Petteri Räty
2009-06-13 19:03 ` Sebastian Pipping
2009-06-13 19:16 ` Petteri Räty
2009-06-15 13:52 ` Robert Buchholz
2009-06-15 17:04 ` Sebastian Pipping [this message]
2009-06-15 18:24 ` Robert Buchholz
2009-06-15 19:13 ` Sebastian Pipping
2009-06-15 20:27 ` Petteri Räty
2009-06-17 0:34 ` Sebastian Pipping
2009-06-17 9:37 ` Marijn Schouten (hkBst)
2009-06-18 0:09 ` Sebastian Pipping
2009-06-18 9:07 ` Marijn Schouten (hkBst)
2009-06-19 18:53 ` Sebastian Pipping
[not found] ` <1245295820.11471.223.camel@chianamo.mine.nu>
2009-06-18 22:33 ` Sebastian Pipping
[not found] ` <1245382383.14805.281.camel@chianamo.mine.nu>
2009-06-19 17:36 ` Sebastian Pipping
2009-06-19 21:47 ` Sebastian Pipping
2009-06-20 13:16 ` Petteri Räty
2009-06-20 17:28 ` Sebastian Pipping
2009-07-14 16:49 ` Sebastian Pipping
2009-07-20 2:03 ` [GLEP] CPE names in metadata (was Re: [gentoo-dev] Inviting you to project "PackageMap") Sebastian Pipping
2009-06-15 21:27 ` [gentoo-dev] Re: [packagekit] Inviting you to project "PackageMap" Christian Faulhammer
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=4A367F08.3050209@hartwork.org \
--to=webmaster@hartwork.org \
--cc=betelgeuse@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pabs@debian.org \
--cc=packagekit@lists.freedesktop.org \
--cc=rbu@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