>________________________________
>From: Andrew Flegg <[email protected]>
>To: Ferenc Szekely <[email protected]>
>Cc: "[email protected]" <[email protected]>
>Sent: Wednesday, June 22, 2011 3:33 PM
>Subject: Re: [MeeGo-community] MeeGo Apps catalog: How to get packager,
>maintainer, author info from a package?
>
>On Wed, Jun 22, 2011 at 21:24, Ferenc Szekely <[email protected]> wrote:
>> On 06/22/2011 09:21 PM, Andrew Flegg wrote:
>>
>>> 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] :)
>
>...which is still in draft stage; so I see no problem in adjusting it
>to include a clarification that "'Packagers/Authors/Maintainers' is a
>term referring to the 'owner' of the project within OBS"
>
>Then:
>
>> 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 :)
>
>If this is easy, I suggest we do it. There's got to be some
>identification of them anyway to allow the "owner" to promote further
>or demote.
>
>> 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...
>
>Yes, it's not trying to prevent fraud; it's trying to ensure that
>people don't do something we don't want them to. Since we have to know
>the "owner" anyway, I think it's a usability improvement (and helps
>with the design because the vote buttons can be replaced with a
>promote (disabled until passed) and demotion button for the "owner").
>
>
>
>
_______________________________________________
MeeGo-community mailing list
[email protected]
http://lists.meego.com/listinfo/meego-community
http://wiki.meego.com/Mailing_list_guidelines
