the-distro/infra
8
0
Fork 3
Code Issues 35 Pull requests 4 Packages Projects 1 Releases Wiki Activity

Bug tracking for the monorepo #2

New issue
Open
opened 2024-07-01 17:17:38 +00:00 by delroth · 3 comments
delroth commented 2024-07-01 17:17:38 +00:00
Owner
Copy link
No description provided.
delroth added this to the Bootstrap infra project 2024-07-01 17:17:38 +00:00
raito commented 2024-07-04 16:50:21 +00:00
Owner
Copy link

@hexchen is assigned to work on that.

@hexchen is assigned to work on that.
hexchen self-assigned this 2024-07-04 17:08:04 +00:00
hexchen commented 2024-07-17 10:15:57 +00:00
Owner
Copy link

From a bit of research, it seems like Bugzilla might be our best option here.

One thing I realized: do we want to have an easy way for people to submit issues on e.g. Github that get synced into [whatever bugtracker we end up selecting]?

From a bit of research, it seems like Bugzilla might be our best option here. One thing I realized: do we want to have an easy way for people to submit issues on e.g. Github that get synced into [whatever bugtracker we end up selecting]?
raito commented 2024-07-17 13:10:17 +00:00
Owner
Copy link

One thing I realized: do we want to have an easy way for people to submit issues on e.g. Github that get synced into [whatever bugtracker we end up selecting]?

what's the envisioned UX story for that? we ask them to go to some github.com/forkos/pkgs and they open issues, got synced to bugzilla and we answer over bugzilla and they continue answering over github? it feels weird and is going to run into many bridging issues if we want to implement differentiating features over bugzilla imho

so i'd be -1 (weak no)

> One thing I realized: do we want to have an easy way for people to submit issues on e.g. Github that get synced into [whatever bugtracker we end up selecting]? what's the envisioned UX story for that? we ask them to go to some github.com/forkos/pkgs and they open issues, got synced to bugzilla and we answer over bugzilla and they continue answering over github? it feels weird and is going to run into many bridging issues if we want to implement differentiating features over bugzilla imho so i'd be -1 (weak no)
👍 1
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
cache-ipv4
format
channel-scripts
acls
hexchen/colmena-checker
hexy/credentials
buildbot
ckie/moarr-v4
gerrit-metrics
moar-builders
unplug-epyc
hydra-wire-up
alertmanager
fodwatch
cadvisor-containers
gerrit-http-clones
meta01
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Bootstrap infra
Assignees
Clear assignees
No assignees
hexchen
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: the-distro/infra#2
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?