Search results
Create the page "Style Guides" on this wiki!
Page title matches
- The Need for Style Guides ...for a various projects. Based on this experience, students will develop a style guide for their team.4 KB (557 words) - 18:45, 8 March 2017
- No H/FOSS - can this be incorporated in any way? Is there a FOSS style guide that can be incorporated?183 B (31 words) - 18:48, 8 March 2017
Page text matches
- This activity guides a person or team to evaluate a FOSS project and decide if they might want t {| class="wikitable" style="width:50%;"14 KB (2,185 words) - 15:36, 14 April 2019
- |- style="background: lightgrey" | ...ir projects to more effectively meet their conservation goals. The program guides users through a series of step-by-step interview wizards, based on the Open57 KB (8,277 words) - 12:16, 15 April 2022
- ...ces to support enhanced use of IRC by CS faculty. These resources include guides for faculty (technological and pedagogical), technological resources for fa :A SIGCSE-style paper that reports on what we've learned.5 KB (836 words) - 12:25, 10 February 2017
- *'''Compare and contrast FOSS to Commercial SW projects using the guides provided for FOSS Field Trip''' ... recast that code block into a well formed and detailed SRS (complete with style and functional & structural requirement) and make it a programming assignme24 KB (3,934 words) - 09:36, 7 February 2017
- Identify program code and documentation style for a specific HFOSS project. Provide possible areas for improvement in a p ::* identify "bad" vs "good" coding style, including code layout styles, variable names, etc.49 KB (7,951 words) - 15:27, 7 September 2015
- The Need for Style Guides ...for a various projects. Based on this experience, students will develop a style guide for their team.4 KB (557 words) - 18:45, 8 March 2017
- ...popular open source projects. Students answer questions and write an essay-style report detailing their findings and comparing the two communities design ou You will need to write a two-section essay-style paper, one section that answers some specific questions, and another that c20 KB (2,953 words) - 12:05, 8 September 2018
- ...nt writer. Most students can handle writing either documentation, code, or guides of various forms and degrees of technicality. More likely is that the stude * Develop spelling and grammar style conventions for documentors22 KB (3,533 words) - 01:37, 7 February 2017
- ...t gets a B+/A- for approachability. There is an extensive set of developer guides that seem to be fairly well written (from my quick skim), and seem to make ... refactor/restructure some code, usually a method or a set of methods, for style and clarity. In both cases, I've had students bring in their own code for t20 KB (3,246 words) - 01:04, 7 February 2017
- <br style="clear:both;"> * Group 5: Interactive Visualization with Git - Intro to Style Guides (Activity) -- Stewart and Joanna5 KB (683 words) - 21:05, 19 October 2017
- {| class="wikitable" style="width:100%;" ! style="width:60%;" | Evaluation Data6 KB (851 words) - 19:02, 20 April 2017
- {| class="wikitable" style="width:100%;" ! style="width:80%;" | Evaluation Data12 KB (1,837 words) - 01:17, 16 April 2017
- ** The style of discussion is informal. The structure itself is linear, but using specia | There is a Developers Guides, and Getting started as a Developer. There are several discussions about Vo15 KB (2,138 words) - 06:22, 1 July 2017
- {| class="wikitable" style="width:100%;" ! style="width:60%;" | Evaluation Data14 KB (2,308 words) - 14:15, 20 June 2018