Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[logic] why ? #14990

Closed
cybernet opened this issue Apr 26, 2021 · 1 comment
Closed

[logic] why ? #14990

cybernet opened this issue Apr 26, 2021 · 1 comment

Comments

@cybernet
Copy link

Why did you choose to split this project on multiple platforms ... GITHUB of all ... and the issues on bugzilla ? if you expect people to signup on a new platform, why not choose gitlab ? IT'S FREE

@NeilHanlon
Copy link
Member

Hi @cybernet -

Ultimately, we're still figuring out what works best, what we need, and where we can simplify. That being said, the decision regarding bugzilla came down to the following:

  • GitLab (or GitHub) can host source code in the future (it doesn't right now) and issues will be for the code
    • Think of Fedora pagure for their source code issues and they use bugzilla.redhat to deal with distribution issues.
  • Bugzilla will be the distribution tracker.
    • It did not make sense to have a distribution bug tracker in Git. The organization does not allow for that and we also don't want to open groups/projects just to field issues with the distribution. The git contributor agreement does explain this.

In summary, there should be a logical separation between source code issues (which is very little) and actual distribution issues (which will likely be higher for a long while). But, this brings up some other things:

  • We don't like the idea of having disorganization on github issues or consolidating things into a single unorganized bucket
    • Git(hub|lab) issues are great, but not for something that is complex, like a distribution and its infrastructure requirements.
  • Creating projects/groups for things that won't have code to host issues did not make logical sense
  • Release Engineering tools already hook into bugzilla and git and use them for their specific use cases.

Hopefully that gives some clarity on the use of bugzilla - where everything will "live" long term remains to be seen. We've only been at it for a few months.

If you have any follow up questions, I'd be happy to try and answer them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants