On Fri, Dec 3, 2010 at 1:20 PM, Matthew Paul Thomas <email address hidden> wrote:
> In my current sketches, developer.ubuntu.com:
> * lets moderators moderate reviews - developer.ubuntu.com/reviews (or maybe that should be developer.ubuntu.com/moderate?)
Either of those would be fine (out of those options, I'd prefer
/reviews/ as it better encapsulates what the app is about -
reviews+moderation - even if it means urls like /reviews/reviews/2/,
/reviews/moderations/3/ etc.).
Going slightly off-topic (perhaps something for the Monday call), but
why do we want reviews+moderations to be at developer.ubuntu.com at
all? Wouldn't software-center.ubuntu.com be a better long-term
location (especially if the web app eventually exposes reviews via the
UI - for whom the target audience would not be developers, but even
just for the moderation functionality, which is not developer specific
like the other resources you've listed below.
> * lets developers submit applications, track their submissions, and see installation stats (and eventually reviews) for their published applications - developer.ubuntu.com/status
> * lets anyone browse and search a knowledge base about developing on Ubuntu - developer.ubuntu.com/kb.
>
> It shouldn't be particularly common for moderators to be developers, so
> there's no particular need for them to stay signed in between the first
> application and the other two, but there's no particular need for them
> *not* to share credentials either.
>
> Most of the time, it won't be relevant to a moderator what Ubuntu
> version or package they're moderating for: they'll just go to the
> moderation app's base URL and be presented with a global list of flagged
> reviews, most-flagged first. The main thing that they'll want to filter
> on is language, and some moderators will be multilingual, so that
> probably makes more sense as a query parameter (&lang=en+hu) than as a
> path.
Yep, I'm adding a branch that makes that transition now.
On Fri, Dec 3, 2010 at 1:20 PM, Matthew Paul Thomas <email address hidden> wrote: ubuntu. com: ubuntu. com/reviews (or maybe that should be developer. ubuntu. com/moderate? )
> In my current sketches, developer.
> * lets moderators moderate reviews - developer.
Either of those would be fine (out of those options, I'd prefer reviews/ 2/, moderations/ 3/ etc.).
/reviews/ as it better encapsulates what the app is about -
reviews+moderation - even if it means urls like /reviews/
/reviews/
Going slightly off-topic (perhaps something for the Monday call), but ubuntu. com at center. ubuntu. com be a better long-term
why do we want reviews+moderations to be at developer.
all? Wouldn't software-
location (especially if the web app eventually exposes reviews via the
UI - for whom the target audience would not be developers, but even
just for the moderation functionality, which is not developer specific
like the other resources you've listed below.
> * lets developers submit applications, track their submissions, and see installation stats (and eventually reviews) for their published applications - developer. ubuntu. com/status ubuntu. com/kb.
> * lets anyone browse and search a knowledge base about developing on Ubuntu - developer.
>
> It shouldn't be particularly common for moderators to be developers, so
> there's no particular need for them to stay signed in between the first
> application and the other two, but there's no particular need for them
> *not* to share credentials either.
>
> Most of the time, it won't be relevant to a moderator what Ubuntu
> version or package they're moderating for: they'll just go to the
> moderation app's base URL and be presented with a global list of flagged
> reviews, most-flagged first. The main thing that they'll want to filter
> on is language, and some moderators will be multilingual, so that
> probably makes more sense as a query parameter (&lang=en+hu) than as a
> path.
Yep, I'm adding a branch that makes that transition now.
Cheers,