> Luke, curious if y'all had discussed separate Jira projects. > Atlassian > themselves (and JetBrains when they used to use Jira) and others use > this set up for the same reasons as your proposal. Essentially you > have one non-blessed Jira project where users can still come create > issues. But you have another project that defines issues the Gradle > team works. There would be a manual process on your part to move > issues from one to the other. Your forum integration could write > directly to the blessed one, since you already had eyes and hands on > it. In terms of moving, the act of moving itself is a sort of > "accepted signal". Just another option...
Hmmm... more complications. Instead of one Jira and one forum, that makes it *two* Jiras and one forum. That's three things to keep an eye on and manage instead of 2 :-) Kris PS: To the Gradle Team, I appreciate you throwing me a bone and offering me 'special' status to be able to create Jira tickest directly. That's cool, I'm flattered. But you don't have to do this unless it really makes sense to you. It is your process/tracker so your decision. I would not be offended if you think it would work better for you to create the issues yourself and have me post to the forum. ----- Original Message ----- > Yes, this clearly is intended to make life easier for the Gradle > team, > not you or me. And thats not necessarily a bad thing. > > Luke, curious if y'all had discussed separate Jira projects. > Atlassian > themselves (and JetBrains when they used to use Jira) and others use > this set up for the same reasons as your proposal. Essentially you > have one non-blessed Jira project where users can still come create > issues. But you have another project that defines issues the Gradle > team works. There would be a manual process on your part to move > issues from one to the other. Your forum integration could write > directly to the blessed one, since you already had eyes and hands on > it. In terms of moving, the act of moving itself is a sort of > "accepted signal". Just another option... > > > On Wed 15 Aug 2012 12:50:00 PM CDT, Kris De Volder wrote: > > Sure, I could still watch issues etc. the point is that in order to > > be > > able to 'raise' something and track progress of my 'pre-issue' upto > > the > > point it gets promoted to an 'issue' I have to now use a different > > tool. > > > > I don't really see that as a simplification but as a complication. > > (Two tools is more complex than one tool). > > > > I do understand the idea to try and keep 'garbage' separate from > > 'issues'. > > I just don't see why that can't be done within the Jira tracker. > > Jira is not perfect, but it does provide many ways to manage and > > distinguish issues. > > So what problem is making me go to the forum going to solve that > > you couldn't also solve by using some kind of tagging scheme in > > Jira? > > > > Anyway, its really not up to me. If you guys think doing a > > filtering > > at the forum level is the way to go, that's entirely up to you. > > I'll try to follow > > the process that you guys think is best for you. > > > > If it means I have to post my issues to the forum going forward > > that is fine. > > I think I can live with that :-) > > > > Kris > > > > ----- Original Message ----- > >> Not advocating either way, but none of your arguments really hit > >> on > >> the > >> intent of the proposal. > >> > >> You would still have access to Jira, if I am understanding Luke > >> correctly. The thing the Gradle team is trying to get out of is > >> the > >> creation of garbage basically. Duplicate issues, non-issues, etc. > >> As > >> I understand it, they want to be able to screen potential problems > >> *before* they get into Jira. So you'd still have access to Jira, > >> just > >> not to create issues directly. You would still watch/vote/etc in > >> Jira > >> directly. > >> > >> > >> On Wed 15 Aug 2012 11:24:12 AM CDT, Kris De Volder wrote: > >>> I'm not a big fan of forums myself. For reporting problems and > >>> tracking the status/progress I really think Jira issues is much > >>> better. > >>> > >>> Sure Jira is not perfect, but it lets you tag things as > >>> 'duplicate', 'user error', etc. And they allow you to see what > >>> release it is targetted for, if someone is assigned to it, if it > >>> has been resolved etc. > >>> > >>> A forum is just a collection of threads with none of these > >>> features. I just don't see myself 'filing' issues by going to the > >>> forum. > >>> > >>> BTW: I have not yet signed on to the forum. I already have enough > >>> different places to go to to check for new stuff on a regular > >>> basis. And like I said, to me the Jira tracker seems like a > >>> better > >>> place to keep an eye on the issues that affect me. > >>> > >>> Kris > >>> > >>> ----- Original Message ----- > >>>> If you're interested in this, please read: > >>>> http://forums.gradle.org/gradle/topics/8xl1i3rqvg7yz > >>>> > >>>> Feel free to comment here if you are adverse to posting on the > >>>> forums. > >>>> > >>>> -- > >>>> Luke Daley > >>>> Principal Engineer, Gradleware > >>>> http://gradleware.com > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe from this list, please visit: > >>>> > >>>> http://xircles.codehaus.org/manage_email > >>>> > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe from this list, please visit: > >>> > >>> http://xircles.codehaus.org/manage_email > >>> > >>> > >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
