| Re: [jetty-users] Github Hosting of Jetty |
To me this is the most reasoned and pragmatic approach. It seems very prudent to tweak the things that aren’t great about the current setup rather than chase after the latest fad. Github isn’t without its own tradeoffs and warts and the grass isn’t always greener, as they say. Eric From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Greg Wilkins All, Experience from those moves suggests to me that moving can cause more disruption than the benefits that it gains. I'm very content with the project being developed under the Eclipse Foundation, it has provided an umbrella organisation that has not been too intrusive in the technical development of the project, has imposed some reasonable IP due diligence and provides hosting resources that while not start of the art are capable, maintained and not far from the state of the art. So I've got zero interest in moving the project away from the eclipse foundation from an organisational point of view. I am however keen to accept contributions in whatever form they are given and github pull requests are a popular way to make contributions, and are well supported with collaborative tools. The project has already received 21 pull request on the github mirror and another 5 on a fork of the mirror. In the past, we have simply rejected these PRs with a message asking for patch contribution. However, it is already possible for us to directly pull from these pull requests, so long as the contributor has signed an eclipse CLA and referred to the PR in a bugzilla. So going forward, I suggest that at the minimum we respond to PRs with a request for a CLA and bugzilla, rather than asking for the contribution to be reformed. So my question is, will moving the canonical repository to github make this process any easier? Maybe a little bit, but not so as the contributor will notice. They will still need to sign a CLA and open a bugzilla. The difference is that the committer processing the PR will be able to click a button to get the merge rather than use command line git commands. I think that we should look at this in stages. The first stage is to get some more control over the PRs that are raised for the current github mirror. We should be able to put suitable CONTRIBUTING file in place that describes the CLA and bugzilla requirements. We should be able to open/close the PRs as well as comment on them. I think we can then operate in that mode for a while and get some actual PRs that we can process. The contributor should not see any difference in the process. Once we have experience with that path and the processing of PRs, then we can consider if it is worthwhile moving the canonical repository to make the commiters task a little bit easier. On 12 September 2014 01:52, Tamás Cservenák <tamas@xxxxxxxxxxxxx> wrote: +1 On Wed, Sep 10, 2014 at 4:05 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote: https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#GitHub_Hooks jetty-users mailing list
Greg Wilkins <gregw@xxxxxxxxxxx> |