<br><div class="gmail_quote">On Thu, Apr 8, 2010 at 10:01 AM, Ramdas S <span dir="ltr"><<a href="mailto:ramdaz@gmail.com">ramdaz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<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"><snip></blockquote><div>----------- <br></div><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
Can we look at a growth in terms of percentage over last year, and continue targeting that way year over year?<br>
<br>
<br>
Some quantifiable targets<br>
#########################<br>
<br>
1) Let's say a 100% plus increase in sponsorship money ( would love 200,300,400%)<br>
<br>
2) Get 20% or more attendees.<br>
<br>
3) Have 20-40% more number of talks<br>
<br>
4) Get a couple of well known speakers<br>
<br>
The trick here is to find out which all prominent Python developers
work with companies with an interest in India or manage teams in India,
and get the companies to adjust their visit to coincide with India.<br></blockquote><div><br>Similarly how can you improve the overall quality of conference. Better Talks, more interactive sessions. Can we have code jams?<br>
<br></div></div></blockquote></div><snip><div><br></div><div><div>I think we were getting distracted by RubyConf or such other events that might have occurred at a grander scale with corporate backing. </div><div>
Though I am someone almost alien to the Ruby world but I think Ruby did gain great popularity majorly due to Rails and the way Rails has been promoted. Besides Rails started in a company itself - 37signals.</div><div> Since Rails is the back-end for some successful projects like basecamp, github, etc, its bound to get popular among big players once small ones have tested, tried and shown that it works.</div>
<div> I agree to starting small and growing the community and the conference gradually in smaller sustainable steps, rather than fixing a huge milestone and not completing it in good quality. Lets keep statistics of last year as base and try to grow it further in all aspects as suggested by Ramdas. That would really turn us into the direction of a stronger community.</div>
<div> As for hackathons/sprint sessions, I think in Python there's a lot of room for such events. I really loved the way a whole floor was dedicated for such activities at FOSS.in. In our case maintainer of a package or a core-developer or anyone really involved, could setup a small bench-camp, get interested people together, introduce them to what, how and why's and complete some tasks (squashing bugs, finishing some todos, adding new features, etc). </div>
<div> This would greatly help us in breaking the barrier of doubts, confusions and lack of information that every new "possible contributor" faces these days. In a sense InPyCon would not only result in promoting Python to newcomers but also in adding new developers to the Python Community itself.</div>
<div> </div><div>People say "Do one thing and do it well"... lets do it that way.</div></div><div><br></div><div>just a few thoughts,</div><div><br></div><div>Abhishek</div>