<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">The real hint is that "the number of contributions will go up". That's<br>
a noble goal and I think it's at the heart of this proposal.<br></blockquote><div><br></div><div>It's not. What's at the heart of my proposal is that `arc` sucks. Most of those quotes I posted are from regular contributors (here's another one: "arcanist kinda makes stuff even more confusing than Git by itself"). Newcomers will give it their best shot, thinking it's just another thing they need to learn, thinking it's their fault for running into problems, thinking they'll get the hang of it eventually. Except they won't, or at least I haven't, after using it for over a year.</div><div><br></div><div>Maybe the fundamental problem with Phabricator is that it doesn't understand Git well, and the problems I posted on <a href="https://ghc.haskell.org/trac/ghc/wiki/WhyNotPhabricator">https://ghc.haskell.org/trac/ghc/wiki/WhyNotPhabricator</a> are just symptoms of it. I'm having trouble putting this into words though (something about branches and submodules). Perhaps someone else can?<br></div><div><br></div><div><div>In my opinion it's is a waste of our time trying to improve `arc` (it is 34000 lines of PHP btw + another 70000 LOC for libphutil), when `pull requests` are an obvious alternative that most of the Haskell community already uses.</div></div><div><br></div><div>When you're going to require contributors to use a non-standard tool to get patches to your code review system, it better just work. `arc` is clearly failing us here, and I'm saying enough is enough.</div><div><br></div><div>I need to think about your other points. Thank you for the thorough reply.</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Here's the meat of it question: what is the cost of achieving this<br>
goal? That is, what amount of work is sufficient to make this goal<br>
realizable, and finally - why is GitHub *the best use of our time for<br>
achieving this?* That's one aspect of the cost - that it's the best<br>
use of the time. I feel like this is fundamentally why I always seem<br>
to never 'get' this argument, and I'm sure it's very frustrating on<br>
behalf of the people who have talked to me about it and like GitHub.<br>
But I feel like I've never gotten a straight answer for GHC.<br>
<br>
If the goal is actually "make more people contribute", that's pretty<br>
broad. I can make that very easy: give everyone who ever submits a<br>
patch push access. This is a legitimate way to run large projects that<br>
has worked. People will almost certainly be more willing to commit,<br>
especially when overhead on patch submission is reduced so much. Why<br>
not just do that instead? It's not like we even mandate code review,<br>
although we could. You could reasonably trust CI to catch and revert<br>
things a lot of the time for people who commit directly to master. We<br>
all do it sometimes.<br>
<br>
I'm being serious about this. I can start doing that tomorrow because<br>
the *cost is low*, both now and reasonably speaking into some<br>
foreseeable future. It is one of many solutions to raw heart of the<br>
proposal. GitHub is not a low cost move, but also, it is a *long term<br>
cost* because of the technical deficiencies it won't aim to address<br>
(merge commits are ugly, branch reviews are weak, ticket/PR namespace<br>
overlaps with Trac, etc etc) or that we'll have to work around.<br>
<br>
That means that if we want GitHub to fix the "give us more<br>
contributors" problem, and it has a high cost, it not only has _to fix<br>
the problem_, it also has to do that well enough to offset its cost. I<br>
don't think it's clear that is the case right now, among a lot of<br>
other solutions.<br>
<br>
I don't think the root issue is "We _need_ GitHub to get more<br>
contributors". It sounds like the complaint is more "I don't like how<br>
Phabricator works right now". That's an important distinction, because<br>
the latter is not only more specific, it's more actionable:<br>
<br>
- Things like Arcanist can be tracked as a Git submodule. There is<br>
little to no pain in this, it's low cost, and it can always be<br>
synchronized with Phabricator. This eliminates the "Must clone<br>
arcanist" and "need to upgrade arcanist" points.<br>
<br>
- Similarly when Phabricator sometimes kills a lot of builds, it's<br>
because I do an upgrade. That's mostly an error on my part and I can<br>
simply schedule upgrades regularly, barring hotfixes or somesuch. That<br>
should basically eliminate these. The other build issues are from<br>
picking the wrong base commit from the revision, I think, which I<br>
believe should be fixable upstream (I need to get a solid example of<br>
one that isn't a mega ultra patch.)<br>
<br>
- If Harbormaster is not building dependent patches as mentioned in<br>
WhyNotPhabricator, that is a bug, and I have not been aware of it.<br>
Please make me aware of it so I can file bugs! I seriously don't look<br>
at _every_ patch, I need to know this. That could have probably been<br>
fixed ASAP otherwise.<br>
<br>
- We can get rid of the awkwardness of squashes etc by using<br>
Phabricator's "immutable" history, although it introduces merge<br>
commits. Whether this is acceptable is up to debate (I dislike merge<br>
commits, but could live with it).<br>
<br>
- I do not understand point #3, about answering questions. Here's<br>
the reality: every single one of those cases is *almost always an<br>
error*. That's not a joke. Forgetting to commit a file, amending<br>
changes in the working tree, and specifying a reviewer are all total<br>
errors as it stands today. Why is this a minus? It catches a useful<br>
class of 'interaction bugs'. If it's because sometimes Phabricator<br>
yells about build arifacts in the tree, those should be .gitignore'd.<br>
If it's because you have to 'git stash' sometimes, this is fairly<br>
trivial IMO. Finally, specifying reviewers IS inconvenient, but<br>
currently needed. We could easily assign a '#reviewers' tag that would<br>
add default reviewers.<br>
- In the future, Phabricator will hopefully be able to<br>
automatically assign the right reviewers to every single incoming<br>
patch, based on the source file paths in the tree, using the Owners<br>
tool. Technically, we could do that today if we wanted, it's just a<br>
little more effort to add more Herald rules. This will be far, far<br>
more robust than anything GitHub can offer, and eliminates point #3.<br>
<br>
- Styling, linting etc errors being included, because reviews are<br>
hard to create: This is tangential IMO. We need to just bite the<br>
bullet on this and settle on some lint and coding styles, and apply<br>
them to the tree uniformly. The reality is *nobody ever does style<br>
changes on their own*, and they are always accompanied by a diff, and<br>
they always have to redo the work of pulling them out, Phab or not.<br>
Literally 99% of the time we ask for this, it happens this way.<br>
Perhaps instead we should just eliminate this class of work by just<br>
running linters over all of the source code at once, and being happy<br>
with it.<br>
<br>
Doing this in fact has other benefits: like `arc lint` will always<br>
_correctly_ report when linting errors are violated. And we can reject<br>
patches that violate them, because they will always be accurate.<br>
<br>
- As for some of the quotes, some of them are funny, but the real<br>
message lies in the context. :) In particular, there have been several<br>
cases (such as the DWARF work) where the idea was "write 30 commits<br>
and put them on Phabricator". News flash: *this is bad*, no matter<br>
whether you're using Phabricator or not, because it makes reviewing<br>
the whole thing immensely difficult from a reviewer perspective. The<br>
point here is that we can clear this up by being more communicative<br>
about what we expect of authors of large patches, and communicating<br>
your intent ASAP so we can get patches in as fast as possible. Writing<br>
a patch is the easiest part of the work.<br>
<br>
And more:<br>
<br>
- Clean up the documentation, it's a mess. It feels nice that<br>
everything has clear, lucid explanations on the wiki, but the wiki is<br>
ridiculously massive and we have a tendancy for 'link creep' where we<br>
spread things out. The contributors docs could probably stand to be<br>
streamlined. We would have to do this anyway, moving to GitHub or not.<br>
<br>
- Improve the homepage, directly linking to this aforementioned page.<br>
<br>
- Make it clear what we expect of contributors. I feel like a lot of<br>
this could be explained by having a 5 minute drive-by guide for<br>
patches, and then a longer 10-minute guide about A) How to style<br>
things, B) How to format your patches if you're going to contribute<br>
regularly, C) Why it is this way, and D) finally links to all the<br>
other things you need to know. People going into Phabricator expecting<br>
it to behave like GitHub is a problem (more a cultural problem IMO but<br>
that's another story), and if this can't be directly fixed, the best<br>
thing to do is make it clear why it isn't.<br>
<br>
Those are just some of the things OTTOMH, but this email is already<br>
way too long. This is what I mean though: fixing most of these is<br>
going to have *seriously smaller cost* than moving to GitHub. It does<br>
not account for "The GitHub factor" of people contributing "just<br>
because it's on GitHub", but again, that value has to outweigh the<br>
other costs. I'm not seriously convinced it does.<br>
<br>
I know it's work to fix these things. But GitHub doesn't really<br>
magically make a lot of our needs go away, and it's not going to<br>
magically fix things like style or lint errors, the fact Travis-CI is<br>
still pretty insufficient for us in the long term (and Harbormaster is<br>
faster, on our own hardware, too), or that it will cause needlessly<br>
higher amounts of spam through Trac and GitHub itself. I don't think<br>
settling on it as - what seems to be - a first resort, is a really<br>
good idea.<br>
<div class=""><div class="h5"><br>
<br>
On Wed, Sep 2, 2015 at 4:09 PM, Niklas Hambüchen <<a href="mailto:mail@nh2.me">mail@nh2.me</a>> wrote:<br>
> On 02/09/15 22:42, Kosyrev Serge wrote:<br>
>> As a wild idea -- did anyone look at /Gitlab/ instead?<br>
><br>
> Hi, yes. It does not currently have a sufficient review functionality<br>
> (cannot handle multiple revisions easily).<br>
><br>
> On 02/09/15 20:51, Simon Marlow wrote:<br>
>> It might feel better<br>
>> for the author, but discovering what changed between two branches of<br>
>> multiple commits on github is almost impossible.<br>
><br>
> I disagree with the first part of this: When the UI of the review tool<br>
> is good, it is easy to follow. But there's no open-source implementation<br>
> of that around.<br>
><br>
> I agree that it is not easy to follow on Github.<br>
> _______________________________________________<br>
> ghc-devs mailing list<br>
> <a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
> <a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
><br>
<br>
<br>
<br>
</div></div><span class=""><font color="#888888">--<br>
Regards,<br>
<br>
Austin Seipp, Haskell Consultant<br>
Well-Typed LLP, <a href="http://www.well-typed.com/" rel="noreferrer" target="_blank">http://www.well-typed.com/</a><br>
</font></span><div class=""><div class="h5">_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</div></div></blockquote></div><br></div></div>