Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No link to upstream source for charms from charm page #427

Open
mthaddon opened this issue Mar 9, 2017 · 5 comments
Open

No link to upstream source for charms from charm page #427

mthaddon opened this issue Mar 9, 2017 · 5 comments

Comments

@mthaddon
Copy link

mthaddon commented Mar 9, 2017

Currrently there is no link from a charm page (such as https://jujucharms.com/landscape-client/ ) to where the upstream code lives, so it's very hard for someone to know where they should submit charm changes.

@mitechie
Copy link
Contributor

mitechie commented Mar 9, 2017

This is because the authors have not put a homepage or bugs-url in for the charm. I'm ping'ing @sparkiegeek to see if they could arrange that for their charm. See the "set" command examples in https://jujucharms.com/docs/2.1/tools-charm-tools

@mitechie
Copy link
Contributor

mitechie commented Mar 9, 2017

Note that there's http caching in place so once the urls are set it'll take 10-15min for the changes to show on the charm webpage. It will work immediately from the cli:

charm show cs:landscape-client bugs-url
charm show cs:landscape-client homepage

@xavpaice
Copy link

Just to ensure it's clear, there is also no link on the landscape-server charm as well as the client.

@digitalrayne
Copy link

Also, a bugs URL or homepage is informative, but not definitive. There is currently no way to say reliably which upstream repository, commit or tag was used when publishing a charm.

It's often possible to track back via the project homepage or bug submission link, where hopefully the charm author is diligent about tagging their releases in relation to uploads to the charm store - this is not always the case, and open to interpretation as well, as there is no definitive linkage between the source of a charm, and the uploaded charm.

@sparkiegeek
Copy link

FWIW both landscape-server and landscape-client charms now have correct links for bugs-url and homepage.

Thanks for the pointers @mitechie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants