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

[RFE] "Dynamic" ownership #22

Closed
voxik opened this Issue Jan 3, 2014 · 12 comments

Comments

Projects
None yet
2 participants
@voxik
Contributor

voxik commented Jan 3, 2014

This is just rough idea, but it would be cool if the ownership of the package would be dynamically changed by merits, e.g. if somebody has more commits, resolved issues etc per some period of time, he would become owner of the package.

@pypingou

This comment has been minimized.

Show comment
Hide comment
@pypingou

pypingou Jan 3, 2014

Member

With the change from a concept of ownership to a concept of "point of contact" this might be indeed something we could consider, however, I would see this as an external tool that would query datagrepper to get the info of fedmsg, make an educated decision and apply it either via the pkgdb2 API or directly on the server as a "weekly" cron job or so and using the internal API.

Member

pypingou commented Jan 3, 2014

With the change from a concept of ownership to a concept of "point of contact" this might be indeed something we could consider, however, I would see this as an external tool that would query datagrepper to get the info of fedmsg, make an educated decision and apply it either via the pkgdb2 API or directly on the server as a "weekly" cron job or so and using the internal API.

@pypingou

This comment has been minimized.

Show comment
Hide comment
@voxik

This comment has been minimized.

Show comment
Hide comment
@voxik

voxik Feb 4, 2014

Contributor

Thanks for the research. As far as I can say, the results are biased, especially when I see ppisar gaining 1500 packages, since this is most probably due to perl mass rebuilds. filtering out commits with the same changelog would make the difference IMO.

Contributor

voxik commented Feb 4, 2014

Thanks for the research. As far as I can say, the results are biased, especially when I see ppisar gaining 1500 packages, since this is most probably due to perl mass rebuilds. filtering out commits with the same changelog would make the difference IMO.

@pypingou

This comment has been minimized.

Show comment
Hide comment
@pypingou

pypingou Feb 4, 2014

Member

I might be able to retrieve the changelog for the git messages indeed. I didn't know ppisar was doing the perl Mass-Rebuild, I can exclude him as I do for Dennis Gilmore who does the general Mass-Rebuild.

Was there a recent perl Mass-Rebuild, do you know?

Member

pypingou commented Feb 4, 2014

I might be able to retrieve the changelog for the git messages indeed. I didn't know ppisar was doing the perl Mass-Rebuild, I can exclude him as I do for Dennis Gilmore who does the general Mass-Rebuild.

Was there a recent perl Mass-Rebuild, do you know?

@voxik

This comment has been minimized.

Show comment
Hide comment
@voxik

voxik Feb 4, 2014

Contributor

I am doing mass rebuilds of Ruby packages from time to time as well. Not sure if blacklist is the best solution.

Contributor

voxik commented Feb 4, 2014

I am doing mass rebuilds of Ruby packages from time to time as well. Not sure if blacklist is the best solution.

@voxik

This comment has been minimized.

Show comment
Hide comment
@voxik

voxik Feb 4, 2014

Contributor

BTW git messages or RPM changelogs, they should be equivalent to detect mass rebuilds

Contributor

voxik commented Feb 4, 2014

BTW git messages or RPM changelogs, they should be equivalent to detect mass rebuilds

@pypingou

This comment has been minimized.

Show comment
Hide comment
@pypingou

pypingou Feb 5, 2014

Member

I will be git message as it's what I have access to with fedmsg, looking into RPM changelogs would be a completely different approach.

Member

pypingou commented Feb 5, 2014

I will be git message as it's what I have access to with fedmsg, looking into RPM changelogs would be a completely different approach.

@pypingou

This comment has been minimized.

Show comment
Hide comment
@pypingou

pypingou Jul 30, 2014

Member

I think we can close this one as well

Member

pypingou commented Jul 30, 2014

I think we can close this one as well

@voxik

This comment has been minimized.

Show comment
Hide comment
@voxik

voxik Jul 30, 2014

Contributor

Is it supported somehow?

Contributor

voxik commented Jul 30, 2014

Is it supported somehow?

@pypingou

This comment has been minimized.

Show comment
Hide comment
@pypingou

pypingou Jul 30, 2014

Member

It's not, but we saw that relying on datagrepper doesn't provide the best results and relying on RPM changelogs is not really feasible.

Member

pypingou commented Jul 30, 2014

It's not, but we saw that relying on datagrepper doesn't provide the best results and relying on RPM changelogs is not really feasible.

@voxik

This comment has been minimized.

Show comment
Hide comment
@voxik

voxik Jul 30, 2014

Contributor

Ok ... so may be one day .... :) Thanks for considering.

Contributor

voxik commented Jul 30, 2014

Ok ... so may be one day .... :) Thanks for considering.

@voxik voxik closed this Jul 30, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment