Search results

Jump to: navigation, search
  • {| {{Pathway Prerequisite Table}} * '''Complete a yet-to-be-determined pathway''' that does not yet exist.
    0 members (0 subcategories, 0 files) - 11:21, 6 August 2020
  • ! Pathway Step {| {{Pathway Step Table}}|-
    578 B (74 words) - 17:44, 22 January 2019
  • {| {{Pathway Prerequisite Table}} === Pathway Steps, Outcomes, & Learning Activities ===
    0 members (0 subcategories, 0 files) - 00:58, 9 March 2017
  • {| {{Pathway Prerequisite Table}} === Pathway Steps, Outcomes, & Learning Activities ===
    0 members (0 subcategories, 0 files) - 00:34, 9 March 2017
  • {| {{Pathway Prerequisite Table}} === Pathway Steps, Outcomes, & Learning Activities ===
    1 member (0 subcategories, 0 files) - 00:40, 9 March 2017
  • {| {{Pathway Prerequisite Table}} === Pathway Steps, Outcomes, & Learning Activities ===
    0 members (0 subcategories, 0 files) - 18:37, 11 March 2017
  • ...r are part of a separate pathway - for example, the Create a Tracker Issue pathway.) ... taken to replicate the bug." might be a better fit for the "Verify a Bug" pathway.
    1 KB (245 words) - 00:25, 9 March 2017
  • ...] has content to be transcluded into the '''prerequisite table''' of every pathway.
    15 members (0 subcategories, 0 files) - 14:45, 27 February 2017
  • Is this pathway missing a step 0? The pre-req knowledge may go deeper than the pathway - can this be simpler perhaps.
    215 B (39 words) - 00:02, 9 March 2017
  • Would like others thoughts on whether the pathway should include a step to understand a bug tracker or should this be per-req
    1 KB (247 words) - 01:08, 9 March 2017
  • ...nd_Learning_Activities#Specification_.26_Coding|Specification and Coding]] pathway could be the prerequisite for "Tools" and [[:Possible_Pathways_and_Learning
    556 B (81 words) - 00:39, 9 March 2017
  • ... many learning activities so far that support the individual steps of this pathway.
    2 KB (246 words) - 18:42, 11 March 2017
  • Consider rebranding this pathway to "quality assurance", which could include static analysis, refactoring, u *There is overlap of this pathway with the adding new feature pathway because, ideally, with each feature the associated unit tests should be dev
    278 B (40 words) - 00:52, 9 March 2017
  • There should probably be Pathway(s) for becoming proficient in using tools and in communicating with communi
    179 B (28 words) - 00:09, 9 March 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

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