Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-31 Thread Alex Rousskov
@lists.squid-cache.org] On Behalf Of > Kinkie > Sent: Saturday, July 22, 2017 18:16 > To: Alex Rousskov <rouss...@measurement-factory.com> > Cc: Squid Developers <squid-dev@lists.squid-cache.org> > Subject: Re: [squid-dev] [RFC] Disable Github issue tracker > > I

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-22 Thread Eliezer Croitoru
...@lists.squid-cache.org] On Behalf Of Kinkie Sent: Saturday, July 22, 2017 18:16 To: Alex Rousskov <rouss...@measurement-factory.com> Cc: Squid Developers <squid-dev@lists.squid-cache.org> Subject: Re: [squid-dev] [RFC] Disable Github issue tracker I also agree to close Issues for the ti

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-22 Thread Kinkie
I also agree to close Issues for the time being. We can always reopen them later on if it'll be deemed useful. On Fri, Jul 21, 2017 at 5:37 PM, Alex Rousskov wrote: > On 07/21/2017 10:15 AM, Amos Jeffries wrote: >> Alex would you like to draw up a formal

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-21 Thread Alex Rousskov
On 07/21/2017 10:15 AM, Amos Jeffries wrote: > Alex would you like to draw up a formal announcement email to go out to > people not on squid-dev about the change having been done? > I'm thinking squid-announce/squid-users and the blog. I can, but I do not recommend announcing anything and

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-21 Thread Amos Jeffries
On 22/07/17 03:08, Alex Rousskov wrote: On 07/21/2017 12:29 AM, Eliezer Croitoru wrote: so anyone that will land into the github repository will be aware that the project is moving\moved from bzr to github IMO, that historical fact is rather useless for somebody who is already on Github,

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-21 Thread Alex Rousskov
s to) critically important Squid-specific information IMO. Cheers, Alex. > -Original Message- > From: Alex Rousskov [mailto:rouss...@measurement-factory.com] > Sent: Friday, July 21, 2017 07:57 > To: Eliezer Croitoru <elie...@ngtech.co.il>; squid-dev@lists.squid-cach

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-21 Thread Eliezer Croitoru
ch.co.il>; > squid-dev@lists.squid-cache.org > Subject: Re: [squid-dev] [RFC] Disable Github issue tracker > > On 07/20/2017 01:25 AM, Eliezer Croitoru wrote: >> Can we allow issues access to specific users? > > AFAIK no. We can restrict certain issue updates (

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-20 Thread Alex Rousskov
ch audience? IMHO, we are. Cheers, Alex. > -Original Message- > From: Alex Rousskov [mailto:rouss...@measurement-factory.com] > Sent: Thursday, July 20, 2017 20:35 > To: Eliezer Croitoru <elie...@ngtech.co.il>; squid-dev@lists.squid-cache.org > Subject: Re: [squid-

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-20 Thread Eliezer Croitoru
:35 To: Eliezer Croitoru <elie...@ngtech.co.il>; squid-dev@lists.squid-cache.org Subject: Re: [squid-dev] [RFC] Disable Github issue tracker On 07/20/2017 01:25 AM, Eliezer Croitoru wrote: > Can we allow issues access to specific users? AFAIK no. We can restrict certain issue updates (e.g.,

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-20 Thread Alex Rousskov
On 07/20/2017 01:25 AM, Eliezer Croitoru wrote: > Can we allow issues access to specific users? AFAIK no. We can restrict certain issue updates (e.g., comment editing) but not issue reading and issue creation. > I believe that the right place to have a "TODO" or similar notes as a github >

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-20 Thread Eliezer Croitoru
toru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -Original Message- From: squid-dev [mailto:squid-dev-boun...@lists.squid-cache.org] On Behalf Of Amos Jeffries Sent: Wednesday, July 19, 2017 06:27 To: squid-dev@lists.squid-cache.org Subject: Re: [squid

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-19 Thread Alex Rousskov
On 07/19/2017 06:31 AM, Amos Jeffries wrote: > On 19/07/17 16:41, Alex Rousskov wrote: >> On 07/18/2017 09:26 PM, Amos Jeffries wrote: >>> There are maintainer workflow scripts still todo, but before going to >>> the trouble I'm considering whether that workflow still makes any sense >>> - it was

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-19 Thread Amos Jeffries
On 19/07/17 16:41, Alex Rousskov wrote: On 07/18/2017 09:26 PM, Amos Jeffries wrote: On 19/07/17 09:22, Alex Rousskov wrote: With Squid official repository now at Github, a lot more folks will be tempted to report bugs and file feature requests there. I propose to remove that

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-18 Thread Alex Rousskov
On 07/18/2017 09:26 PM, Amos Jeffries wrote: > On 19/07/17 09:22, Alex Rousskov wrote: >> With Squid official repository now at Github, a lot more folks will >> be tempted to report bugs and file feature requests there. I propose to >> remove that functionality from the Github interface (for

Re: [squid-dev] [RFC] Disable Github issue tracker

2017-07-18 Thread Amos Jeffries
On 19/07/17 09:22, Alex Rousskov wrote: Hello, With Squid official repository now at Github, a lot more folks will be tempted to report bugs and file feature requests there. I propose to remove that functionality from the Github interface (for now). Any objections or better ideas?