The following is Vernon Cole' response to James Henstrige's response to Vernon...<br>[...]<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The big difference<br>
between Storm and the other projects you've mentioned is that Storm<br>
does not have any full time developers: instead it is infrastructure<br>
used by a number of Canonical projects (Landscape, Launchpad and<br>
UbuntuOne). This means that most of the contributions you see from us<br>
are driven by the needs of those projects (although we do try to<br>
review and merge changes from others).<br>
</blockquote><div><br>Thanks. That explains a lot. There is no "storm team" as such, so nobody has dedicated time for just that project. Things are clearer now.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I think we can do better than we have in the past though, which is why<br>
I started this thread. I don't expect community members to have a<br>
higher commitment to the project than us (if they are hacking on<br>
Storm, it is most likely to support one of their own projects too),<br>
but I'd like to see that effort put into the trunk.<br>
<div class="im"></div> <br></blockquote><div>I agree. My personal project would require a major enhancement in the base code to really work well. It would not exist viably as a fork. This discussion gives me hope that I could actually do it. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
> I personally felt quite a cold reception [...]when I submitted an attempt to<br>
> make the tutorial more approachable. This has made me hesitate to make other<br>
> contributions.<br>
<br>
</div>The problem with that branch was that it changed the tutorial from<br>
what we'd consider idiomatic Storm use to a form we would not<br>
recommend new users use. If you took this as personal criticism<br>
rather than criticism of the change, I am sorry about that: it wasn't<br>
intended. If you peruse the past bug and review comments, you'll find<br>
criticisms of pretty much every Storm developer's code.<br>
</blockquote><div><br>Criticism is what reviews are for. I have been doing code reviews since the late 1970's, so I understand that. In a very real way, my submission was itself a criticism. IMHO the tutorial really sucks -- err -- that is to say -- is difficult for a person totally unacquainted with storm to understand. I could not understand it at first, so I added training wheels until it made sense to me. <br>
I realize that my changes reduced the value of the tutorial as sample code. On the other hand, if a newbie cannot get through the tutorial, he or she will never need sample code.<br> The point is that I stuck my nose in, as an outsider, to a group who didn't know me, and suggested a major change in style in one particular area. Most groups would react badly to that, so I expected some negative feedback. When the feedback seemed totally negative, and terse as well, I figured that my suggestions would always be unwelcome, I packed up my stuff and went back home. Apparently I misinterpreted. I will make another try.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
[...]<br>
James.<br>
</blockquote><div>--<br>Vernon <br><br></div></div>