Thanks everyone so far for the positive feedback.
I'll make a start then and create a sandbox project for this purpose.
Furthermore, I'll provide more detailed information about each planned task,
over time and otherwise related discussions.
As I mentioned earlier, I'd like to use a wiki to keep better track of these and
other discussions, but will wait until we graduated before ask infra to set one
up. As soon as we'll have a wiki I'll transfer the relevant info from the mail
threads.
I have another suggestion with respect to how we should 'track' sandbox related
work through JIRA, but will start a separate thread for that shortly.
Regards, Ate
On 03/19/2012 03:06 PM, Hadrian Zbarcea wrote:
+1. This is an excellent idea and one of the paths I always thought Rave would
follow eventually anyway.
Hadrian
On 03/16/2012 05:40 AM, Ross Gardler wrote:
On 15 March 2012 09:02, Ate Douma<[email protected]> wrote:
So, we've decided to go about the other way around: to start from scratch
within Rave itself. This also allows and invites the Rave community to
participate from the start, for a more agile process and better alignment of
architecture and functionality. But we can still use Hippo HST, which is
open-source and available under ASL 2.0 license, as example and reference
for this purpose.
I make no comment on the technical aspects of this contribution, I've
not spent the time to understand it fully. However, I want to thank
you for not proposing a large code donation and instead bringing your
expertise to the community in the way described. I wouldn't have
objected to the code donation, but this route means that the community
is able to see the work progress and thus more likely to be able to
take full advantage of it (and hopefully contribute to it).
+1 to the proposal
Ross
