Evan Huus wrote:
>
>> On Aug 10, 2014, at 21:43, Ed Beroset wrote:
>> I'm not sure it matters sufficiently that it could or should cause course alteration, but as one who has contributed modestly to Wireshark before the move to gerrit, but not since then, I'd have to say that for me, the setup/registration/configuration/etc. has definitely impeded further contributions. The new process is something that I haven't really gotten around to trying to figure out. I'm not saying it's the wrong choice, but it's just that much more effort to even *submit* a patch, that I suspect that a lot of would-be contributors might find the threshold too high. Maybe updating documentation could help. Right now, if you go to the main "develop" page https://www.wireshark.org/develop.html and click on the link under "code review site" you get to https://code.wireshark.org/review/#/q/status:open,n,z which offers no clue at all as to how one should actually register. I'm sure I could figure it out, and I'm sure many have. It's just that I'd really just like to be able to contribute patches without having to do quite so much exploration. Maybe I'm just lazy, but it might be nice if the barrier to useful contribution were lowered just a bit.
>
>There is http://wiki.wireshark.org/Development/SubmittingPatches which we should definitely do a better job of advertising. That should walk you through the major setup steps.
>
>Where would be a more useful/obvious place to include that information?
If there were a link to that page, perhaps under the words "contribute change", on https://www.wireshark.org/develop.html I think it would be a little easier to find. Also, the "sign in" step seems to have been the source of most of the questions I've seen on this list, so maybe a bit of expansion on the options there and how to effect them would be useful. I keep thinking that I'll write it up myself once I figure it out, but hadn't gotten around to doing either yet. :(
Ed
