Ate,
thanks again for the nice welcome physically, and also digitally now... ;)
Since I (and maybe one of my students) have to become acquainted with
the code base first, I guess it would be a good first lesson to locate
where to introduce our code - I'm pretty sure plenty of questions will
arise from that, which I will post here. Thanks for the support!
Best,
Dominik
Am 18.06.2012 11:36, schrieb Ate Douma:
Hi Dominik,
I think I can speak for most if not all of the participants of the
Rave Hackathon that we enjoyed having you and Sten presenting the work
you've done on the ROLE project and especially the potential alignment
and contributions to Rave! I for one definitely look forward to such
contributions and further collaboration/participation of you and the
ROLE team with the Rave project.
The IWC feature you showed is very promising and looks like a very
good fit for Rave.
How this can be integrated, what exact amount of code is involved, how
the license and copyright requirements (on both sides) can be met,
etc. is a bit difficult to assess upfront, at least to me it is :)
As I know you got a trunk build of Rave working now, it would be great
if you can maybe try to get the IWC feature to work with Rave trunk
and provide us with an example (patch) to try out ourselves.
And possibly others here have time and interest to chime in and work
together with you on this.
Any takers?
Kind regards,
Ate
On 06/15/2012 05:13 PM, Dominik Renzel wrote:
Hi all,
after a nice Apache Rave Hackathon in Utrecht (thanks for having us
there), I'd
like to propose an extension for multi-user/browser interwidget
communication
for contribution to Rave, specifically referring to Epic RAVE-25.
Respective
code is already FLOSS and has been developed in the context of the EU
project
ROLE (Responsive Open Learning Environments; http://role-project.eu).
The slidedeck of our presentation in Utrecht is available from
http://www.slideshare.net/DominikRenzel/role-technologies-a-possible-contribution-to-apache-rave,
on slide 14 you find a compilation of online resources, including
documentation,
demonstration, and code.
My next step would be to find a reasonable integration into the
Apache Rave code
base, then create a respective issue (probably of type "story";
related to Epic
RAVE-25) and attach a patch to it.
Would that be acceptable? I'd be glad to hear your opinions.
Cheers,
Dominik
