Committership is earned through participation. The barrier is not high,
I'd say your open engagement with the community so far is an excellent
start, however, we do need to see a few patches via the issue tracker
first.
There's also some legal and infrastructural to go through before someone
can have commit access so even if we were to vote you in as a committer
it would take a little time.
Please provide a patch via https://issues.apache.org/jira/browse/WOOKIE
Please remember smaller incremental patches are much easier to review
and thus get processed more quickly.
(if you need any help creating the patches let us know)
OK, I didn't know that committing is undergoing such a formal process. I
just thought in terms of simplicity and speed :-)
So, I have provided a patch and put it on the issue tracker (I hope I
did it the right way, otherwise just correct me please).
BTW: For our project LTfLL (www.ltfll-project.org) I designed a
widget-template which includes libraries for easy handling of shared
data and for receiving updates - especially targeted for using IWC with
Wookie and the coupling widget features provided as the patch. Maybe it
is of some use to anybody because we set up some routines to handle
shared data (e.g. not only as strings but also as JSON objects). There
are a few issues when using IWC the way we are using it (all widgets of
one user). So to minimize network traffic you can specify that widgets
only listen to some shared data variables or by using JSON objects we
store everything as one shared variable and are using a namespace
metaphor. This means that a widget gets bound to a certain namespace and
only reacts on updates therein. Just as a quick glimpse what we are
trying to get to work ... Again, if somebody is interested in such stuff
as well just contact me.
-Bernhard
