| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
Having a GitHub presence is arguably advantageous to free software |
| 5 |
projects because of its user community. It furthermore invites the |
| 6 |
whole GitHub generation git users (i.e. people who use the GitHub |
| 7 |
interface (pull requests in particular) more than they use git |
| 8 |
directly) to contribute to Portage in a (to them) nicer way. |
| 9 |
|
| 10 |
Zach agreed with my idea, and put Portage up[0]. However, Zach is not |
| 11 |
available for the time being, nor the foreseeable future. One of use |
| 12 |
should put Portage back up on GitHub. |
| 13 |
|
| 14 |
I would be happy to do it myself, and maintain this repository. All |
| 15 |
that it takes is syncing with upstream Portage every now and then |
| 16 |
(maybe daily). I could post relevant pull requests here for review, or |
| 17 |
add you guys to the repository so that you could review it (I know |
| 18 |
Mike is on GitHub, and so are probably a lot of you guys) and merge |
| 19 |
it, and push it upstream. |
| 20 |
|
| 21 |
If you guys don't want *me* to do this, then that is understandable. |
| 22 |
After all, I am not a project member (but a mere contributor). I still |
| 23 |
strongly suggest putting Portage on GitHub. It doesn't really matter |
| 24 |
*who* does it. |
| 25 |
|
| 26 |
[0] <https://github.com/zmedico/portage> |
| 27 |
- -- |
| 28 |
Alexander |
| 29 |
alexander@××××××.net |
| 30 |
http://plaimi.net/~alexander |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 34 |
|
| 35 |
iF4EAREIAAYFAlLatm8ACgkQRtClrXBQc7XuOwD+MLw+h66xP1Y02G1z37BU5e56 |
| 36 |
Q5YcWv8keHSm1gKrznEBALD6ieVnMZ2VzsRvFt/LYg+RPUeyhovGJvwUUEnC6kNi |
| 37 |
=1+ju |
| 38 |
-----END PGP SIGNATURE----- |
Archives