Very good points Lewis, you are totally right about this. Two things. First, we're still waiting for Infra to import our existing JIRA issues -- we need to find a way expedite that or bite the bullet and import them ourselves "manually" somehow.
Second, the work in the two-dot-o branch has all been focused around a new module called "Core Persistence" which is a rewrite of the internals of the Usergrid Entity Manager. This is covered by some of those waiting JIRA issues, but this is a big enough change that really need a proposal that introduces and explains Core Persistence so we can get community feedback and enable folks to help out with development. I'm working on writing such a proposal/summary and hope to share it in the next week or so. - Dave On Thu, Jan 23, 2014 at 10:14 AM, Nate McCall <[email protected]>wrote: > I think we have a pile of issues in an export from Apigee's internal jira > lingering in an INFRA ticket somewhere. Rod? > > That said, I agree that we need some more discussion on some of this - at > least have it in Jira - before a big set of changes comes in. > > > On Thu, Jan 23, 2014 at 12:03 PM, Lewis John Mcgibbney < > [email protected]> wrote: > > > Hi Folks, > > I'm curious as to what the commits are on list? > > I've now subscribed to commits-digest@ in an attempt to cut down the > > traffic and I'm getting around 10 commits emails a day! > > Are we using Jira for anything? > > What code base(s) are folk actually working on? > > I think we need to come to some kind of consensus amongst ourselves as to > > what Apache Usergrid aims to become now, also in what direction the > project > > is going. > > I understand that some seem to be working on a 2.0 branch right now, > > however AFAICT little exists in Jira to back this up apart from an epic > > issue to which I have seen no sub issues attached. > > No issues are being logged in Jira and quite frankly I'm beginning to > lose > > control on where we are going with Usergrid right now... > > > > We have some clear objectives to get out of the Incubator. > > > > 1. Learning the Apache Way > > 2. Growing a diverse community > > 3. Getting project infrastructure and codebase setup at Apache > > > > IMHO it will become more difficult to get committers on board if commits > > are flying around all over the place. We also don't seem to have a > roadmap > > for our first incubator release. > > > > Anyone have comments on this? From my POV it would be excellent to see us > > tie in with 1 and 2 above sooner rather than later. > > > > Thanks for reading. > > Lewis > > > > -- > > *Lewis* > > > > > > -- > ----------------- > Nate McCall > Austin, TX > @zznate > > Co-Founder & Sr. Technical Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com >
