public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Jan Hauke Rahm <jhr@debian.org>
Subject: Re: [gentoo-dev] paper on oss-qm project
Date: Mon, 03 May 2010 20:41:07 +0200	[thread overview]
Message-ID: <4BDF18C3.1070507@gentoo.org> (raw)
In-Reply-To: <20100502223213.GD29226@nibiru.local>

hello enrico,


interesting concept.  i'd like to comment on a few details:

 - licensing seems not be addressed, yet.
   licensing can kill everything, it needs consideration.

 - branch and tag namespaces as currently defined have a few problems:

   - versioning:

     - the A.B.C.D scheme won't be fun to gentoo, both
       due to no-letters-in-here and because of no-pre-releases.
       while at that keeping pre-releases does not seem helpful to me.

   - vendor concept:

     - uppercase vendor names look rather odd, especially with project
       names in lowercase.

     - having the vendor first makes no sense to me.
       a "package.vendor.subbranch" keeps all zlibs together,
       instead of all gentoo stuff.  if the project is about
       packages, that makes more sense to me.

     - renaming the concept to "downstream" would make it
       fit better.  gentoo is not a vendor to me.

 - with one git repo used for many packages people
   will need to know how to clone single branches only.
   most git users probably won't, you will need to teach them.
   the PDF seems a good place to do that.

hope to see you on linuxtag berlin 2010, best,




sebastian



  reply	other threads:[~2010-05-03 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02 22:32 [gentoo-dev] paper on oss-qm project Enrico Weigelt
2010-05-03 18:41 ` Sebastian Pipping [this message]
2010-05-08 20:11   ` Enrico Weigelt
2010-05-09  6:03     ` Sebastian Pipping
2010-05-17  2:19       ` Enrico Weigelt

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=4BDF18C3.1070507@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=jhr@debian.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