Gentoo Archives: gentoo-dev

From: "Marijn Schouten (hkBst)" <hkBst@g.o>
To: gentoo-dev@l.g.o
Subject: Improving developer/user communication (was Re: [gentoo-dev] net-im/pidgin protocols)
Date: Thu, 19 Jul 2007 16:39:55
Message-Id: 469F9271.9080908@gentoo.org
In Reply to: Re: [gentoo-dev] net-im/pidgin protocols by joshua jackson
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 joshua jackson wrote:
5 > Jakub Moc wrote:
6 >> Petteri Rýty napsal(a):
7 >>> Or just do it via package.use in profiles until IUSE defaults are
8 >>> implemented.
9 >>>
10 >>> Regards,
11 >>> Petteri
12 >> As noted before, they are implemented, just not allowed in the tree.
13 >> Plus, what vapier said, this info belongs to the ebuilds, not to profiles.
14 >
15 >> Wrt pidgin - seriously, what's the big issue here? Users can't use
16 >> emerge -pv output and determine what they want, or? Will we bloat the
17 >> profiles everytime someone forgets to enable a flag and goes complain
18 >> upstream about a 'missing' feature?
19 >
20 >
21 >
22 >> ----------------------------------------------------------------------
23 >
24 >> !DSPAM:469f3b40137571336712104!
25 > Honestly..this is not something to get picky over jakub. Upstream was
26 > nice and actually came and politely asked us to change the defaults to
27 > what most people would consider sane (all protocols by default). As I
28 > think most people emerging pidgin..would like to use any protocol by
29 > default..not go..hey I don't have yahoo, I should check my use flags.
30 > Which obviously hasn't happened as users pop up in #pidgin to ask why
31 > the heck there isn't a yahoo account available.
32 >
33 > This should be a nothing change to do. Its also working with upstream
34 > and maintaining some good relationships here..and or help improve them
35 > in general. That should in fact you know...be part of our goals....to
36 > improve communications between Gentoo and other projects.
37
38 Perhaps we also need to make it more clear where users can ask such
39 Gentoo-specific questions about specific packages, so they don't need to go
40 and annoy upstream. Associate an irc-channel with each package. Most packages
41 have a herd associated with them which can belong to a project which could
42 have an irc-channel where the relevant developers could be found and which can
43 put common problems in its topic. Fallback for when no appropriate irc-channel
44 can be found would be #gentoo. Currently it is usually difficult to find such
45 irc-channels or to know if there is none and that your only option is #gentoo
46 or #$upstream. It would also make it easier for users to start helping
47 developers and eventually become developers themselves, since they won't need
48 to search for a point of entry anymore.
49
50 Marijn
51 -----BEGIN PGP SIGNATURE-----
52 Version: GnuPG v2.0.5 (GNU/Linux)
53 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
54
55 iD8DBQFGn5Jxp/VmCx0OL2wRAoJlAKCzuF92/4rDf/Cty2uOMDC1mZXdBwCdEj/y
56 cOnwaXHjD8aDvJQ+XShHQ7E=
57 =dfna
58 -----END PGP SIGNATURE-----
59 --
60 gentoo-dev@g.o mailing list

Replies