Name space collision
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 871
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 5
Description
Hi,
I intend to package umap for official Debian and stumbled upon another software also called umap inside the Debian Med repository. This looks very unfortunate to me and I consider it a good idea to talk to the authors of "[the other umap](https://bitbucket.org/hoffmanlab/umap/src/default/)" where I will file an issue as well.
Kind regards, Andreas.
Contributor guide
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
Start by reviewing the Debian Med package reference and the linked Bitbucket umap project to establish the naming conflict. Then check the discussion history and contact the other project's authors as proposed; the issue is done only when the collision has an agreed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100