[storm] Moving Storm Forward

[Gustavo Niemeyer]

Hi Vernon,

> Storm seems to suffer from a Canonical-centric attitude. (If Canonical does
> not need it, we're not interested.) This is almost never seen in other
> Canonical projects like bazaar and launchpad.

This is a quite unfair statement.  All of these projects, and even
more noticeably with Launchpad and Bazaar, try *very* hard to adapt to
the most common practices across software projects everywhere.  One of
the known things about Bazaar is that it's able to handle many
different kinds of workflows (people sometimes even criticize it
exactly for that).

Going back to Storm, one of the reasons you feel this way may well be
my fault.  I've tried very hard since the beginning of the project to
keep the scope under control.  Among other reasons, having a clearly
defined and consistent base and making a good platform for building
upon is more important than trying to handle all possible use cases.

That said, this has nothing to do with Canonical vs. non-Canonical.
We've rejected (with reasoning) requests coming from Canonical
employees too.

>   I personally felt quite a cold reception when I submitted an attempt to
> make the tutorial more approachable. This has made me hesitate to make other
> contributions. The present discussion about storm <-> schema integration
> also hints at a keep-out attitude by the Canonical team. Perhaps Canonical
> management needs to give the team more time budget to consider outside uses
> of storm as well as internal use?

Again, this is not about Canonical vs. non-Canonical.  This is about
project scoping.  I've had pretty warm discussions with people from
Canonical which wanted to implement schema creation in Storm.  I
haven't watched the tutorial episode closely enough, but I'm curious
about why you feel you've had a cold reception.

And one more time: I'm not against schema creation per se.  I'm
against schema creation if it removes some of the benefits of Storm
which we value.  I won't go over the whole discussion here again,
since the list archive has more details about this than I can quickly
bring up now.

Rest assured that there's no such things as a "keep-out" attitude from
the Canonical team.  Most of us are long time open source developers
which work in a very distributed way even when working for Canonical,
and still participate in external projects.  Lack of time certainly
limits our ability to do certain things, both internally and
externally, but that's natural pretty much everywhere.

-- 
Gustavo Niemeyer
http://niemeyer.net