From: pedro rijo <pedrorijo91@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: hacktoberfest
Date: Wed, 4 Oct 2017 22:20:53 +0100 [thread overview]
Message-ID: <CAPMsMoCCE=tux5Pi=eC8_YtFb93TYOgrZdOS9CXnuLyRr+1v=w@mail.gmail.com> (raw)
In-Reply-To: <20170928211859.uw7dep6gypsifivy@sigill.intra.peff.net>
seems my last answer was blocked due to HTML :(
here's the answer: Seems a nice start yes. I've been on vacations, but
next week I will go trough the current issues and add the
hacktoberfest label to some issues if you agree.
I went through the open issues a few moments ago. Some were closed
(solved or not applicable anymore), and some got an hacktoberfest
label, hoping new contributors pop up. Feel free to have a look and
add new issues to the label, as well as remove some of those I thought
it could be a good fit. There are easy issue, and some not so easy
(not very hard, but a bit more work) probably.
Issues labeled:
https://github.com/git/git-scm.com/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest
Thanks,
Pedro
2017-09-28 22:19 GMT+01:00 Jeff King <peff@peff.net>:
> 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
--
Obrigado,
Pedro Rijo
next prev parent reply other threads:[~2017-10-04 21:25 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 ` hacktoberfest Jeff King
2017-10-04 21:20 ` pedro rijo [this message]
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='CAPMsMoCCE=tux5Pi=eC8_YtFb93TYOgrZdOS9CXnuLyRr+1v=w@mail.gmail.com' \
--to=pedrorijo91@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).