# A suggestion for package maintainers

**URL:** <https://discourse.julialang.org/t/a-suggestion-for-package-maintainers/44111>\
**Category:** Community\
**Tags:** package, suggestions\
**Created:** [August 1, 2020, 11:10pm UTC](https://discourse.julialang.org/t/a-suggestion-for-package-maintainers/44111 "2020-08-01T23:10:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)\
**Post date:** [August 1, 2020, 11:17pm UTC](https://discourse.julialang.org/t/a-suggestion-for-package-maintainers/44111/2 "2020-08-01T23:17:54Z")

</div>

I’ll second this, and its reverse… 😉

> [@Plea to package developers regarding documentation!](https://discourse.julialang.org/t/plea-to-package-developers-regarding-documentation/37473):
>
> Very serious topic ahead: Please please please can package developers put a link BACK to the source repo inside your documentation! Without it, the documentation becomes a trap. Randomly selected example: [StatsBase.jl Documentation · StatsBase.jl](https://juliastats.org/StatsBase.jl/stable/) It is becoming more common now that Google is taking me to documentation pages rather than the Github repo. I frequently flip back and forth between code and documentation, but this process is beyond cumbersome if the documentation contains no easily…

---

_[View the full topic](https://discourse.julialang.org/t/a-suggestion-for-package-maintainers/44111)._