why don't you include the Jira link in the thread D.
On Thu, Apr 23, 2009 at 4:34 PM, Anne Kathrine Petteroe <[email protected]>wrote: > I think documenting the current code should be on top of our list. > I have created a task in Jira for it. > > /Anne > > > > On 22. april. 2009, at 08.48, Richard Hirsch wrote: > > I actually tried to do some Scala work in ESME but without documentation I >> was lost pretty fast. >> >> D. >> >> On Tue, Apr 21, 2009 at 10:11 PM, Vassil Dichev <[email protected]> >> wrote: >> >> Does anyone have suggestions, how Apache ESME can use this interest to >>>> increase its community? >>>> >>> >>> I think the best part is that we don't need to do anything different >>> than what we have to do anyway :) >>> >>> I have a few ideas: >>>> >>>> - A guide to how to use ESME to learn Scala -- (@Vassil - do you have >>>> ideas?) >>>> >>> >>> Popularity surge or not, this might be a good idea; of course it has >>> to be adapted to ESME's concepts. >>> >>> - A few tips to try out on a local ESME installation to learn Scala. >>>> "Hello World" experience with ESME. >>>> >>> >>> A very interesting idea would be to use different components from ESME >>> to create e.g. a Twitter bot; some of the code from ESME actions was >>> initially reused by a standalone bot which feeds items into ESME. >>> >>> - Better documentation in our existing Scala code (look here for a >>>> >>> better >>> >>>> example - >>>> >>>> >>> http://scala-tools.org/mvnsites/liftweb/lift-amqp/scaladocs/net/liftweb/amqp/AMQPDispatcher.scala.html >>> ), >>> >>>> so that beginners have an idea what we are doing in our code base. >>>> >>> >>> - More PR work to point people to the Apache ESME site. >>>> >>> >>> Absolutely- but I feel before we need to point hordes of potential >>> developers to our site, we should have something more presentable :( >>> maybe not a requirement for a motivated developer if they see promise, >>> but nevertheless finding out easily how to get started could come a >>> long way. >>> >>> >
