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

In need of maintenance! #102

Closed
loleg opened this issue Feb 15, 2021 · 11 comments
Closed

In need of maintenance! #102

loleg opened this issue Feb 15, 2021 · 11 comments

Comments

@loleg
Copy link

loleg commented Feb 15, 2021

This code has been untouched for a number of years, and could use some developer love. Even though it is a frontend to a static database, so security warnings are not especially worrying - there are people around the world who may be depending on this content being accessible. Adding SSL certificates, checking up on some overdue issues, and of course updating the underlying datasets is something this community would very much appreciate.

If you or someone you know can tend to this repository, please drop us a line here: https://discuss.okfn.org/t/winter-maintenance-of-okfn-projects/10116/

@tfmorris
Copy link

Your profile says that you're a member of OK*, so you should have the privileges to do this yourself. If you need help, @rufuspollock merged the last PR, so might be a good resource for questions.

@rufuspollock
Copy link
Member

@loleg happy to make you a maintainer here if you don't already have access 😄 - and yes would be great to have some love here ... ❤️

@loleg
Copy link
Author

loleg commented Feb 16, 2021 via email

@augusto-herrmann
Copy link
Collaborator

For a while I have been meaning to update the Brazilian public bodies dataset and extraction tools (#72). I also would like to advance the data modelling (e.g. #68). This might be a good time to actually do it.

However, I also think that we probably need a new frontend, cleaning/updating other country datasets, finding data maintainers, etc., and I don't have the time to do it all.

@rufuspollock
Copy link
Member

@augusto-herrmann i think if you update the data we can probably find a way to sort frontend.

@augusto-herrmann
Copy link
Collaborator

Amazing!

Considering the Open Data Day is coming soon, I think this could be a good ODD project to do.

@augusto-herrmann
Copy link
Collaborator

I have not managed to do this by the time of the ODD, but I have now proposed including a field (#104) and will soon update the br.csv data.

@augusto-herrmann
Copy link
Collaborator

Done! I've left #104 and #105 up for review for anyone interested and with some time to do it. However, if time goes by and nobody is available, I'll merge them myself.

Maybe this already qualifies for closing this issue. @loleg WDYT?

@rufuspollock we now have links to images (logos or main building photos) of several public bodies. It would be nice to display them on that UI revamp you mentioned.

@loleg do you think it would be a good idea to implement the importing of Swiss data as scripts on this repository (in scripts/import) with updates by Github Actions, as I did for Brazilian data in #105?

@loleg
Copy link
Author

loleg commented Apr 16, 2021

I think that is a great idea, though I don't maintain the morph.io scraper it should be straightforward to port here. Thanks very much for the update!

@loleg
Copy link
Author

loleg commented Apr 19, 2021

As to closing the issue: feel free to do it. I think though a ticket like this is a good little flag to gain people's attention.

@augusto-herrmann
Copy link
Collaborator

Of course, @loleg. Thanks for calling attention, as this project had been dormant for a while.

Let me first check the things you mentioned when you opened it.

Adding SSL certificates, checking up on some overdue issues, and of course updating the underlying datasets is something this community would very much appreciate.

I've just checked, the publicbodies.org has https enabled and a valid TLS certificate just fine. It expires on August 13th, 2021.

As for the overdue issues, I've looked into some, but I still think it would be worth to review all open issues and see if they still make sense today, evaluate if they're worth the effort, if anyone can help, etc., or just simply organising them.

Updating the datasets: it's already been done for BR, which is also configured to automatically update once a week. As time allows for it, we can start updating and automating other data sources as well.

I think anything more specific can be handled on its own issue, so I'm closing this one.

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

4 participants