Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread Val Kulkov
On 19 January 2018 at 05:19, Karl Palsson wrote: >> But I would not worry about making the lives of contributors >> easier [since they come & go]. I would worry about making the >> lives of core devs easier, since their number is rarely >> changing, and they have to put in the effort. > > An examp

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread Karl Palsson
> But I would not worry about making the lives of contributors > easier [since they come & go]. I would worry about making the > lives of core devs easier, since their number is rarely > changing, and they have to put in the effort. An example of wording you may wish to re-examine. This is exactly

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread Karl Palsson
> > I started working on a script, here is how it works. its pretty > much the same for patchwork and github with the difference that > on github we write comments and patchwork we send mails. after > 90 days we send a note saying "it stalled pleases remind folks > and help get it merged" after 12

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread Piotr Dymacz
Hi Val, On 19.01.2018 02:02, Val Kulkov wrote: On 18 January 2018 at 19:49, Alberto Bursi wrote: On 01/19/2018 01:05 AM, Val Kulkov wrote: There is more than a handful of PRs currently bit-rotting in openwrt/packages that are ready for merging, with all requested changes in place since ma

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread Alexandru Ardelean
On Fri, Jan 19, 2018 at 10:09 AM, John Crispin wrote: > > > On 19/01/18 08:55, Alexandru Ardelean wrote: >> >> On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote: >>> >>> On 18 January 2018 at 19:49, Alberto Bursi >>> wrote: On 01/19/2018 01:05 AM, Val Kulkov wrote: >

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-19 Thread John Crispin
On 19/01/18 08:55, Alexandru Ardelean wrote: On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote: On 18 January 2018 at 19:49, Alberto Bursi wrote: On 01/19/2018 01:05 AM, Val Kulkov wrote: There is more than a handful of PRs currently bit-rotting in openwrt/packages that are ready for mer

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-18 Thread Alexandru Ardelean
On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote: > On 18 January 2018 at 19:49, Alberto Bursi wrote: >> >> >> >> On 01/19/2018 01:05 AM, Val Kulkov wrote: >>> >>> There is more than a handful of PRs currently bit-rotting in >>> openwrt/packages that are ready for merging, with all requested >>>

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-18 Thread Val Kulkov
On 18 January 2018 at 19:49, Alberto Bursi wrote: > > > > On 01/19/2018 01:05 AM, Val Kulkov wrote: >> >> There is more than a handful of PRs currently bit-rotting in >> openwrt/packages that are ready for merging, with all requested >> changes in place since many months ago. Auto-closing such PRs

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-18 Thread Alberto Bursi
On 01/19/2018 01:05 AM, Val Kulkov wrote: There is more than a handful of PRs currently bit-rotting in openwrt/packages that are ready for merging, with all requested changes in place since many months ago. Auto-closing such PRs will offend the contributors who would see their effort go down th

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-18 Thread Val Kulkov
On 18 January 2018 at 03:44, Jo-Philipp Wich wrote: > Hi John, Alex, > > I have no problem with closing / autorejecting open tickets in patchwork > as long as they somehow remain available for future reference. > >> To add here. Would it be possible/desire-able to add an auto-timeout >> to patchwo

Re: [LEDE-DEV] [OpenWrt-Devel] patchwork

2018-01-18 Thread Etienne Champetier
Hi All, 2018-01-18 1:30 GMT-08:00 Piotr Dymacz : > Hi, > > On 18.01.2018 09:44, Jo-Philipp Wich wrote: >> >> Hi John, Alex, >> >> I have no problem with closing / autorejecting open tickets in patchwork >> as long as they somehow remain available for future reference. > > > ACK. > > Would it be po