1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 11/08/2015 16:32, Michał Górny wrote: |
5 |
> Hello, everyone. |
6 |
> |
7 |
> Now that we're officially on git and can officially use pull |
8 |
> requests to provide rapid community interaction, it'd be convenient |
9 |
> to have a little better framework for pinging package maintainers. |
10 |
> |
11 |
> With the unofficial mirror/pull request project, I was either |
12 |
> looking for project member GitHub accounts and pinging found |
13 |
> project members by name, or talking to them directly on IRC. |
14 |
> However, with the growth in number of pull requests this will |
15 |
> become more and more inconvenient. Therefore, I think it's time to |
16 |
> be able to mirror teams willing to work with GitHub community there |
17 |
> for easier 'pings'. |
18 |
> |
19 |
|
20 |
I like the idea, sounds very handy |
21 |
|
22 |
> I have two ideas right now: |
23 |
> |
24 |
> 1. creating GitHub Gentoo project teams corresponding to willing |
25 |
> Gentoo teams, |
26 |
> |
27 |
> 2. preparing lists of GitHub usernames on project wiki pages. |
28 |
> |
29 |
> Solution 1. is cleaner. In this case, we create GitHub teams under |
30 |
> the Gentoo projects, and add appropriate Gentoo developers having |
31 |
> GitHub accounts to the teams. Then, in PRs we can just ping the |
32 |
> whole team like @Gentoo/Qt or like. |
33 |
> |
34 |
|
35 |
+1 imho, clean & simple, only team and ppl willing to participate can |
36 |
get there |
37 |
|
38 |
> Solution 2. avoids adding any GitHub teams. In this case, in team |
39 |
> wiki page we collect team member usernames like "@Pesa, |
40 |
> @kensington, ..." so we could copy-paste it to pull requests. We |
41 |
> still require extra effort when 'assigning' PRs but at least I |
42 |
> don't have to lookup the same people over and over again. |
43 |
> |
44 |
> With some Wiki people help, we could even implement updating |
45 |
> GitHub teams automatically following Wiki member changes. |
46 |
> |
47 |
> Your thoughts? |
48 |
> |
49 |
-----BEGIN PGP SIGNATURE----- |
50 |
Version: GnuPG v2 |
51 |
|
52 |
iF4EAREIAAYFAlXKCqsACgkQKiQSS7ZY+hNd9AD9FBXc16nF9sp2Xk1gBpXsduGt |
53 |
a2+f1tHSMN9ChSrCBM4A/Ao1nCfMNBEaI9WYBUOQ0Cti5hkjM9X66sMlnszsBahP |
54 |
=GS6Q |
55 |
-----END PGP SIGNATURE----- |