haskell / haskell/cabal-userguide
Leveling Up - Uploading a package to hackage
- Dominant language
- Nix
- Stars
- 29
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
file to edit: https://github.com/haskell/cabal-userguide/blob/main/src/leveling_up/06_uploading_package_to_hackage.md
## Brief Summary
This (like haddocks #22) is another poorly documented area. This section should cover common considerations (versioning, globally unique names), the relevant metadata in the `.cabal` file that will make it on to hackage, and the process of uploading a library to hackage.
Contributor guide
No contributing guide indexed for this repository
Research direction
Edit src/leveling_up/06_uploading_package_to_hackage.md. Start by reading the existing section, then organize guidance around versioning, globally unique package names, .cabal metadata published to Hackage, and the library upload process. Done means the section clearly covers these common considerations and steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100