Documentation/4.3/Report a problem - Revision history

Kikinis: /* User Feedback */

2014-10-05T15:49:20Z

User Feedback

2013-10-30T01:35:16Z

User Feedback

2013-09-29T08:58:21Z

Workflow for Handling Bugs and Feature Requests in Slicer

2013-09-29T08:55:24Z

User Feedback

2013-09-29T08:54:34Z

Workflow for Handling Bug in Slicer

2013-09-29T08:53:26Z

2013-09-29T08:51:50Z

User Feedback

2013-09-29T08:50:43Z

User Feedback

2013-09-29T08:49:30Z

User Feedback

2013-09-29T08:35:19Z

@@ Line 6: / Line 6: @@
 *I have a question about how to use Slicer for a particular task
 ** Look at our [[Documentation/UserTraining|portfolio of training materials]] and make a google search to see, if the question has been discussed in the mailinglists.
-** I am still unclear about what to do. In this case, sign up for the slicer user mailing list: [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-user Sign-up]
+** I am still unclear about what to do. In this case, sign up for the slicer user mailing list: [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-users Sign-up]
 *Something is not working as it should or I would like to request a feature.
 ** File a bug report in the issues [http://na-mic.org/Mantis/bug_report_page.php tracker] (you need to register first). It is important to provide enough specific information so that a software developer can duplicate the problem. [[Documentation/{{documentation/version}}/Report_a_problem#Workflow_for_Handling_Bugs_and_Feature_Requests_in_Slicer|See below]] for more details.

@@ Line 12: / Line 12: @@
 **Please send us the citation for your paper.
 **Background: funding for Slicer is provided through competitive mechanisms to a large extent by the US government and to a lesser extend through funding from other governments. The justification of for those resources is that Slicer enables scientific work. Knowing about scientific publications enabled by Slicer is a critical step in this process. Given the international nature of the Slicer community, the nationality of the scientists is not important. Every good paper counts.
 ==Workflow for Handling Bugs and Feature Requests in Slicer==

@@ Line 14: / Line 14: @@
 ==Workflow for Handling Bugs and Feature Requests in Slicer==
-The following instructions describe the recommended workflow to report a problem related to Slicer application.
+The following instructions describe the recommended workflow to report a problem related to Slicer application. The issue flows from top left to bottom left following the arrows. Issues are bug reports, feature requests and similiar items. A data base with a web interface is at the core of this software engineering methodology.
 * 1. [http://na-mic.org/Mantis/signup_page.php Register] on the issue tracker

@@ Line 8: / Line 8: @@
 ** I am still unclear about what to do. In this case, sign up for the slicer user mailing list: [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-user Sign-up]
 *Something is not working as it should or I would like to request a feature.
-** File a bug report in the issues [http://na-mic.org/Mantis/bug_report_page.php tracker] (you need to register first). It is important to provide enough specific information so that a software developer can duplicate the problem. [[Documentation/{{documentation/version}}/Report_a_problem#User_Feedback|See below]] for more details.
+** File a bug report in the issues [http://na-mic.org/Mantis/bug_report_page.php tracker] (you need to register first). It is important to provide enough specific information so that a software developer can duplicate the problem. [[Documentation/{{documentation/version}}/Report_a_problem#Workflow_for_Handling_Bugs_and_Feature_Requests_in_Slicer|See below]] for more details.
 * I would like to let the Slicer community know, how Slicer helped me in my research.
 **Please send us the citation for your paper.

@@ Line 13: / Line 13: @@
 **Background: funding for Slicer is provided through competitive mechanisms to a large extent by the US government and to a lesser extend through funding from other governments. The justification of for those resources is that Slicer enables scientific work. Knowing about scientific publications enabled by Slicer is a critical step in this process. Given the international nature of the Slicer community, the nationality of the scientists is not important. Every good paper counts.
-==Workflow for Handling Bug in Slicer==
+==Workflow for Handling Bugs and Feature Requests in Slicer==
 The following instructions describe the recommended workflow to report a problem related to Slicer application.

← Older revision		Revision as of 08:35, 29 September 2013
Line 1:		Line 1:
	<noinclude>{{documentation/versioncheck}}</noinclude>		<noinclude>{{documentation/versioncheck}}</noinclude>
		+
		+
		+	=User Feedback=
		+
		+	*I have a question about how to use Slicer for a particular task
		+	** Look at our [[Documentation/UserTraining\|portfolio of training materials]].
		+
		+
	The following instructions describes the recommended workflow to report a problem related to Slicer application.		The following instructions describes the recommended workflow to report a problem related to Slicer application.