New BIND Gitlab open for public access

[Victoria Risk]

In July 2017 we opened ISC's RT bug database <https://www.isc.org/blogs/bind-and-isc-dhcp-bug-db-opening-for-guest-users/> for public read-only browsing of BIND and ISC DHCP issues. New bugs submitted were still kept confidential by default, but issues that had been triaged, and feature requests, were publicly viewable.

Now we want to take a further step towards transparency and welcoming community participation in the BIND project. We have migrated to Gitlab <https://gitlab.isc.org/> for our BIND development platform, and it is now open for community use.

Gitlab will make collaborating with ISC easier and more transparent.

Community members can create and manage their own accounts.
Community developers can submit merge requests directly, and will get author credit tracked in the source repo, (instead of emailing patches to our old bug tracker).
Gitlab includes an open issue tracker, where all issues are open to public view by default and where community participants can comment on and add to existing issues, as well as creating new ones.  We welcome upvoting on feature requests.
Gitlab includes a wiki space where ISC can share designs and plans.
Because we are hosting Gitlab internally at ISC, we can also maintain private issues and private branches, to protect work on confidential issues and suspected security vulnerabilities.
BIND users, patch contributors, operating system packagers, tool developers, researchers and anyone in the DNS community are all welcome to access Gitlab.isc.org <http://gitlab.isc.org/> and navigate to the BIND project.

To create an account go to Gitlab.isc.org <https://gitlab.isc.org/> and create an account, or link an existing Github or Gitlab account.

Further Details

Security issues should still be sent via email (encrypted if possible) to security-officer at isc.org <mailto:security-officer at isc.org>.
Gitlab supports creation of confidential issues. If you need to report an issue or provide information that cannot be shared publicly, select this checkbox when you submit your issue.
ISC Support customers should continue to raise issues with their support team through your own portal or via email to support at isc.org <mailto:support at isc.org>. ISC will continue to protect customer confidentiality while working on support customer issues.
ISC's Gitlab instance will not accept creation of new issues via email to reduce spam entries. You will be able to send and receive updates via email however.
As of March 5, 2018, we will no longer accept new BIND issues in our old bugs.isc.org <http://bugs.isc.org/> database. We will begin redirecting email users ASAP, but will still log their submissions in bugs.isc.org <http://bugs.isc.org/>.
Existing open BIND issues will be ported selectively to Gitlab over the next 2 months. If you have an issue pending in bugs.isc.org <http://bugs.isc.org/> that is not actively being worked that you feel should be a priority, please feel free to re-enter it into Gitlab to ensure it survives the transition.
Note that this change applies only to BIND issues: ISC-DHCP is still using bugs.isc.org <http://bugs.isc.org/> and Kea is still using kea.ics.org <http://kea.isc.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&sensitive=0&component=!Boss+of+BIND&component=!libdns++&component=!msgq&milestone=!Remaining+BIND10+tickets&group=milestone&report=1&order=priority>

Victoria Risk
Product Manager
Internet Systems Consortium
vicky at isc.org




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-workers/attachments/20180215/c70204ab/attachment.html>