From: Alexander Berntsen <alexander@plaimi.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] GitHub presence
Date: Sat, 18 Jan 2014 18:14:23 +0100 [thread overview]
Message-ID: <52DAB66F.4030703@plaimi.net> (raw)
-----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
alexander@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-----
next reply other threads:[~2014-01-18 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 17:14 Alexander Berntsen [this message]
2014-01-18 21:52 ` [gentoo-portage-dev] GitHub presence Robin H. Johnson
2014-01-18 23:25 ` Alexander Berntsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52DAB66F.4030703@plaimi.net \
--to=alexander@plaimi.net \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox