incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuri Z <>
Subject Re: Adding experiments into the repository
Date Fri, 14 Jun 2013 22:39:30 GMT
By the way Joseph, your name is on the list of committers for the Apache
Wave , You might want to make
request to the infra to claim a username so you will be able to handle the
experimental related issues by yourself.

On Fri, Jun 14, 2013 at 11:00 PM, Upayavira <> wrote:

> At this point, **all** code should be exempt from code review.
> To explain in more detail, there's two models a project can follow:
> = review then commit =
> Mature communities usually follow this, when there's substantial risk in
> making chances. Wave is way to young for this, IMO.
> = commit then review =
> This is what I'm used to. Make a commit, and have other developers watch
> the commit list. They can object on the dev list if they see something
> they don't like, but the basic assumption is that, if you have commit
> rights, we trust you.
> So I would say, yeah, create a sandbox area in SVN. Have as many play
> areas as folks want. Those can be clones of the WIAB code, or can be
> completely fresh directories.
> As a start, I'd say, anyone who'd like to participate in such
> experiments should submit an ICLA to Apache. This is a legal document
> stating that you give a license to Apache to the code that you provide
> (but you still retain copyright).
> See here:
> Whilst this doesn't grant you commit rights to the repo, it is certainly
> a prerequisite, and will ease the inclusion of your code into the
> repository. If you do send your ICLA as suggested in the above link,
> feel free to mail me privately and I will track its arrival.
> Upayavira
> On Fri, Jun 14, 2013, at 08:49 PM, Joseph Gentle wrote:
> > Following from Michael MacFadden's suggestion to put related
> > (hopefully integrated) technologies into the same wave repository, I
> > propose adding an experiments directory into SVN. (Do we vote on this
> > or something, or should I just do it?)
> >
> > Experimental code should be exempt from code review, although there
> > should be an expectation that unused experimental code may be cleaned
> > up if it isn't actively worked on for more than 3 months or so. I want
> > a place where we can collaboratively iterate on fresh ideas & design.
> > We want to produce things that are eventually useful to the wave
> > project.
> >
> > I think we should place experiments outside of the trunk directory, here:
> >
> >
> > Thoughts?
> > -J

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