ClamAV Bugzilla new ticket creation will redirect to GitHub Issues

In early 2021, we made a decision to switch to using GitHub directly. Before 
then, our primary Git repository was sequestered to the Cisco corporate 
network. The public GitHub repository was just a mirror. That made it tougher 
for us to connect to and work with contributors from the ClamAV community. Our 
daily routines drew our attention away from GitHub.


At the same time, we also settled on a plan for how we could test using GitHub 
Issues for ClamAV bug reports. Initially, this would supplement our aging 
Bugzilla server. While Bugzilla requires users to make an account on our 
server, enabling GitHub Issues would open up bug reporting to the wider GitHub 
community that already has an account.


Since enabling GitHub Issues at the start of June, we have found that using 
GitHub Issues has been a very positive experience. At this point, most of our 
reports come in through GitHub Issues. With the aid of issue templates, the 
quality of bug reports coming through GitHub Issues has also been of a higher 
caliber than those coming through Bugzilla. With users following guidance in 
the template, the bug reports are generally easier to triage and respond to 
intelligently.


All that being said, we will disable Bugzilla ticket creation so we can focus 
all new bug reports towards GitHub Issues. Effective immediately, the new 
ticket creation form on bugzilla.clamav.net 
<https://bugzilla.clamav.net/enter_bug.cgi> will redirect users to the new 
issue creation page on our primary ClamAV repository on 
GitHub.com<https://github.com/Cisco-Talos/clamav/issues/new/choose>.


Existing open tickets on Bugzilla will remain open for now, and the Bugzilla 
server is expected to remain available through 2022 as we complete this 
transition.


If you have an open ticket on Bugzilla and would like to help migrate it to 
GitHub Issues, we would appreciate the help. If you choose to migrate any 
tickets from Bugzilla to GitHub Issues, please add references in each ticket 
and close the original Bugzilla ticket(s) to assist our team with the ticket 
queue maintenance.


Thank you!

Micah

Read the blog post: 
https://blog.clamav.net/2021/12/clamav-bugzilla-new-ticket-creation.html
Posted by Micah Snyder<https://www.blogger.com/profile/07798916006145826441> at 
12:37 
PM<https://blog.clamav.net/2021/12/clamav-bugzilla-new-ticket-creation.html>[https://img1.blogblog.com/img/icon18_email.gif]<https://www.blogger.com/email-post.g?blogID=2366689974368239573&postID=152835141517312434>
Labels: bugzilla<https://blog.clamav.net/search/label/bugzilla>, 
community<https://blog.clamav.net/search/label/community>, 
github<https://blog.clamav.net/search/label/github>, 
updates<https://blog.clamav.net/search/label/updates>

_______________________________________________

clamav-devel mailing list
clamav-devel@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-devel

Please submit your patches to our Github: 
https://github.com/Cisco-Talos/clamav-devel/pulls

Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to