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

[Alex Rousskov]

On 07/21/2017 12:29 AM, Eliezer Croitoru wrote:

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

FWIW, I fail to see a logical connection from "nobody was using X for a
year" to "let's leave X available for another month".

Github Issues are not meant for "chatting" or "project connection
initiation". "Nobody" is using them that way across Github. We can try
to force people to use our Issues in our special, novel way, but that
seems like a doomed strategy for a project that does not receive much
attention.

If we leave Github Issues open, would you volunteer to tell everybody
who "misuse" Issues for bug reports and feature requests to re-file
their issues with Bugzilla, explaining why they need to spend an extra
20 minutes of their time (after they already did a perfectly reasonable
and honorable thing -- filing a well-written bug report in Github Issues)?


> Please take your time to add a README.md to the github repo 

I agree that this should be done.


> 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, already looking at a live git repository. README.md should
only contain (references to) critically important Squid-specific
information IMO.


Cheers,

Alex.


> -----Original Message-----
> From: Alex Rousskov [mailto:rousskov at measurement-factory.com] 
> Sent: Friday, July 21, 2017 07:57
> To: Eliezer Croitoru <eliezer at ngtech.co.il>; squid-dev at lists.squid-cache.org
> Subject: Re: [squid-dev] [RFC] Disable Github issue tracker
> 
> 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 have an account at github, why should I 
>> open a new account just to start interacting with the Squid-Cache 
>> project?
> 
> You are probably assuming that Bugzilla cannot accept github logins.
> This is not my area of expertise, but I believe that Bugzilla can be configured to do so (natively or via extensions).
> 
> 
>> What do you think about the idea of leaving the issues section open?
> 
> FWIW, Github issues were open for more than a year, without attracting any significant contributions. I would be surprised if they suddenly start doing so now.
> 
> 
>> Or maybe we are not looking for such audience?
> 
> IMHO, we are.
> 
> 
> Cheers,
> 
> Alex.
> 
> 
> 
>> -----Original Message-----
>> From: Alex Rousskov [mailto:rousskov at measurement-factory.com]
>> Sent: Thursday, July 20, 2017 20:35
>> To: Eliezer Croitoru <eliezer at ngtech.co.il>; 
>> squid-dev at 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., 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 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 specific things and to allow only specific users get access to it.
>>>
>>
>> What is the essential difference between a code-specific TODO/note and a feature request that makes only the former category benefit from using Github Issues?
>>
>> Alex.
>>
>