Merge lp://staging/~mhall119/ubuntu-community-accomplishments/approved-loco-team into lp://staging/ubuntu-community-accomplishments

Proposed by Michael Hall
Status: Rejected
Rejected by: Jono Bacon
Proposed branch: lp://staging/~mhall119/ubuntu-community-accomplishments/approved-loco-team
Merge into: lp://staging/ubuntu-community-accomplishments
Diff against target: 96 lines (+59/-1)
5 files modified
CATEGORIES (+1/-0)
accomplishments/ubuntu-community/en/advocacy/member-approved-loco-team.accomplishment (+17/-0)
accomplishments/ubuntu-community/en/advocacy/member-loco-team.accomplishment (+1/-1)
scripts/ubuntu-community/advocacy/member-approved-loco-team.py (+35/-0)
tests/ubuntu-community/advocacy/member-approved-loco-team (+5/-0)
To merge this branch: bzr merge lp://staging/~mhall119/ubuntu-community-accomplishments/approved-loco-team
Reviewer Review Type Date Requested Status
Jono Bacon Disapprove
Rafał Cieślak Needs Information
Review via email: mp+108424@code.staging.launchpad.net

Commit message

Add accomplishment for being a member of an approved loco team

Description of the change

Add accomplishment for being a member of an approved loco team

** NEEDS SUMMARY AND STEPS ADDED **

To post a comment you must log in.
146. By Michael Hall

Merge from trunk

Revision history for this message
Rafał Cieślak (rafalcieslak256) wrote :

Thanks for the MP, Michael!
There are two problems I see about this submission:
 * Fields 'summary' and 'steps' are left empty. I doubt this is intentional, as then there is almost no information about the accomplishment, so I guess you simply forgot to fill them in. Could you please fix that?
 * I wonder if we really want separate accomplishments for 'Be a member of a loco team' and 'Be a member of an approved loco team'. There are mainly two cases: a) the user will get them both at once, if his team is already registered, and b) the user will get just one of them, if his team is not registered. In both there is only one element for rewarding him for his activity, that is joining a LoCo. The fact of whether his loco is registered or not is not much an average can do about when he joins the team. This said, the only thing worth rewarding in that matter would be 'Get your LoCo to be approved', but that's a different story. I have requested a review directly from Jono, maybe he can help recognize if such accomplishment makes sense.

review: Needs Information
Revision history for this message
Michael Hall (mhall119) wrote :

The 'summary' and 'steps' fields were left empty because Jono was going to fill them in.

This accomplishment is for approved teams, not registered teams. Approved teams are existing teams that have shown a consistent level of activity and commitment to Ubuntu, they must apply for Approved status with the LoCo Council, and once approved they receive some support from Canonical (free CDs for example). More about team approval here: http://loco.ubuntu.com/loco-council/approved

Revision history for this message
Rafał Cieślak (rafalcieslak256) wrote :

Right. I am pretty much aware of what approved teams are, but my point
is that one does not choose the LoCo they belong to, so rewarding a
particular user for belonging to an approved team may get unfair.

 * I lives in Poland, and the Polish LoCo is not approved (and there
are no chances it will). That means I will get the "Be a Member of a
LoCo Team" accomplishment, but not "Be a Member of a Approved LoCo
Team"
 * User X lives in UK. It happens that UK LoCo is approved, thus he
means he gets both trophies, "Be a Member of a LoCo Team" and "Be a
Member of a Approved LoCo Team", so he is rewarded twice.
Keeping in mind that accomplishments are meant to reward users for
their activity in the community, I fail to see what user X did what I
have not done (or what he did better then I did), that was worth
rewarding by that second trophy he got (and I did not).

Revision history for this message
Jono Bacon (jonobacon) wrote :

I tend to agree with Rafal here, I don't think we need to distinguish between an approved and non-approved team, and we already have a LoCo Team member accom.

review: Disapprove

Unmerged revisions

146. By Michael Hall

Merge from trunk

145. By Michael Hall

Add LoCo Teams:Membership to the CATEGORIES file

144. By Michael Hall

Add sub-category for LoCo Teams:Membership

143. By Michael Hall

Add accomplishment for being a member of an approved loco team

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches

to all changes: