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