Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Eliezer Croitoru
NOC NOC, anybody there? Please take a minute to look at the subject. Thanks, Eilezer Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -Original Message- From: Alex Rousskov [mailto:rouss...@measurement-factory.com] Sent: Friday, July

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

2017-07-20 Thread Eliezer Croitoru
Then if nobody is sending these issues or using then, I believe that leaving this section should stay open as a "Chat" and "Connection initiation" channel for a month or so. Also if it's doable to integrate github accounts with the bugzilla it would be pretty good thing to do. And last but not

Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Alex Rousskov
On 07/20/2017 02:52 PM, Eliezer Croitoru wrote: > And... I must say that I am experiencing something weird with the wiki in the > last month or more. > I mean that for example I received the message in the top left side of the > wiki: > "Thank you for your changes. Your attention to detail is app

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

2017-07-20 Thread Alex Rousskov
On 07/20/2017 02:48 PM, Eliezer Croitoru wrote: > github cab mainly be related to coding Since no automation can enforce that kind of separation, we would have to do it manually, which will both annoy posters (confused by an unusual split) and drain our resources. > If I(a programmer) already h

Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Eliezer Croitoru
Thanks, And... I must say that I am experiencing something weird with the wiki in the last month or more. When I post a new article or update an existing one the connection end very far in the "future" despite to the fact that the wiki finished handling the post. I mean that for example I posted

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

2017-07-20 Thread Eliezer Croitoru
Well, what I was thinking is that issues in github cab mainly be related to coding and development like what the squid-dev list is. I understand that technically the Bugzilla and the issues section are not different too much, but, we can logically set a rule that issues would be in the Squid-Cac

Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Alex Rousskov
On 07/20/2017 01:58 AM, Kinkie wrote: > I believe we are talking about updating the pages that reference bzr > with pages that reference the current repositories and best practices Yes, Kinkie's interpretation is correct. We are not moving the wiki or any wiki pages. We should update a few pages

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 > issu

Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Kinkie
I believe we are talking about updating the pages that reference bzr with pages that reference the current repositories and best practices On Thu, 20 Jul 2017 at 08:27, Eliezer Croitoru wrote: > I didn't knew we are trying to "re-write" the wiki. > To what scale are we talking? > Mover everythin

Re: [squid-dev] Bzr to git migration schedule

2017-07-20 Thread Eliezer Croitoru
I didn't knew we are trying to "re-write" the wiki. To what scale are we talking? Mover everything from the wiki.squid-cache.org to github or just specific articles? Eliezer Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -Original Mess

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

2017-07-20 Thread Eliezer Croitoru
Can we allow issues access to specific users? I believe that the right place to have a "TODO" or similar notes as a github issue might be a good thing. I think that the Bugzilla has much to offer then github issues so +1 for staying with the Bugzilla, but maybe try to utilize issues for code spec