MerginMaps / MerginMaps/geodiff
Find a way how to publish non-official pygeodiff versions
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
We need to publish experimental versions of pygeodiff:
- using pip versioning
- using new pip distro
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 project's packaging configuration and existing release process, then compare the requested pip versioning and new pip distribution approaches. Done means there is a documented, repeatable way to publish experimental pygeodiff versions without disrupting official releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100