From: Jeff King <peff@peff.net>
To: pedro rijo <pedrorijo91@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: hacktoberfest
Date: Thu, 28 Sep 2017 17:19:00 -0400 [thread overview]
Message-ID: <20170928211859.uw7dep6gypsifivy@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPMsMoBK+EQZQx4FUs_EqN+BE+93-mtu9kzViqQ6B=LUOFESbw@mail.gmail.com>
On Wed, Sep 27, 2017 at 11:05:49PM +0100, pedro rijo wrote:
> While the git repository itself is not hosted under GitHub, the Pro
> Git book, git for Windows, and git-scm website (at least) projects
> are, and could use this movement to get some more contributions, and
> eventually more maintainers (at least git-scm website had some
> maintainers problem some time ago).
>
> I've been helping on the git-scm repository (mostly filtering issues
> and PRs), and I know there are still some issues which need to be
> addressed. If the remaining maintainers agree, we could filter and
> provide more instructions to some easy (or not so easy) issues, adding
> the 'hacktoberfest' label and try to use this movement to solve some
> problems
I'd love it if more people wanted to contribute to the git-scm
repository. I think one can probably find some low-hanging fruit by
looking at the open issues list (though I'd be happy, too, if people
with bug or feature suggestions opened new issues).
Here are a couple small-to-moderate bugs that have been languishing:
https://github.com/git/git-scm.com/issues/701
https://github.com/git/git-scm.com/issues/987
https://github.com/git/git-scm.com/issues/994
-Peff
next prev parent reply other threads:[~2017-09-28 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 22:05 hacktoberfest pedro rijo
2017-09-28 21:19 ` Jeff King [this message]
2017-10-04 21:20 ` hacktoberfest pedro rijo
2017-10-05 11:34 ` hacktoberfest Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170928211859.uw7dep6gypsifivy@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pedrorijo91@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).