On 26.08.2017, at 14:47, Lou DeGenaro <[email protected]> wrote: > > I applaud your taking the initiative towards improvement. I did have > experience perhaps 1.5 years ago using GitHub for another non-Apache > project. My view was negative, though I could not now recite the precise > issues encountered. My best recollection is that the happy paths worked > fine, but when mistakes were made or problems were encountered recovery was > often difficult and frustrating. If I am the only objector then I vote 0, > but my gut votes -1.
Do you remember if your experiences were related more to git or to github? My problems were always mainly related to (not) understanding the distributed approach - e.g. why feature branches are a good thing, when merging branches is a good thing and in which direction vs. cherry picking or rebasing, when doing a force push is acceptable and when not, etc. > With respect to speculation, my sense is that switching to GitHub will not > open the floodgates to contributions. Well, maybe not floodgates, but I can tell for DKPro Core that we basically never had contributions back on Google Code (when it still existed) and we started getting contributions once we had moved to GitHub. Not as if people were coming in large numbers, but they were coming. More important then more contributors is IMHO how much effort it is to incorporate those changes / patches come in. It is a bad thing when patches sit around in Jira forever. The UI/process that GitHub provides to review, discuss and test incoming patches feels much smoother and natural to me than fetching patches, testing them, discussing via Jira, possibly by copy/pasting code snippets or line number references in comments, etc. I'd almost never do that on Jira because it is too cumbersome. Result: it is not fun to get patches in which - not for the maintainers and eventually also not for the contributors because their patches sit there forever. -- Richard
