rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Franklin <m.ben.frank...@gmail.com>
Subject Re: [DISCUSS] Project Next Steps
Date Thu, 17 Apr 2014 15:41:33 GMT
On Thu, Apr 17, 2014 at 11:13 AM, Chris Geer <chris@cxtsoftware.com> wrote:

> Ross,
>
> I'm using Chef to deploy Rave today, it wouldn't be hard to take that and
> convert it to be Vagrant based I suppose. Would people use that if I build
> it?
>

We use Vagrant to test our chef scripts.  It would be great if we had a
Vagrant config available that pulled down a VM, setup Tomcat and looked for
the war's & gadgets in the source directory to serve out.  This would
significantly lower the barrier of getting started building on Rave.


>
> Chris
>
>
> On Thu, Apr 17, 2014 at 7:48 AM, Ross Gardler <rgardler@opendirective.com
> >wrote:
>
> > I did a session at Apache on on using Vagrant as a community development
> > tool (short version, produce VM images for cloud providers, use then to
> > provide live demos, personal demos, dev environments).
> >
> > When writing the session I tried to use Rave as the case study, but the
> > installation failed. I didn't have the time to debug so went with Solr
> > instead.
> >
> > Would the team be interested in a Vagrant + Puppet configuration to do
> > this. I'll need someone more current than me to help me figure out the
> > installation problem. I probably will not maintain the scripts as I'm no
> > longer using Rave.
> >
> > It has the added benefit of ensuring all devs are on the same environment
> > for build and test (although Vagrant + Puppet also makes it easy to
> create
> > VMs using different base OSs).
> >
> > Ross
> >
> >
> > On Thu, Apr 10, 2014 at 14:51 PM, Matt Franklin <
> m.ben.franklin@gmail.com
> > >wrote:
> >
> > Many of us met at ApacheCon NA to discuss the project and what needs to
> be
> > done to move it forward.  From this discussion, it was clear that the
> major
> > thing we need to work toward is growing the community.  The purpose of
> this
> > thread is to discuss what we can do from both a technical and
> non-technical
> > standpoint to attract new members.
> >
> > The first barrier to entry that was discussed is the complexity of
> getting
> > started with the project.  To combat this issue, the following technical
> > actions were proposed:
> >
> > 1) Complete the API refactor.  Moving all operations to the new CXF REST
> > APIs will allow for simpler integrations and customization from the
> client
> > side without having to overlay or add Java code to Rave.
> >
> > 2) Complete the Angular front end.  The JSPs are convoluted and difficult
> > to customize.  Having a simple to modify UI framework greatly decreases
> the
> > barrier of entry.
> >
> > 3) Create a new Angular widget provider that simply does angular includes
> > of content inline in the page.  This allows users to get started without
> > having to understand OpenSocial or W3C widgets.
> >
> > From a non-technical standpoint the following was discussed:
> >
> > 1) Outreach to other projects.  Many projects are developing their own
> > modular UIs.  We should help them use Rave once we have completed
> lowering
> > the technical barrier.
> >
> > 2) Website/Documentation.  We need to rebrand and clarify what Rave is
> all
> > about.
> >
> > Let's discuss these and other options and put a prioritized list out for
> > discussion with the wider community on the user's list.
> >
> >
> >
> > --
> > Sent from MetroMail
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message