Category talk:Add a Feature (Pathway)

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
 
There may be some differences in Steps 4 and 5 depending on the community and the tools, e.g. the student may not be able to close the ticket.
 
There may be some differences in Steps 4 and 5 depending on the community and the tools, e.g. the student may not be able to close the ticket.
  
There needs to be a pathway to incorporate the "Tools" and "Community" aspects of the pre-requisites
+
There needs to be a pathway to incorporate the "Tools" and "Community" aspects of the pre-requisites. For instance a potential [[:Possible_Pathways_and_Learning_Activities#Specification_.26_Coding|Specification and Coding]] pathway could be the prerequisite for "Tools" and [[:Possible_Pathways_and_Learning_Activities#Communication_.26_Tools|Communication and Tools]] could be the prerequisite for "Community".

Revision as of 00:17, 9 March 2017

Need to have an "Identify a Feature to be Added" activity based on assessing the current feature set (for Step 1)

There may be some differences in Steps 4 and 5 depending on the community and the tools, e.g. the student may not be able to close the ticket.

There needs to be a pathway to incorporate the "Tools" and "Community" aspects of the pre-requisites. For instance a potential Specification and Coding pathway could be the prerequisite for "Tools" and Communication and Tools could be the prerequisite for "Community".

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox