On Mar 26, 2015 11:04 AM, "Brian Wolff" <bawolff(a)gmail.com> wrote:
On Mar 26, 2015 9:58 AM, "MZMcBride" <z(a)mzmcbride.com> wrote:
>
> Hi.
>
> Moushira Elamrawy wrote:
> >The Extension will keep the name Gather and internally the team was
more
> >inclined to name the feature
"Stacks". However, a survey study has been
> >carried out by the design research team and Collections, as a name for
a
> >feature, scored far better than the other
suggested alternatives. Full
> >survey information and results are documented here
> ><https://www.mediawiki.org/wiki/Extension%CB%90Gather/renaming_survey>.
>
> Right... in the January 2015 thread you linked, it was quickly pointed
out
that
Extension:Collection already exists. The mobile team, in typical
form, decided to ignore any previous work and instead make its own
project. At least we were able to shout loudly enough to stop this
functionality from being part of the MobileFrontend extension.
Hey, count your blessings its not called "collections" with just an s at
the end to distinguish it...
> >This is a new experiment in content curation, which hopefully helps
with
> >learning new users behavior on mobile web. We
are looking forward to
> >learning awesome lessons from this beta launch.
>
> As was also previously pointed out, we've had curation support for a
long
> time in the form of categories (another feature
that could have been
> improved rather than making a new extension). Or making a list of pages
> using wikilinks. Or tagging pages with templates, which auto-generates
an
> index. Perhaps you can explain why this new
feature is limited to
mobile?
I dont know if this criticism is fair. Many users have been asking for
multiple
watchlist type functionality for years despite the option of
creating a subpage or category and throwing special:recentchangeslinked.
Categories dont really have per user namespace, and i think its important
to have interfaces that encourage users to do this sort of thing rather
then making them figure out that they are physically able to and allowed to.
I do agree that its odd that this isnt developed in core for all users.
The faq
entry is unconvincing.
--bawolff
Actually after reading the extension page, I'm a little confused. If the
goal is to create private personal lists why are the lists public? I can
understand the use case for private lists (watchlist). I understand the use
case for public lists (categories). What is the use case for pseudo-private
lists?
Maybe it will make more sense to me when the extension is deployed and I
see it in action.