search

sailfishos-chum / main

Documentation and issue tracker for the SailfishOS:Chum community repository
https://build.merproject.org/project/show/sailfishos:chum
MIT License
26 stars 4 forks source link

Create a list of maintainers for each of the packages #10

Open rinigus opened 3 years ago

rinigus commented 3 years ago

lbt suggested to create a list of maintainers that would link package to someone responsible for it.

piggz commented 3 years ago

Any ideas how to do this in a easy maintainable way?

fridlmue commented 3 years ago

wouldn't it be enough to set the maintainer in chum:testing accordingly? (Like suggested regarding updates?)

rinigus commented 3 years ago

So, in principle the info is at https://build.merproject.org/package/meta/sailfishos:chum:testing/harbour-avarisk . If it's missing it is either you or me (list from https://build.merproject.org/project/meta/sailfishos:chum:testing). This can be pulled using osc meta as far as I could see:

osc meta pkg sailfishos:chum:testing harbour-avarisk

and similar for prj. We would need then to pull the data and format it in some human-readable way. But that would be limited to OBS maintainers. I presume some would want to maintain at Github and ping us to start the builds. Not sure what to do with this case and if we want to encourage that.

lbt commented 3 years ago

My suggestion would be a yaml(?) file that could be extended to provide supplemental information

Initially just put it in git and manage it there?

The idea is more to record who "owns" a given app and is allowed to ask for updates. Eventually it could include more metadata that may be used by a frontend.

Like this https://git.sailfishos.org/mer-core/Maintainers/blob/master/maintainers.yaml but that structure was for a different requirement

rinigus commented 3 years ago

Such kind of YAML would be nice, probably not as structured as we mostly have simpler case. Ideally I would get that info from what we have at OBS and compose on the basis of that. Then we can also get human preferred representation as well. Would need bit of programming, but doable.