Hi Peter, Le Thu, 23 Jul 2015 23:55:34 +0200, Peter Stuge <[email protected]> a écrit :
> David Ung wrote: > > This doesn't sound very encouraging for the project in general. :-( > > It's essentially the contributor's task to make it effortless for > maintainers to accept contributions. Maybe not effortless but as easy as reasonable, certainly. Here, IIUC, the main factor is the time needed to analyze the patch(es). OTOH, it should not be burdensome to contribute. Ok, that's anecdotal, but still: I've tried to register to the OpenOCD Gerrit, and gave up for now because it wants me to register through a GitHub, Google, Launchpad, or Yahoo! account, or through Open ID, and did not leave me any visible option to just register with the e-mail and password of my choice. *That*, for instance, is a burden, as these accounts are not related to, an not needed for, contributing to OpenOCD. IMO, the amount of unrelated-to-OpenOCD effort that a contributor needs to endure in order to submit a patch should be limited to providing a verified e-mail address to Gerrit. > That can be really difficult if contributions touch on complex issues. Since the main issue seems to be a lack of "maintainer time", then maybe a solution could be topic-specific branches (or possibly repos), managed by sub-maintainers, like there are in U-boot, as opposed to the single master branch there is now? This could bring the following benefits: - relieve the main maintainer by shifting and splitting the patch analysis and merge load over sub-maintainers; - allow persons interested in a topic to rise to 'branch owner' status, bringing their energy to their topic of interest; - allow users interested in some topic to test / use it through its topic branch before it gets merged on the master branch and later released. Some topic branches could be permanent (adding or updating scripts for interfaces, cpu or targets scripts, for instance), some could exist only for a time (aarch64 support introduction could be a candidate). Of course, not having registered on the OpenOCD Gerrit yet (since it might force me to create an ad hoc account elsewhere), I have no idea how many roles it defines or uses, and how many people there are in each role, or even if there are topic branches in Gerrit already that just don't show up in a git clone, so maybe what I'm suggesting is already internally done (in which case I'm sorry I missed that in my searches). > //Peter Amicalement, -- Albert. ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
