search

mswart / openmensa-parsers

A collection of openmensa.org parsers with feed v2 generator
36 stars 45 forks source link

New maintainer proposal #144

Open cvzi opened 1 year ago

cvzi commented 1 year ago

@mswart I saw that there hasn't been any activity since over a year, but there are still new pull requests. Therefore I would like to propose myself as a new maintainer for this repository.

My credentials: I run several parsers on my own repositories. They can be found at https://github.com/cvzi/mensahd https://github.com/cvzi/mensa

muety commented 1 year ago

I'd love to have this project come back to life again! And it looks like a new maintainer is needed. @mswart, what do you think?

klemens commented 1 year ago

I tried keeping the project alive by reviewing and merging pull request and hosting the parsers, but at some point got a bit overwhelmed (as other things required more attention) and stopped doing reviews. But I'd also love if we could revive this project!

I think it makes most sense to convert this into a kind of community-project, so that no single person has to do everything. We could create a new organization and fork the repository there or maybe move it to the @openmensa organization (not sure if this is a good idea, @jgraichen what do you think?).

I also like the idea of using github actions to run the parsers @cvzi, it even seems you can now directly deploy to pages from actions without having to commit the results, so keeping the repo clean. I might try setting that up if I find some time. :sweat_smile:

jgraichen commented 1 year ago

We could create a new organization and fork the repository there or maybe move it to the https://github.com/openmensa organization.

@klemens I'd be fine with forking it to @openmensa and adding members on request, but likely won't have time to maintain parsers too, sorry. I am already busy keeping the server and application up and running. GitHub orgs have teams, so some kind of self organization should be possible either way. On the other hand, keeping it in a separate organization doesn't sound bad either :thinking:.

I've never been involved with parsers much. Therefore, I would keep the decision up to you. If there are some important needs from the parser or community side to the core application, I'd like to focus on them. Currently, there is openmensa/openmensa#688 asking to replace/supersede some canteens, but it is getting complicated due to how parsers, sources, feeds, and meta-feeds are interacting together. If you have some ideas on how to ease parser management (maybe at the cost of meta feeds?) I am all ears. How about adding a manager role on the application so that canteens and feeds cannot only be managed by the initial author?

you can now directly deploy to pages from actions without having to commit the results.

I am doing this for docs.openmensa.org here: https://github.com/openmensa/openmensa/blob/main/.github/workflows/docs.yml#L21-L42