← Back to team overview

app-review-board team mailing list archive

Re: myapps statistics

 

Al 01/12/11 12:50, En/na Daniel Holbach ha escrit:
> Hello everybody,
> 
> I can't exactly remember who mentioned it to me, but I think I recall
> somebody saying that there were plans (or at least ideas) to add some
> kind of statistics into myapps.
> 

I think I might have mentioned on the chat we had last week, but Anthony
can better explain the details.

> Does anybody know what was discussed there?
> 
> Also: which parts of the myapps reviews will be public? Will we have the
> chance to invite contributors outside the ARB to review apps?
> 

Allison, Anthony, I wanted to send the notes of the call we had last
week, but got sidetracked. Let me do this now and try to answer Daniel's
question at the same time.

Also, you've already got a clear idea of the work, so please feel free
to correct or complement any of the points.

• The Consumer Apps Server team is ready to start the work of making the
ARB process public in MyApps (that was last week, as far as I understand
it this work is now in progress or committed)

• The ARB queue in MyApps is where applications are reviewed - no more
Launchpad (but will do reviews on IRC/mailing list)

• The main goal is to make the ARB apps queue in MyApps public:
  ∘ Details: everyone will be able to click on the list of applications
and see the details for each app
  ∘ Review: everyone will be able to see the review page for each app to
see its status and the developer-ARB conversation, but only in read-only
mode. Only ARB members can change the status
  ∘ Tarballs: the link to the tarballs submitted will be public, so that
non-ARB contributors can help with packaging

• Other:
  ∘ Apps end up automatically on the ARB queue if the developer sets a
0$ price and a chooses a Free Software license. No manual relocation to
the right queue (commercial vs. ARB) is necessary
  ∘ It would be nice to map the django group for ARB reviewers to the
Launchpad ARB team. Anthony says this shouldn't be too hard.
  ∘ Some nice to have features (might need to be left for later):
    ‣ Ability to respond without having to resubmit
    ‣ Private comments from reviewers to developers
  ∘ There were some initial concerns on whether the ARB queue should be
public, to avoid the situation where a commercial app ends up
accidentally in the ARB queue and thus the submitted tarball (either
with sources or binaries) is made public. The consensus in the call was
that the steps to set the price and the license steps are obvious enough
for developers to get them right, and that the benefits of making the
ARB queue public (transparency, allow external contributors to help with
packaging) outweight the risk, which is in any case low.
  ∘ Notification e-mails will be sent to the app-review-board mailing list.

> Thanks a lot to everyone involved in this work!
> 
> (Anthony: if I CCed you by mistake, can you please tell me who I'd
> rather get in touch with?)
> 
> Have a great day,
>  Daniel
> 

Cheers,
David

Attachment: signature.asc
Description: OpenPGP digital signature


References