[Labs-l] List of packages that are supported by tool labs

[Ryan Lane]

On Wed, Nov 13, 2013 at 12:44 AM, Merlijn van Deen <valhallasw at arctus.nl>wrote:

> On 13 November 2013 03:43, Andrew Bogott <abogott at wikimedia.org> wrote:
>
>> I can't understand.
>>
>>
>> I'm not really sure what would be a valid 'by hand' alternative to
>> puppet, as even if you ran 'apt-get install <whatever>' as root that would
>> only get your package on tools-login; not at all helpful for active tools.
>>
>
> It's not about puppet, it's about the response 'please jump through these
> hoops to get it done' instead of 'You're supposed to jump through these
> hoops, so I've done it for you this time', or (even better) 'It's done, and
> I have created a bug as reference'. Sending a 'create a bug in this
> component' link to a mailing list is roughly as much work as just creating
> the bug directly...
>
>
Bugs are more than just accounting and aren't there for bureaucracy. Bugs
are a way of allocating a segment of time from the incredibly overworked
operations engineers. If ops puts in tickets themselves it uses time that
could otherwise be spent fixing bugs or making things more automated and
self-service. It also breaks the relatively asynchronous process that comes
with bugs and turns it into a process that requires an immediate action (or
the risk of forgetting about the request).

We're a community. In Labs a lot of the workload is shared by volunteers
(in fact, it was the original point of Labs). Feel free to add a bug on a
fellow community member's behalf. You'll be helping the ops and the other
community member, which makes our community stronger.

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