threads / discuss / 45026

Re: git-scm.com status report

Subject: Re: git-scm.com status report

## tl;dr

4 messages between Feb 2, 2017 and Feb 20, 2017.

replies: 3people: 2as markdown or json

Samuel Lijin· Feb 2, 2017, 22:51 UTC · lore

For anyone interested, this thread is on the HN front page right now[0].

There's one suggestion in particular that stands out to me - shifting to Digital Ocean[1], which for $240/mo offers wayyyy more than what it sounds like the current Heroku costs are.

[0] https://news.ycombinator.com/item?id=13554065 [1] https://news.ycombinator.com/item?id=13554632

On Thu, Feb 2, 2017 at 4:01 PM, pedro rijo <pedrorijo91@gmail.com> wrote:

Show 13 quoted lines

> Hey,
>
> While I’m not experienced with Rails apps, I would like to give my
> contribution to the Git project. I could help doing some kind of triage,
> removing abusing PRs/issues (like
> https://github.com/git/git-scm.com/pull/557), looking for typos and other
> tasks that wouldn’t require a lot of RoR knowledge to get start. Also,
> completely free and available to start digging into the RoR stuff of course!
>
> If you are interested, just let me know :)
>
> Thanks,
> Pedro Rijo

Jeff King· Feb 3, 2017, 12:08 UTC · lore

On Thu, Feb 02, 2017 at 10:01:45PM +0000, pedro rijo wrote:

Show 8 quoted lines

> While I’m not experienced with Rails apps, I would like to give my
> contribution to the Git project. I could help doing some kind of
> triage, removing abusing PRs/issues (like
> https://github.com/git/git-scm.com/pull/557
> <https://github.com/git/git-scm.com/pull/557>), looking for typos and
> other tasks that wouldn’t require a lot of RoR knowledge to get start.
> Also, completely free and available to start digging into the RoR
> stuff of course!

Thanks! I think a good first step is just to start watching the repository and jump in on issues where you think you can contribute.

Clicking "close" or "merge" on an issue is something only I can do for now, but having a group of people reviewing and responding to issues and PRs is a big help (so I _can_ just click those buttons). And then over time hopefully we can grow a stable of reviewers, and hand out repo privileges to the active ones.

-Peff

Jeff King· Feb 3, 2017, 22:24 UTC · lore

On Fri, Feb 03, 2017 at 09:23:33PM +0000, pedro rijo wrote:

Show 6 quoted lines

> Seems a good idea. I will start by going through some old prs/issues to
> look for trash. If I do find some like the one I referred I will let you
> know by mentioning you. After that I will have a look at simpler issues/prs.
> 
> Let me know if you do agree (or you recommend another workflow) so that I
> can start looking at it this weekend :)

That sounds perfect. Thanks!

-Peff

Jeff King· Feb 20, 2017, 07:53 UTC · lore

On Sat, Feb 18, 2017 at 10:27:51PM +0000, pedro rijo wrote:

> I would say everyone did an amazing job, closing more than 150 old issues
> in a single week! I think the amount of issues is finally manageable (40
> issues currently).

Yes, thank you to all who have been helping. But especially you and Samuel, who obviously spent a lot of time sifting through old issues.

> And if you agree, I would like to start looking at old PRs (some will
> probably don't make sense anymore), and will start reviewing them as soon
> as I have the time to setup the RoR app on my machine so that I can
> understand and see the changes introduced on the PRs.

Sounds good.

>  Many PRs seem to introduce small and innocent changes, but I always like
> to run the code to see :)

Yeah, many of the display-oriented changes are pretty obvious from reading the code, but I have caught a couple of regressions just by running the PRs and making sure the rendered result is sane.

-Peff