1 |
Am Dienstag, den 09.06.2009, 21:00 -0500 schrieb Doug Goldstein: |
2 |
> On Thu, Jun 4, 2009 at 5:26 PM, Tiziano Müller<dev-zero@g.o> wrote: |
3 |
> > This is your friendly reminder! Same bat time (typically the 2nd & 4th |
4 |
> > Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @ |
5 |
> > irc.freenode.net) ! |
6 |
> > |
7 |
> > If you have something you'd wish for us to chat about, maybe even vote |
8 |
> > on, let us know! Simply reply to this e-mail for the whole Gentoo dev |
9 |
> > list to see. |
10 |
> > |
11 |
> > For more info on the Gentoo Council, feel free to browse our homepage: |
12 |
> > http://www.gentoo.org/proj/en/council/ |
13 |
> > |
14 |
> > |
15 |
> > Following is the preliminary meeting agenda. |
16 |
> > |
17 |
> > |
18 |
> > EAPI 3: Short discussion of the progress |
19 |
> > ---------------------------------------- |
20 |
> > |
21 |
> > zmedico will provide an update on the progress of the implementation. Short |
22 |
> > discussion of problems and implementation decisions if needed. |
23 |
> |
24 |
> I'd say let's involve all the package manager maintainer groups. Each |
25 |
> packager manager can have a rep speak on their behalf and we can plow |
26 |
> through this topic fairly quickly. |
27 |
Sure, one prominent maintainer of an alternative package manager is |
28 |
usually around during meetings. But since the more complex features are |
29 |
already implemented in kdebuild and paludis supported kdebuild, we're |
30 |
really waiting for support in our official package manager. I don't know |
31 |
about the state of pkgcore though. |
32 |
|
33 |
> > |
34 |
> > |
35 |
> > Default ACCEPT_LICENSE |
36 |
> > ---------------------- |
37 |
> > Goal: A possible default value for ACCEPT_LICENSE has been proposed. Decide |
38 |
> > whether that's ok. What happens to the X11 license files (one for each app)? |
39 |
> |
40 |
> In virtually all situations MIT has been used for the X11 license, |
41 |
> which should be sufficient enough for us. The previously proposed |
42 |
> defaults for ACCEPT_LICENSE all looked reasonable to me. |
43 |
> |
44 |
> > |
45 |
> > |
46 |
> > Bash-4 in EAPI-3 |
47 |
> > ---------------- |
48 |
> > Goal: A request has been made to allow bash-4.0 features in EAPI-3. Decide |
49 |
> > first whether or not to open the EAPI-3 feature list at all. |
50 |
> |
51 |
> No. bash-4 has seen some regressions and some oddities. 24 patches in |
52 |
> and its starting to seem remotely sane, except the problem is it does |
53 |
> not have wide scale adoption yet. I expect to see a lot of patches |
54 |
> coming. Additionally, EAPI-3 has been an ongoing thing long enough. |
55 |
> The more we keep pushing this off the more items should be shuffled |
56 |
> in. We decided what EAPI-3 was a long time back. Stick with that. |
57 |
> EAPI-4 can be the bases of bash-4 support. |
58 |
Well, that's my opinion as well. But since there was an official request |
59 |
for this we have to decide on it. |
60 |
|
61 |
> |
62 |
> > |
63 |
> > |
64 |
> > Define EAPI development/deployment cycles |
65 |
> > ----------------------------------------- |
66 |
> > |
67 |
> > Goal: Start discussion about EAPI development/deployment. For example: |
68 |
> > Collect problems of eapi introductions in the past, like reverting |
69 |
> > ebuilds to former eapis to get them stable, not waiting for the pm |
70 |
> > support a certain eapi before requesting stable keywords for ebuilds |
71 |
> > using the new eapi, .... Collect problems of EAPI development like |
72 |
> > feature-freeze, late feature removals (due to implementation problems). |
73 |
> > Eventually develop a lightweight EAPI development model. |
74 |
> |
75 |
> This is still something being discussed on the mailing lists and |
76 |
> belongs there. Not in a council meeting. |
77 |
Which mailinglist? Since council people have now pretty good experience |
78 |
on what needs to be done to get an eapi ready I think it is the right |
79 |
place to start the discussion. |
80 |
|
81 |
> |
82 |
> If I am AFK during the council meeting due to being in a skiff, I have |
83 |
> designated tanderson/gentoofan23 as my proxy. |
84 |
> |
85 |
noted. |
86 |
|
87 |
|
88 |
-- |
89 |
Tiziano Müller |
90 |
Gentoo Linux Developer, Council Member |
91 |
Areas of responsibility: |
92 |
Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor |
93 |
E-Mail : dev-zero@g.o |
94 |
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 |