YES. In fact, I volunteer for whatever would help with this initiative. I know reviewing patches is probably the most time consuming bit, so perhaps if the incoming submissions were prioritized by the submissions moderator, and then assigned across to a patch reviewer (or a few of them) who could check/test/fix/sanitycheck/reroll/verify or whatever is necessary, and then assign it along to someone with commit access, then the busy factor for the few with commit access could be reduced to simply applying the patch and doing the commit, as the "heavy lifting" would already be done.
I personally have many patches waiting for submission as some of them rely on getting prerequisite patches applied first - such as my serial flash patch for brcm-2.4 needs to be applied before I can submit the new diag detection patches for a specific sflash equipped board. I am sure there are others who are in a similar position, or don't bother submitting because of the inherent headaches, or they are less experienced and take the lack of response as a silent commentary on how bad/incorrect/useless their patch submission was or whatever other conclusions they could jump to, and become disinterested in helping or think they are not good enough to help. The submissions moderator could respond to the submitter with a simple "thanks, your submission has been accepted and entered in to the pipeline for review" message and the reviewer(s) could send another status message that the patch has passed the review and should be applied soon, then the "black hole" factor goes away along with the reminder/ping emails from submitters who are at various levels of frustration, wondering what's going on inside the submission machine black box. On Sat, 2010-01-16 at 15:14 +0100, bud.d...@suisse.org wrote: > Just a reminder. As usual :'( > see bottom of the message > > I understand you guys are busy, but the lack of feedback in the list can > be frustrating to contributors. It definitely is sometimes for me ;) > > Is there a list of open patches? Wouldn't it make sense to have one > listed by priority, by which they also get overlooked by someone > dedicated? Something like > > Recent List of patches and actions > > Prio, What > > High > 1 release 8.09.3 > 2 patch security issue foo > 3 patch something important > > Medium > 1 patch bump version of package x, maillist link > 2 patch missing config file package xy, maillist link > > Low > 1 feature request x, ticketno 3456 > 2 feature request y, ticketno 1234 > > Of course this has to be moderated. But one dedicated moderator and one > developer working the list could be a start. > > .. bud > > > -------- Original Message -------- > Subject: [OpenWrt-Devel] broadcom-mmc replacement broadcom-sdhc package > Date: Fri, 11 Dec 2009 14:23:46 +0100 > From: bud.d...@suisse.org > Reply-To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > To: OpenWrt Development List <openwrt-devel@lists.openwrt.org> > > As announced the new package broadcom-sdhc. I created a enhancement > ticket here > https://dev.openwrt.org/ticket/6343 > Please add it to trunk and remove broadcom-mmc, which is then obsolete. > > Thanks bud > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
