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
Group packages by language/builder via dummy maintainer #89017
Conversation
How about we make a maintainer team for these two, and somehow teach repology about maintainer teams? |
That sounds good but I'd still like to see this merged for now and then switched over to that when it's implemented. |
@grahamc speaking of teams, could you take a look at #84177 (comment) please? |
@grahamc Could you please clarify if this a blocker? |
Reviewing some old "topic: golang" PRs. It seems like the approach in #84177 is the preferred one? I'd be happy to be part of a Go maintainer team. |
No, this is works differently. Currently a team is just a pointer to a list of people and not an entity in itself so it isn't useful for repology.
I made a team for Golang compliers in #90225, feel free to open a PR to add yourself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, done thanks!
Although I have limited experience, this does seem like a reasonable step to me, assuming the repology changes would be more involved. LGTM.
@grahamc Unless there are objections I'll merge this in a week or so, I'd like to see how useful it is (or isn't) before making wider changes. |
@zowoq ping, no objections raised so it feels okay to me to move forward with this as a stop gap to gain useful functionality. |
@zowoq feel free to add me to the Rust package maintainers, once you add that team. |
Reverting this in #93394 as |
I can't be bothered trying to make changes to |
I'd like to sort these by language/builder for repology, e.g. being able to see which rust packages are outdated.
cc @grahamc @infinisil
I don't think this will cause any problems with ofborg, rfc33 or the github id checks?