1 |
hello enrico, |
2 |
|
3 |
|
4 |
interesting concept. i'd like to comment on a few details: |
5 |
|
6 |
- licensing seems not be addressed, yet. |
7 |
licensing can kill everything, it needs consideration. |
8 |
|
9 |
- branch and tag namespaces as currently defined have a few problems: |
10 |
|
11 |
- versioning: |
12 |
|
13 |
- the A.B.C.D scheme won't be fun to gentoo, both |
14 |
due to no-letters-in-here and because of no-pre-releases. |
15 |
while at that keeping pre-releases does not seem helpful to me. |
16 |
|
17 |
- vendor concept: |
18 |
|
19 |
- uppercase vendor names look rather odd, especially with project |
20 |
names in lowercase. |
21 |
|
22 |
- having the vendor first makes no sense to me. |
23 |
a "package.vendor.subbranch" keeps all zlibs together, |
24 |
instead of all gentoo stuff. if the project is about |
25 |
packages, that makes more sense to me. |
26 |
|
27 |
- renaming the concept to "downstream" would make it |
28 |
fit better. gentoo is not a vendor to me. |
29 |
|
30 |
- with one git repo used for many packages people |
31 |
will need to know how to clone single branches only. |
32 |
most git users probably won't, you will need to teach them. |
33 |
the PDF seems a good place to do that. |
34 |
|
35 |
hope to see you on linuxtag berlin 2010, best, |
36 |
|
37 |
|
38 |
|
39 |
|
40 |
sebastian |