Search results

Create the page "Status" on this wiki!

• Evaluate a Project (Activity)
  ...nical+Road+Map Technical Road Map page] identifies features, their current status, and a point of contact, in addition to expected dates of completion.
  15 KB (2,199 words) - 17:44, 8 March 2017
• POSSE 2014-11 Announcement
  ...at darci.burdge@ncc.edu by September 26th, 2014. We will notify you of the status of your application by September 29th, 2014. Prior work with FOSS projects
  4 KB (579 words) - 09:16, 7 February 2017
• Stage 2 Activities/2.3 ParticipantResponses 2014-11
  Status - general health of a bug. (UNCONFIRMED, NEW, ASSIGNED, NEEDINFO, REOPENED, The bugs appear to be displayed by status and then priority.
  49 KB (7,951 words) - 15:27, 7 September 2015
• Materials Catalog
  * Status should be Under Development, Ready to Pilot, Ready to Use ! Status
  2 KB (252 words) - 13:05, 8 February 2017
• TeamMeeting 2015 01 Agenda
  * Assess status of the project relative to the proposal * Review of budget status
  4 KB (545 words) - 16:38, 8 January 2015
• POSSE 2015-09 Announcement
  ...rdge at darci.burdge@ncc.edu by June 15th, 2015. We will notify you of the status of your application by June 30th, 2015. Prior work with FOSS projects is no
  4 KB (579 words) - 01:42, 7 February 2017
• Research Bug Activity
  ## Under ''Status'' select ''Closed''
  2 KB (281 words) - 17:53, 8 March 2017
• Write a Bug Report (Activity)
  * identify and track the status of a particular bug report in the gnome-music project, * status: open,
  4 KB (656 words) - 18:56, 8 March 2017
• Work Locally with Git from the Command Line (Activity)
  Run `git status` before and after each of these commands. # What kind of information does `git status` report?
  8 KB (1,231 words) - 18:50, 8 March 2017
• Bug Gardening
  ... exists. Once you have identified a bug to work on, try to verify the bug status. | '''Bug Number''' ||'''Short Description'''||'''Bug Status'''||'''URL for Bug'''||'''Analysis'''||'''Actions Taken'''
  9 KB (1,434 words) - 21:19, 3 July 2019
• SIGCSE 2016 POSSE Roundup
  Breakout group status
  2 KB (346 words) - 21:04, 19 October 2017
• Git: Working with Remotes from the Command Line
  git status git status
  6 KB (859 words) - 00:07, 8 September 2018
• TeamMeeting 2016 01 Agenda
  * Assess status of the project relative to the proposal * Review of budget status
  5 KB (655 words) - 18:58, 7 January 2016
• TeamMeeting 2016 01 Notes
  * Review of budget status
  8 KB (1,156 words) - 22:20, 8 January 2016
• Sprint 2016 08 Agenda
  | Groups report out - Status update
  2 KB (326 words) - 15:55, 13 August 2016
• FOSS Course, UPenn, Murphy
  ...the other class meeting that week will be for learning activities, project status updates and presentations, or time to work on the project.
  11 KB (1,518 words) - 12:34, 20 April 2019
• Git: GitHub Workflow Activity
  ** Check the status of the repository
  3 KB (379 words) - 22:58, 7 September 2018
• Bug Selection
  |'''Bug Number''' ||'''Short Description'''||'''Bug Status'''||'''URL for Bug'''||'''Analysis'''
  3 KB (541 words) - 17:53, 8 March 2017
• Project Evaluation Activity V2
  ...nical+Road+Map Technical Road Map page] identifies features, their current status, and a point of contact, in addition to expected dates of completion.
  15 KB (2,359 words) - 11:42, 8 September 2018
• SIGCSE 2017 POSSE Roundup
  Breakout group status
  5 KB (683 words) - 21:05, 19 October 2017