[Labs-l] Visibility of tools

[Ryan Lane]

On Wed, Feb 20, 2013 at 8:07 AM, Platonides <platonides at gmail.com> wrote:

> On 20/02/13 16:02, Harry Burt wrote:
> > On Wed, Feb 20, 2013 at 2:54 PM, Marc A. Pelletier <marc at uberbox.org
> > <mailto:marc at uberbox.org>> wrote:
> >       I think an important part of this would be to have a Wiki where
> > the mainspace is the tools' information and description.  I wouldn't
> > even want to limit it to Labs-hosted tools; there are plenty of
> > community developers that cannot or do not need to be hosted at the labs
> > whose work is nevertheless valuable to the projects and would deserve
> > being known about.
> >
> > As you may be aware Coren, the Toolserver has tried to maintain its own
> > list of tools in the past, and indeed still maintains an amount of
> > documentation on the Toolserver wiki. Note that the main issue is not
> > the availability of a space, it's whether tool developers can be
> > bothered to document their own tools. Whether they can be bothered is
> > itself a factor of traffic: at the moment, I think most Toolserver
> > developers see the primary discovery route to be via their local wiki,
> > rather than a central one. I don't expect that to change.
>
> If we follow the idea of one project per tool, we can make a list with
> each tool, there could be an automatic at the root, so that even if
> there's no description for one tool, at least it shows its existence.
>
>
One project per tool is too much. It splits up access and infrastructure
too much. It seems we'll be making one user per tool (see bug 45119). We
can automatically create a documentation page when a tool user is created.
We can then turn those users into a list of tools automatically using SMW.

- Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/labs-l/attachments/20130220/50bc657d/attachment-0001.html>