[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-dev
Subject:    RE: Jira for Velocity & Velocity Tools - Gier / Daniel?
From:       "Tim Colson \(tcolson\)" <tcolson () cisco ! com>
Date:       2005-03-31 17:47:34
Message-ID: 17B8C6DE4E228348B4939BDA6B05A9DC02963B () xmb-sjc-237 ! amer ! cisco ! com
[Download RAW message or body]

Say -- now that the infrathon is over, we could put in the request to
move from bugzilla to Jira... but still haven't heard from the other
"active" committers. (I use the word active loosely <grin>)

Timo


> ----- Original Message ----- 
> From: "Tim Colson (tcolson)" <tcolson@cisco.com>
> To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
> Sent: Thursday, March 17, 2005 6:23 AM
> Subject: RE: Jira for Velocity & Velocity Tools
> 
> 
> > Geir Magnusson Jr. and Daniel Rall are the other two active
> > committers.
> Geir / Daniel -- what do you have to say?
> 
> > One moment... am I reading this right that we need a PMC member to
> > add/delete users?  That's a major negative.  We should be as open as
> > possible - anyone should be able to submit or to read the
> > bugs with few  barriers.
> No worries -- you aren't reading it quite right. :-)
> 
> It's just like Bugzilla -- anyone can view issues. Registered 
> users can
> submit bugs.
> 
> The "administrator" which they recommend but do not require 
> to be a PMC
> member -- is simply the person who can add/remove users to the
> jira-developers security group. These folks would be the committers --
> which changes not all that often.
> 
> Jira permissions are multi-faceted. In order to, for example, have an
> issue assigned to you -- you need the "assignable" permission for that
> project. The projects can have different permission schemes and
> workflows* (in the enterprise version) which allow you to 
> setup whatever
> flow suits the project best. For example, some orgs I've been at will
> send all new bugs to the QA Lead, who assigns to a QA person, 
> who checks
> for duplicate issues and then tries to reproduce the bug. Then they
> assign back to the Project Mgr, who determines priority, and 
> assigns the
> bug to a developer. And on and on until resolution.
> 
> The capability is -there- but many projects simply divide the groups
> into "users" and "develoeprs" and that works fairly well too.  ;-)
> 
> One more positive for Jira -- "it's not just bugs!" For 
> example, issues
> can be categorized as feature requests and scheduled for a version and
> then folks can look at the "Roadmap" and see that "Floating 
> Numbers" are
> scheduled for version 1.5. It's far easier to see this visually. ;-)
> 
> Timo
> 
> 
> 
> 
> 
> 
> > ----- Original Message ----- 
> > From: "Tim Colson (tcolson)" <tcolson@cisco.com>
> > To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
> > Sent: Wednesday, March 16, 2005 10:34 PM
> > Subject: RE: Jira for Velocity & Velocity Tools
> >
> >
> > So far, general consensus seems to be favorable for moving to
> > Jira, so I
> > looked up the details:
> >
> > http://wiki.apache.org/old/JIRABugzillaMigration
> >
> > Step 1: agree to move -- seems like we need the other committers to
> > chime in and vote)
> > Step 2: migrate bugzilla -- Yes
> > Step 3: Project Structure -- "one project per versioned product" --
> > which is inline with what I was recommending.
> > Velocity Core
> > Velocity Tools
> >
> > Step 4: Project Key(s)
> > Velocity Core = VELOCITY
> > Velocity Tools = VELTOOLS
> >
> > Step 5: List Developers
> >
> > "Please ask every developer to create a JIRA account in 
> advance. Then
> > give us a list of usernames that we will associate with your
> > permission
> > scheme. If they have an existing bugzilla account, they must use the
> > same e-mail address that they use with bugzilla."
> >
> > Step 6: Admin -- pick one person (typically a PMC member) 
> who will be
> > responsible for adding and deleting users from their group.
> >
> > Step 7: Enter request in Jira
> > ...probably should wait a week for things to settle down after the
> > Apache "Infrathon" upgrades going on this weekend.
> >
> >
> >
> > Say -- who are the 'current' committers on the core? Besides Will?
> >
> > This page seems outta date:
> > http://jakarta.apache.org/velocity/contributors.html
> > And tools..hmmm... we all know it's Nathan & Marino...and 
> Shinobu too,
> > right? But I just realized there isn't a "Contributer" page for the
> > Veltools sub-project.
> >
> > -Timo
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: 
> velocity-dev-help@jakarta.apache.org
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: 
> velocity-dev-help@jakarta.apache.org
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]