On 06/22/2011 09:21 PM, Andrew Flegg wrote: > On Wed, Jun 22, 2011 at 19:37, Ferenc Szekely <[email protected]> > wrote: >> >> I am trying to gather author, maintainer and packager information about >> the packages in order to implement the Community QA for MeeGo Apps [1]. >> >> According to the criteria application authors, maintainers or packagers >> should not be able to vote on their own packages. Unfortunately such >> info is not always available or incorrect through the OBS API [2]. > > Isn't this a deficiency in the OBS API? Could it be derived from where > the package has come? > It is up the repo owner what meta info is available in the raw configuration of a package. OBS itself does not require such data.
> We have shared-signon throughout meego.com. A package will have come > from :home:<user>(:.+)?. If <user> == logged_in_user, no vote. > This is not the same criteria what you wrote on the wiki page [1] :) We can prevent this scenario, yes. I checked, that a home project name _can not_ be altered by the owner using the OBS web UI. So we can compare that against the logged_in_user. This is however not the same as for checking authors, maintainers or even packagers :) I agree with Till and I think we should just kindly ask people not vote for their own app / package. Even if we had automation they could always register new MeeGo accounts and that was it... > Is it that simple? > Yes, it is. As far as the wiki page [1] tells we need to discuss this here on the list and then file a bug, so that the Community Office could change the policy on their next meeting ;) Shall we consider this topic to be formally "discussed" or let's wait a few more days? > HTH, > > Andrew > Thanks, ferenc [1] http://wiki.meego.com/MeeGo_Apps/QA#Crowdsourced_quality_assurance [2] https://api.pub.meego.com/apidocs/#22 [3] https://api.pub.meego.com/source/home:feri/rfk/_meta _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
