[Labs-l] Install tools for production-purpose only

[Ryan Lane]

Things like this would be considered a semi-production tool. We only
prohibit running things in a production way like wikis or something that
should live in production because it would need to have production like
uptime (like something critical to running the sites or associated
processes).

If others may wish to use this for tools, it may make sense to run this in
the webtools project.

- Ryan




On Sat, Dec 22, 2012 at 10:34 AM, Seb35 <seb35wikipedia at gmail.com> wrote:

> Hi,
>
> I would like to know if it is permitted to install on the Labs tools which
> could be useful for Wikimedia activities but without having in mind to
> develop the tool. I searched a bit on archives of the list and on the wiki,
> but didn’t found anything related.
>
> The specific case is the installation of OpenRefine [1][2] (ex Google
> Refine) useful to manipulate data, for instance GLAM metadata --
> specifically here for a cooperation with a museum in Belgium but it could
> be for any data manipulations.
>
> OpenRefine is a web tool in Java+Python which listens on a specific port.
> It is originally intended to run on the local computer. It seems it don’t
> use many ressources for a single user.
>
> So is there any rules regarding the general case? And if it is
> case-by-case, is there a checklist for a specific tool (security,
> ressources, environment, etc.)?
>
> [1] https://en.wikipedia.org/wiki/**Google_Refine<https://en.wikipedia.org/wiki/Google_Refine>
> [2] https://github.com/OpenRefine/**OpenRefine<https://github.com/OpenRefine/OpenRefine>
>
> Thanks,
> ~ Seb35
>
> ______________________________**_________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/**mailman/listinfo/labs-l<https://lists.wikimedia.org/mailman/listinfo/labs-l>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/labs-l/attachments/20121222/16f317ea/attachment.html>