[Hamara-devel] Proposal: Move our bug tracker to GitLab Issues

[Dhanesh Sabane]

On 08/23/2018 03:25 PM, Raju Devidas wrote:
> Reply Inline
> 
> On 22/08/18 2:39 PM, Shivani Bhardwaj wrote:
>> Please note that our GitLab was restructured and made such that 
>> keeping issues would not be a problem there. Bugs were not migrated 
>> from Bugzilla. It is yet to be done. There are a few tools out there 
>> [untested] which might help with the bulk import. However, GitLab does 
>> not provide any such plugin or feature[1].
>>

Last I checked, there weren't many bugs on Bugzilla for Svastik "2.0" 
which would require us to set up a tool and import everything to GitLab.

>> Conclusion: I think, if we're moving the issues to GitLab, all the 
>> issues should be moved there and shut Bugzilla down completely.

As decided in the meeting of 27th Aug 2018 and also as discussed 
off-list about having the choice of integrating Bugzilla issues with the 
wiki, we will stick with Bugzilla for this release and move to GitLab 
for all future releases.

> How about keeping the bugzilla instance only in a read only mode as an 
> archive of previous bugs?
> Instead of shutting it down completely.
> As a reference, here is what the GNOME project did
> https://bugzilla.gnome.org/
> They have a ticker on there homepage.

+1. We should definitely keep it as read only.

> While there bug tracker still allows to file bugs for few sub projects.
> Is there a way to limit the bugzilla instance to accept no new bugs
>>

 From what I've observed in other projects (read Fedora ;)), there is a 
way to limit the Bugzilla instance to accept no new bugs.

-- 
Dhanesh B. Sabane
https://dhanesh95.gitlab.io
PGP ID: 0xB69A98C9C1642329
Fingerprint: 9655 11F2 0D18 E76A 2396  D64D B69A 98C9 C164 2329