1 |
* Luis Francisco Araujo <araujo@g.o> schrieb: |
2 |
|
3 |
Hi, |
4 |
|
5 |
> Well, my idea is more focused on getting closer the developer with the |
6 |
> user, in the sense that they would be like a team (as i already said) , |
7 |
> where the developer is the official figure in the group. So, at some |
8 |
|
9 |
so far okay, but we probably suffer an different problem: |
10 |
|
11 |
The gentoo devs currently do much of the upstream's work. |
12 |
Fixing bugs or even adding new stuff which does not directly have to |
13 |
do w/ gentoo should be done exlusively by the upstream. |
14 |
|
15 |
The problem is: many projects have quite long release cycles and don't |
16 |
do separate bugfix releases. For example expat: it took very long to |
17 |
get some little makefile fixes into the release - the upstream team |
18 |
collected quite much until they did the next release (and then they |
19 |
released an direct, just bugfixing, sucessor of 1.98.x as 2.0.x ...). |
20 |
Some projects are quite strange about such things and its like fighting |
21 |
against windmills trying to change their minds. |
22 |
|
23 |
So I founded an project which maintains such bugfixes and releases |
24 |
hotfix patches against many versions of many patches and also stays |
25 |
in contact w/ upstream to get them in the tree: |
26 |
|
27 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
28 |
|
29 |
This project is meant to concentrate QM efforts more generally (instead |
30 |
of each distro for its own) and prevent double works, so many distros |
31 |
(and also self-compiling people) can benefit from it. |
32 |
|
33 |
I'd like to invite you all to join this project and use it for your |
34 |
dev works @ gentoo. |
35 |
|
36 |
For an oss-qm + gentoo connection I imagine the following workflow: |
37 |
(should also work w/ other distros this way) |
38 |
|
39 |
* gentoo user files an bug -> gets assigned to the devs. |
40 |
* dev inspects the bug whether its gentoo-specific or general |
41 |
@ general: |
42 |
* dev pushes the bug to oss-qm (files a bug there), |
43 |
* oss-qm tries to solve this bug and releases a new hotfix |
44 |
* the gentoo dev then takes in the hotfix and gives the |
45 |
patched package into the QM cycle. |
46 |
|
47 |
@ gentoo: |
48 |
* works as currently |
49 |
|
50 |
As for the suggested user contribution: |
51 |
|
52 |
The users willing to contribute simply join the oss-qm team and do |
53 |
their works there. This at least would cope evrything that's not |
54 |
gentoo specific. What remains to gentoo would be just the contents |
55 |
of the ebuild file (ie. useflags and dependencies okay, etc). |
56 |
|
57 |
At the moment some ebuilds contain much logic for doing the actual |
58 |
build, ie. generating makefiles, etc. This should go completely to |
59 |
oss-qm - the (hotfixed) packages should all supply one of the semi- |
60 |
standard interfaces like autoconf-style ./configure, package imports |
61 |
should be done entirely via pkg-config, etc. |
62 |
|
63 |
|
64 |
In the last few days I did much of such fixing works, ie. on mpd and |
65 |
libao, mainly fixing configure.in + makefiles. Some of those works |
66 |
are currently hanging on the devs feet, but shouldn't. The gentoo devs |
67 |
should only have to take some (maybe hotfixed) package, pull it through |
68 |
the QM cycle and look if its good enough to get it into the tree. |
69 |
|
70 |
|
71 |
cu |
72 |
-- |
73 |
--------------------------------------------------------------------- |
74 |
Enrico Weigelt == metux IT service - http://www.metux.de/ |
75 |
--------------------------------------------------------------------- |
76 |
Please visit the OpenSource QM Taskforce: |
77 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
78 |
Patches / Fixes for a lot dozens of packages in dozens of versions: |
79 |
http://patches.metux.de/ |
80 |
--------------------------------------------------------------------- |
81 |
-- |
82 |
gentoo-dev@g.o mailing list |