I've already taken some initiative here, Bruno. Most of what I've added are things that Google and/or other large integrators have an immediate production need for (and these are assigned to either myself or fargo), but I've also added several things which will significantly improve the overall platform without any specific deadline or assignee. I'd really love it if anyone who has the free time could give feedback on these latter proposals (if you want to implement it it's even better!)
I'd prefer to not be surprised by major code changes. Knowing in advance that someone was working on some major component will make preparing for change a lot easier. It will also help with coming up with release objectives when we get out of the incubator stage. ~Kevin On Jan 20, 2008 4:46 PM, Bruno Bowden <[EMAIL PROTECTED]> wrote: > Echoing Kevin's comments, we'd like to encourage people to use JIRA for > project tracking, as well as bugs. So please add issues for the work > you're > planning yourself and add or vote on other work you care about. This will > help in discussing upcoming work and planning priorities. We'd like to > avoid > the situation where we're surprised by big code changes that we weren't > aware of. > > New Account: > https://issues.apache.org/jira/secure/Signup!default.jspa<https://issues.apache.org/jira/secure/Signup%21default.jspa> > > Shindig Issues: > https://issues.apache.org/jira/browse/SHINDIG > > > On Jan 20, 2008 1:46 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > Hi everyone, > > > > I went ahead and added several components to shindig on the jira tracker > > to > > help ensure that issues are properly tracked and categorized. Please > start > > using these components when you open tickets, and let me know if there's > > anything that I overlooked. > > > > I also noticed that we don't have SVN integration enabled. Does anyone > > know > > if this is available, and if so, how to make it work? > > > > Thanks, > > > > ~Kevin > > >
