#771: [RFC] Modify the ticket reporting process
------------------------------+---------------------------------------------
      Reporter:  mrenzmann    |       Owner:  mrenzmann
          Type:  enhancement  |      Status:  assigned 
      Priority:  minor        |   Milestone:           
     Component:  website      |     Version:           
    Resolution:               |    Keywords:           
Patch_attached:  0            |  
------------------------------+---------------------------------------------
Comment (by dyqith):

 {{{
 In my opinion, stuff that should be located in a ticket:
 (Also, each field and their entries should have an explicit definition
 somewhere, i.e. what does it mean to be a type:defect, and
 priority:critical)

 Reported by:
    add by reporter
 Summary/Description
    add by reporter
 Type
    add by reporter
    {defect, enhancement, task} are fine
 Version:
    add by reporter
    Rename to affected version, since its about what the user used.

 Keywords:
    add by the reporter


 Assigned to: (accepted)
    add by the teammembers

 Priority:
    add by the teammembers
    Define each of the entries based on when it needs to be looked
 at/resolved and the number of people affected:
    blocker (immediate, 1-2 days, affects everyone, (security issues))
    critical (within a week)
    major (within 2 weeks)
    minor (within a month)
    trivial (within 2 months, affects only 1 person)

 Milestone:
    add by the teammembers
    modified based on the milestone goals

 Component:
    define each type (i.e. what's the diff. between madwifi:802.11 stack,
 madwifi:driver, madwifi:HAL)
    One suggestion is to have only 4 types of components (i.e. website,
 irc, madwifi driver, docs), then we subcategorize these types (allow the
 reporter to leave blank if they don't know where to put it, and have
 things like 802.11 stack, HAL, rate modules, user interface, architecture
 compilation, makefiles, etc)

 Cc:

 Patch is attached:      0/1 (true or false)

 }}}

-- 
Ticket URL: <http://madwifi.org/ticket/771>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to