RIFE roadmap?

[Ravi]

RIFE Devs,

I have been evaluating RIFE for the past couple of months and I am
very happy with the features and the community. I think this project
deserves much more publicity than it gets!

Now that I am doing a write-up to management to make this our de-facto
web app framework, I'd like to understand if there is a roadmap for
future releases with features? I see that the last release was July
2007 and haven't seen any new posts to the announcements list of late.

Can somebody give me an idea of where RIFE is going and what new
features are planned.

Thank you Geert and team for a wonderful tool!

Ravi

[Geert Bevin]

Hi Ravi,

thanks a lot for your nice words. RIFE has been dormant for 6 months
since some of the key users and me have had a couple of very busy
months in real life (family stuff and such).

I've picked development back up a couple of weeks ago.

These are the changes that are still pending to come out with the next
release 1.6.2 (hopefully next week):

* moved to the Apache 2 license
* upgraded the support for all the 3rd party scripting languages,
libraries and databases to their latest versions
* RIFE-89 : Add support for custom error handling
* RIFE-304 : Allow exit/submission names to be references to Java fields
* RIFE-315 : Support annotation to specify meta data class
* RIFE-284 : Please include a TemplateWrapper class
* RIFE-255 : add option bundlename to the L10N:key tag
* RIFE-316 : Pathinfo inputs aren't preserved in the URL during
behavioral inheritance
* whole bunch of continuations related bug fixes

(see here http://uwyn.com/issues/browse/RIFE for the issues in detail)

I'm still planning of wrapping up RIFE-238, RIFE-294 and RIFE-290
before the next release.

After that I'm thinking of integrating RIFE/Crud into RIFE itself and
adding a non-HTML XML view that thus generates RESTful responses. This
means that RIFE can be used for instance RESTful service creation
through beans and a simple site declaration.

Next thing I'm going to look at is rewriting the template parser since
it's a bit slow now. I'm also going to work further on the
continuations support so that it can work in multiple methods in a
class and release RIFE/Workflow as a first stable release.

So you can see ... many things are coming :-)

Thanks for the interest,

Geert

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

[ravi2boxster]

RIFE Devs,

I have been evaluating RIFE for the past couple of months and I am very
happy with the features and the community. I think this project deserves
much more publicity than it gets!

Now that I am doing a write-up to management to make this our de-facto web
app framework, I'd like to understand if there is a roadmap for future
releases with features? I see that the last release was July 2007 and
haven't seen any new posts to the announcements list of late.

Can somebody give me an idea of where RIFE is going and what new features
are planned.

Thank you Geert and team for a wonderful tool!

Ravi
--
View this message in context: http://www.nabble.com/RIFE-roadmap--tp16992752s9330p16992752.html
Sent from the RIFE - users mailing list archive at Nabble.com.

[E L]

Hi,

I've been on this list for a while to gauge the seriousness of the project and a stated roadmap on the rife site would be very very helpful.

Geert - you're awsome - but corporations are very worried about using an open source project that is supported by only one person.

El

[Geert Bevin]

Hi Ravi,

seems you re-sent this email from 2 days ago. Did you receive the
reply I sent before?

If not, it's here:

http://groups.google.com/group/rife-users/browse_thread/thread/8901af3eef27bcb2

Best regards,

Geert

--

[Geert Bevin]

Hi El,

Jira is basically the public roadmap. Not everything on their
incorporates what I am planning, but that's also because I don't want
to commit to everything that I might be planning ;-)

I know that corporations are worried about this, and sadly there's not
much I can do about it. I know there are many things that can be
improved such as more coherent documentation, better targeted
examples, articles and stuff like that. In the end it comes down to
the fact that, yes, I'm the only person still dedicating my time to
the project.

El and others, if you think that the RIFE project itself is worth
getting some more attention and be taken more seriously, the best
thing that you can do is start contributing! You probably don't
realize it, but it's new users that can do the most good. It's easy
for you to identify where the pain points are and where the framework
it's difficult to understand. Since the wiki is open for everyone, you
can just write and/or rearrange what you think seems appropriate. The
same goes for the static texts on the non-wiki site. Feel free to send
me better versions or additional content, and I'll put it up.

In short, the best way to revitalize this project is not to wait for
it to happen, but instead to be one of the catalyzers. Even the
smallest of efforts can motivate others to do the same.

Thanks a lot for speaking up though, for a while I feared that nobody
might be interested anymore and that my efforts were all wasted. Now I
know this is not true.

Kind regards,

Geert

--