opensharehq / opensharehq/backend
Tag system development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 4
- Avg merge
- 5h 19m
- Merged PRs (30d)
- 6
Description
The tag system is a key part of OpenShare and should integrate deeply with OpenDigger. Each tag includes an internal unique ID, English name, Chinese name, type (project, company, foundation, tech domain, etc.), and data describing platforms with org, repo, and developer lists, matching the OpenDigger schema. Tags can filter projects and people. Beyond OpenDigger tags, individuals and organizations on OpenShare can manage their own tags for easier point distribution; personal tags are private and organization tags are visible to admins, while public tags should be submitted to OpenDigger for automatic sync. A tag viewer/editor component must show tag details and allow edits, ideally raising PRs directly to OpenDigger using OAuth tokens.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or existing entry points. Start by mapping the backend's current project, person, organization, and OpenDigger integration models, then clarify tag schemas, visibility rules, synchronization, and OAuth-based editing. Done requires an agreed design and implementation plan before the viewer/editor and tag management work can be split into smaller tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100