DHI / DHI/python-package-development
Private package workflow
Open
- Dominant language
- Jupyter Notebook
- Stars
- 8
- Forks
- 1
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Recommended way of publishing internal packages.
Some ideas:
* Rely 100% on GitHub, what about non-git users?
* Use Azure Artifacts, make sure everyone has access to the feed
* DIY [devpi](https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html), can we convince IT that it is their responsibility to provide IT services, and this is an important one?
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by comparing the GitHub, Azure Artifacts, and devpi options in the issue, including non-git users and feed access; done means the internal package publishing workflow and ownership are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github, python
- Domain
- developer-experience, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100