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

requesting standard cert for weblate.dataverse.org #1

Open
donsizemore opened this issue Mar 3, 2020 · 8 comments
Open

requesting standard cert for weblate.dataverse.org #1

donsizemore opened this issue Mar 3, 2020 · 8 comments

Comments

@donsizemore
Copy link
Member

The https-portal Let's Encrypt -produced certs throw a CA warning in my browser and @pdurbin can mint dataverse.org certs, so I'm requesting one.
weblate_dataverse_org.csr.zip

@pdurbin
Copy link
Member

pdurbin commented Mar 3, 2020

@djbrooke can we please pull this into Ready? We want the translators to have a better user experience and we want to facilitate even more languages (12 by my count!). Basically @4tikhonov is trying to provide a better user experience for @mhvezina and other translators.

@djbrooke
Copy link

djbrooke commented Mar 3, 2020

@pdurbin that's fine. If it's easy feel free to move into in progress. Anything needed from me?

@pdurbin
Copy link
Member

pdurbin commented Mar 4, 2020

@djbrooke yes. I don't have permission to move it so please go ahead.

@pdurbin
Copy link
Member

pdurbin commented Mar 4, 2020

@djbrooke actually, there is no "Ready". This is under @GlobalDataverseCommunityConsortium rather than @IQSS. So I guess we need @qqmyers to figure this out? When I say "Ready" I mean the column at https://github.com/orgs/IQSS/projects/2

Screen Shot 2020-03-03 at 9 28 52 PM

@pdurbin
Copy link
Member

pdurbin commented Mar 4, 2020

I created a ticket upstream that I put in Ready instead: IQSS/dataverse#6721

@djbrooke maybe we should document this procedure.

@qqmyers
Copy link
Member

qqmyers commented Mar 4, 2020

@pdurbin - that (separate ticket) seems like a reasonable way to track work - home institutions are probably the most interested. That said, I think that individual GDCC repositories can go ahead and set up additional tools in github if they want. Our assumption is that the repos under GDCC will be diverse enough that there's no one-size-fits-all solution beyond general policies (at https://docs.google.com/document/d/e/2PACX-1vSeoSqRASpqHogVHdi_WTlzudP2ZE_yjwTYtbrDgCVgQbGK3SAr6ktbbAWF0O2wl_KlYwR8QaqCcLlY/pub - suggested changes welcome).

@pdurbin
Copy link
Member

pdurbin commented Mar 4, 2020

@qqmyers I haven't clicked that link yet but specifically about HTTP certs, does the GDCC offer free web certs for subdomains of http://dataversecommunity.global ? Let's say we want to install Discourse and have a https://discourse.dataversecommunity.global for example (Fernando Perez recently said we are welcome to have a reproducibility category on https://discourse.jupyter.org by the way. Maybe we should take him up on that!). Does that make sense? Instead of weblate.dataverse.org would you like to help @donsizemore and @4tikhonov set up weblate.dataversecommunity.global? Let dozens of translations bloom! I shows how the Dataverse community is truly global!

@pdurbin
Copy link
Member

pdurbin commented Mar 4, 2020

@donsizemore I don't have permission to edit the title of this issue but if you could switch it from "docker" to "dataverse" that'd be great. I assume it's a typo. 😄 And you made me copy it over to IQSS/dataverse#6721 you rat! 🐭 Fixed on the other side! 🎉

@donsizemore donsizemore changed the title requesting standard cert for weblate.docker.org requesting standard cert for weblate.dataverse.org Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants