bountysource / bountysource/core

Logical representation change proposition [Teams -> Projects -> Trackers -> Issues/Bounties]

Open
#537 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
643
Forks
199
PR merge metrics
No merged PRs in 30d

Description

Instead of having teams and trackers only. Add projects.

LLVM (team)
- the LLVM (team) can add verified projects of theirs.
- clang
- Polly
- Stacker
- each project has various trackers, each tracker is only representing one query/backend
- the llvm project could have trackers for:
- http://llvm.org/bugs/enter_bug.cgi?product=libraries
- http://llvm.org/bugs/enter_bug.cgi?product=tools

Migrating to a new issue tracking system would be easier as users could still visit the usual project page and not a specific tracker.
Simultaneous usage of different issue trackers, which is not uncommon could be implemented.
The search would be cleaner as only projects not every tracker would show up.
It's easier to verify projects and let these projects handle their trackers.
Users don't have to handle and care about where an issue comes from. Only that he can search issues related to a team, or a specific project.
##

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1574555-logical-representation-change-proposition-teams-projects-trackers-issues-bounties?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github).

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named in the issue. First clarify the proposed team–project–tracker–issue/bounty model, migration expectations, and simultaneous tracker behavior with maintainers; done would require an agreed scope before implementation can begin.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.