On Tue, Jul 07, 2015 at 10:42:49PM +0200, Jiri Kosina wrote: > I think it'd be useful to have a session where maintainers could come up > with feature / improvement requests for kernel.org infrastructure and have > a subsequent discussion about whether they would be generally useful. I suggest people just email users@linux.kernel.org. :) I've always solicited such conversations, but in my previous experience these tend to fall into two categories: 1. "Here's a minor suggestion that could be kinda cool, whenever you have some time." 2. "Here's a radical idea that would require a park of 1,000 various hardware systems and a dedicated staff of 10 people." There doesn't appear to be a lot that falls between these two categories. This is not to say that #2 is not possible, it's just that we have to operate within LF budget constraints and people never tend to follow such grand requests with "and here's my $EMPLOYER who's happy to fund this initiative." If you do happen to be in such a position, then I'll be happy to get you in touch with the Collab Projects management team. > Let me start with my personal wish: > > I personally would very welcome a facility that'd send out an e-mail if a > new commit is pushed to a git.kernel.org repo branch (sort of what tip-bot > and akpm's scripts are doing these days) to automatically notify the patch > author that the patch has been merged and pushed out. We have the following script running on torvalds/linux.git: http://ur1.ca/n2iof It has two downsides: 1. It sends an email per each commit, which tends to thrash the lists (e.g. see https://marc.info/?l=git-commits-head where Linus's tree goes) 2. It doesn't fork into background while doing that, so you have to wait for it to finish sending the emails. If that's fine with you all, I can enable this for other repos as well. All I'd need would be the destination list address. > Suggested attendance: Konstantin, maintainers :) I'll be at the summit. Best, -- Konstantin Ryabitsev Linux Foundation Collab Projects Montréal, Québec