[WG: Sakai QA] [Building Sakai] Proposal: create new Jira issue type: proposal

[May, Megan Marie]

Hey Anth, 
  If the community is going to go this route, I don't think that an issue should be changed to a task.   Part of the rationale for this change is to enable easy searching but I think some of that will be lost when you can no longer search on the type of issue (ie proposal).

Megan 

-----Original Message-----
From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Anthony Whyte
Sent: Monday, May 04, 2009 6:36 PM
To: Cris J Holdorph
Cc: Sakai QA; Sakai-Dev Developers; Sakai UX
Subject: Re: [Building Sakai] Proposal: create new Jira issue type: proposal

Voting on list is ok with me.  Immediate and everyone sees it.  I just mentioned Jira voting as an option worth exploring.

The gist of my proposal is

1) add proposal type
2) require that proposals get added as issues in Jira so they can be tracked, searched, etc.

Cheers,

Anth



On May 5, 2009, at 12:27 AM, Cris J Holdorph wrote:

> I could see a slight confusion with respect to voting.
>
> If you reply to a proposal on the email list, you can vote with 
> something like "+1", "-1" or even "0".
>
> If you look at a proposal in jira you can 'vote' on the jira, but it 
> only adds your support to the proposal, there is no way to cast a 
> negative vote.  ("0" votes could simply take the form of a jira 
> comment).
>
> If you believe the voting should still be done on the mailing list, 
> then I am not sure your suggestion is anything to different then what 
> we're already doing.
>
> ---- Cris J H
>
> Anthony Whyte wrote:
>> Sakai-Dev sees its share of technical proposals; some get approved, 
>> some get rejected, while others get put on hold for one reason or 
>> another.
>> Searching for proposals can be tricky as some proposals get recorded 
>> in Jira, others proposed only on a Sakai list.
>>
>> I'd like to propose that we add a new task type called "proposal" in 
>> Jira where proposals can be submitted, voted on, watched, assigned, 
>> tracked, resolved and closed.  "Feature Request" won't do; my recent 
>> proposal to delete Eclipse metadata files is a task not a feature 
>> request, one worth polling the community to see if support existed 
>> for such work (so far unanimous approval along with several excellent 
>> suggestions as to how it should be done correctly).
>>
>> Adding "proposal" as a type permits easy searching: searching on 
>> "upgrade" or filtering on "global" does not return a clean list of 
>> outstanding proposals and I think we should promote easy ways for 
>> people to search and track suggested initiatives (after all, for 
>> instance, we have the end of life of Java 1.5 to contemplate).  
>> Requiring that technical proposals are logged in Jira would create 
>> one central proposals repository.
>>
>> Along with it we adjust our proposal handling protocol to something 
>> like
>> this:
>>
>> 1) document your proposal in Jira
>> 2) announce it on Sakai-Dev and/or other appropriate Sakai lists and 
>> seek community comment and support (vote on list or in Jira)
>> 3) record community feedback  (e.g., "I suggest this approach", 
>> "Don't forget to do x", "This is not the right time for n reasons," 
>> etc.) in Jira
>> 4) if proposal approved change status to approve / if not approved 
>> change status to rejected, resolution "won't fix" (or add another 
>> resolution type)
>> 6) when ready to implement, change type to task, add affects version, 
>> status open/in progress
>> 7) resolve, test, close
>>
>> That is my proposal.
>>
>> Cheers,
>>
>> Anthony
>>
>>
>>
>> Some outstanding proposals :
>>
>> Add a proposal type in Jira
>> Delete Eclipse metadata files from SVN Upgrade to Maven 2.0.10 (or 
>> thereabouts) Upgrade to Java SE 6 (e.g., 1.6)
>>
>> Upgrade to Tomcat 6
>> http://bugs.sakaiproject.org/jira/browse/SAK-8544
>> http://bugs.sakaiproject.org/jira/browse/SAK-10720  (closed)
>>
>> Upgrade to Spring 2.5.6
>> http://bugs.sakaiproject.org/jira/browse/SAK-16029
>>
>> Upgrade to Hibernate 3.2.6
>> http://bugs.sakaiproject.org/jira/browse/SAK-12508
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev- 
>> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev- 
> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>