ClamAV Bugzilla new ticket creation will redirect to GitHub Issues
"Micah Snyder (micasnyd)" <[email protected]> Fri, 17 Dec 2021 18:24:52 +0000
| Newsgroups | gmane.comp.security.virus.clamav.announce |
|---|---|
| Message-ID | <BYAPR11MB317463BF48F7F2917AEC708FC6789__28118.4653214709$1639765844$gmane$org@BYAPR11MB3174.namprd11.prod.outlook.com> |
--===============7755841140097544437==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_BYAPR11MB317463BF48F7F2917AEC708FC6789BYAPR11MB3174namp_"
--_000_BYAPR11MB317463BF48F7F2917AEC708FC6789BYAPR11MB3174namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ClamAV Bugzilla new ticket creation will redirect to GitHub Issues
In early 2021, we made a decision to switch to using GitHub directly. Befor=
e then, our primary Git repository was sequestered to the Cisco corporate n=
etwork. The public GitHub repository was just a mirror. That made it toughe=
r 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 Git=
Hub Issues for ClamAV bug reports. Initially, this would supplement our agi=
ng Bugzilla server. While Bugzilla requires users to make an account on our=
server, enabling GitHub Issues would open up bug reporting to the wider Gi=
tHub 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 gu=
idance 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 foc=
us all new bug reports towards GitHub Issues. Effective immediately, the ne=
w 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 pr=
imary 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 Bugzill=
a server is expected to remain available through 2022 as we complete this t=
ransition.
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 ticke=
t and close the original Bugzilla ticket(s) to assist our team with the tic=
ket queue maintenance.
Thank you!
Micah
Read the blog post: https://blog.clamav.net/2021/12/clamav-bugzilla-new-tic=
ket-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-cr=
eation.html>[https://img1.blogblog.com/img/icon18_email.gif]<https://www.bl=
ogger.com/email-post.g?blogID=3D2366689974368239573&postID=3D15283514151731=
2434>
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/upd=
ates>
--_000_BYAPR11MB317463BF48F7F2917AEC708FC6789BYAPR11MB3174namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
</div>
<h3 class=3D"post-title entry-title">
<div class=3D"shadow">ClamAV Bugzilla new ticket creation will redirect to =
GitHub Issues
</div>
</h3>
<div class=3D"post-body entry-content">
<p style=3D"margin-top: 0px; margin-bottom: 0px;"></p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">In early 2021, we made a =
decision to switch to using GitHub directly. Before then, our primary Git r=
epository 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 C=
lamAV community. Our daily routines drew our attention away from GitHub.</p=
>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">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.</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">Since enabling GitHub Iss=
ues 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 throu=
gh GitHub Issues. With the aid of
issue templates, the quality of bug reports coming through GitHub Issues h=
as also been of a higher caliber than those coming through Bugzilla. With u=
sers following guidance in the template, the bug reports are generally easi=
er to triage and respond to intelligently.
<br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">All that being said, we w=
ill disable Bugzilla ticket creation so we can focus all new bug reports to=
wards GitHub Issues.
<b>Effective <i>immediately</i>, the <a href=3D"https://bugzilla.clamav.net=
/enter_bug.cgi" target=3D"_blank">
new ticket creation form on bugzilla.clamav.net </a>will redirect users to =
the new issue creation page on
<a href=3D"https://github.com/Cisco-Talos/clamav/issues/new/choose" target=
=3D"_blank">
our primary ClamAV repository on GitHub.com</a>.</b></p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><b><br>
</b></p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">Existing open tickets on =
Bugzilla will remain open for now, and the Bugzilla server is expected to r=
emain available through 2022 as we complete this transition.
<br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">If you have an open ticke=
t 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 tea=
m with the ticket queue maintenance.</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">Thank you!</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">Micah <br>
</p>
<div style=3D"clear:both"></div>
</div>
<div class=3D"post-footer">
<div class=3D"post-footer-line post-footer-line-1"><span class=3D"post-auth=
or vcard"><br>
</span></div>
<div class=3D"post-footer-line post-footer-line-1"><span class=3D"post-auth=
or vcard">Read the blog post:
<a href=3D"https://blog.clamav.net/2021/12/clamav-bugzilla-new-ticket-creat=
ion.html" id=3D"LPNoLPOWALinkPreview">
https://blog.clamav.net/2021/12/clamav-bugzilla-new-ticket-creation.html</a=
><br>
</span></div>
<div class=3D"_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_=
1"></div>
<span class=3D"post-author vcard">Posted by <span class=3D"fn"><a class=3D"=
g-profile" href=3D"https://www.blogger.com/profile/07798916006145826441" re=
l=3D"author" title=3D"author profile"><span>Micah Snyder</span></a></span><=
/span><span class=3D"post-timestamp"> at
<a class=3D"timestamp-link" href=3D"https://blog.clamav.net/2021/12/clamav-=
bugzilla-new-ticket-creation.html" rel=3D"bookmark" title=3D"permanent link=
">
<abbr class=3D"published" title=3D"2021-12-17T12:37:00-05:00">12:37 PM</abb=
r></a></span><span class=3D"post-comment-link"></span><span class=3D"post-i=
cons"><span class=3D"item-action"><a href=3D"https://www.blogger.com/email-=
post.g?blogID=3D2366689974368239573&postID=3D152835141517312434" title=
=3D"Email Post"><img alt=3D"" class=3D"icon-action" width=3D"18" height=3D"=
13" src=3D"https://img1.blogblog.com/img/icon18_email.gif"></a><br>
</span></span><span class=3D"post-footer-line post-footer-line-2"><span cla=
ss=3D"post-labels">Labels:
<a href=3D"https://blog.clamav.net/search/label/bugzilla" rel=3D"tag">bugzi=
lla</a>, <a href=3D"https://blog.clamav.net/search/label/community" rel=3D"=
tag">
community</a>, <a href=3D"https://blog.clamav.net/search/label/github" rel=
=3D"tag">github</a>,
<a href=3D"https://blog.clamav.net/search/label/updates" rel=3D"tag">update=
s</a></span></span></div>
<div>
<div id=3D"Signature">
<div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0)">
<span style=3D"font-family:Helvetica; font-size:12px; font-weight:normal; o=
rphans:auto; text-align:start; widows:auto; display:inline!important"></spa=
n><br>
</div>
</div>
</div>
</div>
</body>
</html>
--_000_BYAPR11MB317463BF48F7F2917AEC708FC6789BYAPR11MB3174namp_--
--===============7755841140097544437==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
clamav-announce mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-announce
http://www.clamav.net/contact.html#ml
--===============7755841140097544437==--