Hi Wayne, I wouldn't say that the scope has drifted, but it has expanded to new fields that are not captured by the old name and scope description. With the support for alternative RAP clients, the focus of our work has also shifted and the remote aspect of RAP is more central now. Looking at the text on the project page, I think this should also be updated.
I will try to describe the changes in a document as you suggested and also draft an update to the project description. Thanks, Ralf On Mon, Sep 24, 2012 at 10:44 PM, Wayne Beaton <[email protected]> wrote: > ** > Can I safely assume that there's been some scope drift in the project? > > The project scope--lifted from the original proposal--is displayed in the > project page [1]. > > I'm not concerned with wording changes; if there are substantive changes > in the scope (or name), the EDP requires that we engage in a restructuring > review. Nothing particularly complicated is required: a document that > describes the changes and one week for community review is all that is > necessary. > > Wayne > > [1] http://projects.eclipse.org/projects/rt.rap > > > On 09/24/2012 02:12 PM, Ralf Sternberg wrote: > > Hi everyone, > > When the RAP project started 6 years ago, its main objective was to > provide a framework to make RCP applications available on the web. The > resemblance of the name "Rich Ajax Platform" to "Rich Client > Platform", was welcome back then as RAP was meant to complement RCP. > But over time, our focus has moved to more lightweight applications > and alternative clients like tablets and phones. Today this name does > not describe our project very well anymore. The term "rich" does not > reveal much information in itself and "Ajax" does not fit well for the > native clients, even though they still use HTTP. Ajax is more a > buzzword than a concise term anyway and as a buzzword, I think Ajax > has lost its appeal. > > I recently found myself explaining RAP more often as a platform for > "remote applications" and I think this describes the idea very well. > It's essentially a platform for applications that run on a remote > server. With the new protocol and the alternative clients, this aspect > seems to become the central part of RAP. > > Therefore I'd like to propose to relabel RAP to "Remote Application > Platform". This name would let us keep our short name, our namespace, > our website, etc. It wouldn't be a very noticable change, but we'd get > rid of the misleading name and highlight our technical approach > better. The 2.0 release in February 2013 may be a good occasion for > this renaming. > > What do you think? > > Ralf > _______________________________________________ > rap-dev mailing > [email protected]https://dev.eclipse.org/mailman/listinfo/rap-dev > > > -- > Wayne Beaton > The Eclipse Foundation > Twitter: @waynebeaton > Explore Eclipse Projects <http://www.eclipse.org/projects> > [image: EclipseCon Europe 2012] <http://www.eclipsecon.org/europe2012> > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev > >
<<480x60_0.png>>
_______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
