Changes between Version 161 and Version 162 of ProjectInformation


Ignore:
Timestamp:
12/09/10 11:12:38 (11 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectInformation

    v161 v162  
    4545 * Think about how could it be better.
    4646 * Try Sahana Eden out -- you can use:
     47  * A running Sahana Eden [http://demo.eden.sahanafoundation.org/eden/ demo site]
    4748  * Your locally-installed Sahana Eden site -- see these setup instructions:
    48    * Instructions for [wiki:UserGuidelinesInstall user installation] (not for developers).
    4949   * Instructions for [wiki:InstallationGuidelinesVirtualMachine running Sahana Eden in a virtual machine] (for developers but also convenient for testing because this can be updated to the latest version).
    5050   * For reference, here is the [wiki:InstallationGuidelines list of all types of installations].
    51   * Or, you can use a running Sahana Eden web site:
    52    * [http://demo.eden.sahanafoundation.org/eden/ demo site]
    53    * [http://test.eden.sahanafoundation.org/eden/ user test site for Pakistan floods response]
    5451 * Modules that could use some usability improvement:
    5552  * All of them, but in particular:
     
    103100''GCI''[[BR]]
    104101Some of our bug reports (tickets) have been left open even though they've been fixed. Others don't have much information. We'd like you to go through some tickets to see if they're done or if they need more information.
    105  * Look at the [wiki:ProjectInformation#Project:Testing bug testing] project description for the web sites to test (or for installing your own copy if the software, if you'd rather).
    106  * Go through the list of [/report/1 open bugs].  Look at reports that have type "defect".  Try to reproduce the problem reported in the ticket:
    107   * If the issue is gone, add a reply to the ticket with what you did and "resolve" the ticket as "invalid". (The submitter can still reply and reopen the bug if they want.)
    108   * If you can reproduce the issue but the description isn't clear, add better "how to reproduce" instructions.
     102 * Register for an account on our [http://demo.eden.sahanafoundation.org/eden/ demo site].  Or you can install your own copy of the software, if you want to test the very latest version. Look at the [wiki:ProjectInformation#Project:Testing bug testing] project description for information on installing.)
     103 * Go through the list of [/report/1 open bugs]. Look at reports that have type "defect".  Start with older bugs -- they're more likely to be fixed or no longer relevant. There may be other GCI students working on this, so look for a comment that the bug is being worked on for GCI -- skip those.
     104 * When you've found a bug to look at, add a comment saying you've verifying it for GCI.
     105 * Try to reproduce the problem reported in the ticket:
     106  * If the description of how to make the bug happen is clear, and the bug is gone, add a reply to the ticket with what you did to test it, and "resolve" the ticket as "invalid". (The person who reported the bug can still reply and reopen the bug if they want.)
     107  * If the instructions to cause the bug to happen aren't clear, try to figure out what the reporter meant -- try to find the bug yourself. If you can reproduce the bug, add better "how to reproduce" instructions.  See the [wiki:BugReportingGuidelines Bug Reporting Guidelines] for what makes a good bug report.
    109108  * If you can't figure out what the ticket means, add a reply that tells the ticket reporter what info would be helpful.
     109 * Post links to the tickets you worked on in your GCI task.
    110110
    111111=== Project: Collate Organisation List ===