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

Repairing language menu #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

almereyda
Copy link

@almereyda almereyda commented Sep 29, 2023

Ideally, a new build based on this fixes the partially working language links in the top right.

Sister PR of opendatacity/stasi-vs-nsa#2

@MichaelKreil
Copy link

Unfortunately, my access to all my OpenDataCity projects was revoked by the new owner company "Datenfreunde".

@almereyda
Copy link
Author

almereyda commented Sep 30, 2023

@mvtango is reported on https://github.com/orgs/opendatacity/people as a maintainer.

Would it maybe be possible to set up Teams in the organisation, which would help to provide selected access to external long-term maintainers which are not part of Datenfreunde, who don't need access to all repositories in the Open Data City organisation?

Maybe it would be possible to replace dynamic runtime components of the previous stack(s) into more or less self managed static assets? To second your hint, http://datenblumen.wired.de/ + http://www.opendatacity.de/ could indeed benefit a bit from some attention by https://datenfreunde.com/.

Also now that the Prism and Stasi-vs-NSA repositories are primarily hosted on GitHub Pages, it may even be a nice gesture to move them into CNAME subdomains of opendatacity.de hand have them age well within an enduring and no maintenance environment there.

@yetzt
Copy link
Contributor

yetzt commented Oct 4, 2023

@almereyda i would not hold my breath. those who retained the opendatacity trademark haven't used it in many years and didn't even renew the websites tls certificate.

@almereyda
Copy link
Author

almereyda commented Oct 4, 2023

I see. It's just a pity to see this beautiful and important work decay. The fixes I propose show a path towards sustainable long-term availability, and most likely do not involve any further effort. Maybe at some point someone steps up and shows a heart for this inherited legacy.

Yet I won't hold my breath just yet, so thanks for the suggestion. Eventually such considerations should be included in the beginning of a given project already, and cannot be applied in hindsight, I don't know.

Is this the same Datenfreunde that were mentioned as 'the new owner company', if I chose to reach out with asking for a second opinion or a little help here?

The user profile of @mvtango does not give any direct hints about how to reach out, why I am asking.

If the maintainer finds this and would like to have a word in private, please feel free to reach out to me at https://degrowth.social/@yala via the federation.

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

Successfully merging this pull request may close these issues.

3 participants