Search results
Create the page "Bug Tracker Activity" on this wiki!
- Project Anatomy Activity - Sugar Labs Tracker -- The Sahana Eden bug tracker14 KB (2,177 words) - 12:54, 15 October 2018
- === PART C2. BUG TRACKER ACTIVITY === === Part 1: Bug Reports ===22 KB (3,575 words) - 01:52, 7 February 2017
- ...nication of the team. However, only one team current has coordinators (the Activity Team, while the Development and Documentation teams have vacancies for thes :''The types of tickets found on the Sugar Labs bug tracker are <nowiki>"</nowiki>defect<nowiki>"</nowiki> and <nowiki>"</nowiki>enhanc9 KB (1,361 words) - 01:48, 7 February 2017
- == Planning an Initial HFOSS Learning Activity == ...you could create a learning activity page for it by copying the [[Learning Activity Format with Directions]].4 KB (528 words) - 16:43, 27 February 2017
- ! Assignment/Activity | [[File:BlogAssignment.docx|Blog activity]] (Add a page to my Wiki and, using wiki markup, add a link to their blog)6 KB (806 words) - 18:42, 4 June 2018
- # [[:Category:Verify a Bug (Pathway)|Verify a Bug (Pathway)]] #* Examples: [[Bug Gardening]]18 KB (2,636 words) - 11:18, 6 August 2020
- # Verify a bug # Fix a bug18 KB (2,683 words) - 11:18, 6 August 2020
- ... It appears that a user must register for an account in order to submit a bug report. Ticket types include defect, enhancement and task. The informatio * The information available in the Sahana bug tracker is similar to that in Sugar, although the interface is different in that Sa13 KB (1,934 words) - 01:36, 7 February 2017
- '''Tracker:''' Describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as ...he information here different than the information found on the Sugar Labs tracker page?13 KB (1,985 words) - 01:29, 7 February 2017
- '''Intro IRC Activity:''' '''Project Anatomy Activity: Guided Tour'''20 KB (3,138 words) - 01:29, 7 February 2017
- === IRC Activity === ...because the amount of activity is a sparse function of time with bursts of activity that may be much further than 24 hours apart.22 KB (3,533 words) - 01:37, 7 February 2017
- ''Tracker'' ''Tracker''14 KB (1,725 words) - 01:32, 7 February 2017
- == Intro IRC Activity == == [http://foss2serve.org/index.php/Project_Anatomy_Activity Project Anatomy Activity] ==43 KB (7,078 words) - 11:19, 6 August 2020
- '''Part A - Question 6 - Project Anatomy Activity''' '''On your wiki page describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as5 KB (890 words) - 01:36, 7 February 2017
- ==== Use of Tracker ==== ...e [https://github.com/sugarlabs sugarlabs page at github] and look for the activity or a sugar component repository that is relevant. If it isn't clear which o11 KB (1,795 words) - 01:34, 7 February 2017
- '''Intro IRC Activity''' == FOSS Field Trip Activity ==10 KB (1,501 words) - 01:36, 7 February 2017
- == Planning an Initial HFOSS Learning Activity == ...you could create a learning activity page for it by copying the [[Learning Activity Format with Directions]].2 KB (219 words) - 16:45, 27 February 2017
- ...rom source; Running the test suite; Verifying bugs from the issue tracker (Bug Gardening); and Fixing bugs. During the second semester students continue w ...for the FORMAT - remove it for a new activity, and add the license for the activity -->3 KB (466 words) - 13:56, 18 October 2019
- Tracker: What is the process for submitting a bug? File a bug using Trac. Describe, Categorize, Create.10 KB (1,499 words) - 21:56, 12 June 2017
- {{Learning Activity Overview Bug Selection3 KB (541 words) - 17:53, 8 March 2017
- {{Learning Activity Overview Project Evaluation Activity15 KB (2,359 words) - 11:42, 8 September 2018
- * base activity modules are called ''Fructose'' # Activity: An average of 30 commits per month seems to be reasonably good for an acti19 KB (2,914 words) - 01:09, 7 February 2017
- === Project Anatomy Activity notes === ...o on what data the developers would like to know, and the "how to submit a bug report" guide was long, rambly, and at times condescending.20 KB (3,246 words) - 01:04, 7 February 2017
- ...a good time wandering through the "sugar labs" pages. I looked at the bug tracker, read the landing page, looked for a recent commit (2014?). When I was don '''FOSS Field Trip Activity'''2 KB (235 words) - 01:10, 7 February 2017
- ...eally the impressed because it seems the community is talking mainly about bug fixes. Perhaps that is the purpose of the chat, but that is not what my exp I do like how the bug tracker differs from Sugarlabs... They divide them up by category rather than listi9 KB (1,597 words) - 01:09, 7 February 2017
- Responses to Intro IRC Activity Questions I observed the Sahana project channel for 36 hours and there was activity with persons logging on and exiting. There was no communication.12 KB (1,888 words) - 01:16, 7 February 2017
- |Bug Tracking ...h priority. Clicking on the bug text reveals So Much information about the bug.10 KB (1,677 words) - 01:05, 7 February 2017
- ! Activity Breakout: Learning activity review or design5 KB (683 words) - 21:05, 19 October 2017
- ''Tracker'' ...t an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component repository hat you think is relevant. If you don't kno10 KB (1,471 words) - 01:12, 7 February 2017
- This is the bug Tracker activity at [https://bugzilla.gnome.org https://bugzilla.gnome.org] Bug 648260 - Improve the documentation of ATK_STATE_VISIBLE and deprecate ATK_S2 KB (337 words) - 04:45, 17 November 2016
- '''The contributor will''': study and try to update a tracker issue (e.g. a bug report or feature request) to identify missing information, provide additio | Issue Tracker0 members (0 subcategories, 0 files) - 00:20, 9 March 2017
- * [[Practice EARS (Activity)]] approach for OpenMRS requirements [[Requirements engineering process (Activity)]]19 KB (2,520 words) - 08:48, 27 January 2021
- ...sts accepted into the project's codebase, and test results logged on issue tracker or otherwise accepted by the community. | Issue Tracker0 members (0 subcategories, 0 files) - 00:34, 9 March 2017
- ...duce a bug in the issue tracker, and update the issue to indicate that the bug was verified or that more information is needed. '''The contribution is''': more information about the bug, which could make it easier to fix.1 member (0 subcategories, 0 files) - 00:40, 9 March 2017
- ...ontributor will''': fix a bug by submitting a patch and updating the issue tracker. ...ntribution is''': a patch for the bug and updated information in the issue tracker.0 members (0 subcategories, 0 files) - 18:37, 11 March 2017
- ...ity to "read and understand the accompanying materials about an issue in a tracker". ''Research Bug Activity'' added under Related Learning Activities for "2. Study the issue details,1 KB (245 words) - 00:25, 9 March 2017
- ...clude>[[:Category:Bugzilla|Bugzilla]] is an '''issue tracker''' (or '''bug tracker'''). (see https://www.bugzilla.org)</onlyinclude> [[Category:Learning Activity]]5 members (0 subcategories, 0 files) - 12:11, 10 February 2017
- === Intro to FOSS Project Anatomy (Activity) === * General process for submitting a bug:16 KB (2,398 words) - 03:18, 19 April 2017
- Report bug --- go to its github site, choose related component, report issue. Report bug --- go to its github site. At the moment there are 22 issues. Study them as5 KB (726 words) - 15:11, 19 April 2017
- ''Tracker'' ... bug involves using [https://trac.edgewall.org Trac] for issue tracking. A bug is reported by [http://wiki.sugarlabs.org/go/BugSquad/Bug_Report creating a24 KB (3,599 words) - 14:56, 3 November 2017
- '''Tracker''' Bug submission: Identify relevant component repo, and then submit through Githu6 KB (851 words) - 19:02, 20 April 2017
- == Intro to FOSS Project Anatomy Activity == Tracker. The general process for submitting bugs is under the issues tab of the Pr21 KB (2,984 words) - 19:34, 20 April 2017
- ... thoughts on whether the pathway should include a step to understand a bug tracker or should this be per-requisite knowledge. ...rent pathways: one to create a tracker issue for a bug and one to create a tracker issue for a new feature.1 KB (247 words) - 01:08, 9 March 2017
- '''Intro to FOSS Project Anatomy (Activity)''' Bug Tracking: Check GitHub, identify related component, report issue.5 KB (695 words) - 17:40, 15 April 2017
- === Intro to FOSS Project Anatomy (Activity) === '''Tracker / Repository'''4 KB (669 words) - 19:43, 13 March 2017
- * It seems that the activity is not available because of issues with incorrect code location, or becausa | '''Level of Activity'''9 KB (1,332 words) - 00:48, 20 April 2017
- [[Stage 1 Activities]] >> [[Intro to IRC (Activity)]] No activity. Lots of people coming and going. Saw a couple POSSE folks in my log.12 KB (1,837 words) - 01:17, 16 April 2017
- **OpenHub project summaries include: lines of code, activity(commits per month), and community monthly contributions. ...only shows up if there are contributors. Projects without contributor have activity not available icon.11 KB (1,463 words) - 16:04, 21 April 2017
- ====Tracker==== * Describe the general process for submitting a bug report15 KB (2,309 words) - 02:51, 16 April 2017
- | Bug gardening | http://foss2serve.org/index.php/Comparable_Interface_-_Code_Reading-Activity3 KB (445 words) - 20:44, 18 June 2019
