Well, I hope I'm still a committer - I wrote a fair bit of WIAB when we were moving away from google. Its ancient history now, but I wrote most of the database code in WIAB, the authentication code, the login & logout pages and status toolbar. I also wrote some tests for the search indexing iirc & apparently not currently used snapshot code.
You can run this to see what I'm a file author on, although apparently I'm still gen...@google.com sometimes. $ grep 'author.*Joseph Gentle' -ri . | grep -v svn I probably just never got around to submitting an ICLA years ago when we moved across to apache. I'll send one through now. -J On Fri, Jun 14, 2013 at 4:02 PM, Upayavira <u...@odoko.co.uk> wrote: > In which case, Joseph should send in an ICLA, and we can get the account > sorted. Thx for spotting Yuri. > > Upayavira > > On Fri, Jun 14, 2013, at 11:39 PM, Yuri Z wrote: >> By the way Joseph, your name is on the list of committers for the Apache >> Wave http://incubator.apache.org/wave/people.html , 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 <u...@odoko.co.uk> 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: http://www.apache.org/dev/new-committers-guide.html#cla >> > >> > 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: >> > > https://svn.apache.org/repos/asf/incubator/wave/experiments >> > > >> > > Thoughts? >> > > -J >> >
