Search results

Jump to: navigation, search

Page title matches

Page text matches

  • I do see a Learning and a Learning Activity category. Trying Learning Activity first.
    6 KB (895 words) - 04:15, 25 January 2014
  • .../Date of recent commits: https://github.com/nodejs/education/graphs/commit-activity 4. Code statis including lines, lanuages, etc; activity stats, like commits per month, etc.; community stats, such as contributors
    20 KB (2,910 words) - 14:53, 28 June 2017
  • ...iously used. It should be easier for my students to use when I assign this activity to my Senior Project class *Activity: 1 - very little activity since May
    28 KB (4,684 words) - 01:01, 12 October 2022
  • == Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) == == Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==
    8 KB (1,222 words) - 01:48, 7 February 2017
  • {{Learning Activity Overview ...s that you will use when participating in a FOSS project. The goal of this activity is not to provide depth in any one tool or aspect of culture, but to provid
    15 KB (2,389 words) - 13:59, 20 April 2019
  • {{Learning Activity Overview # Describe the role that a issue tracker plays in a FOSS project.
    4 KB (688 words) - 19:47, 22 May 2019
  • ...et their needs." Well set up site, but as of 6/2018, there seems to be no activity since about 2015. Email inquiry did produce a response. | A software collaboration platform that provides bug tracking, code hosting using Bazaar, code reviews, Ubuntu package building
    57 KB (8,277 words) - 12:16, 15 April 2022
  • == Project Anatomy Activity == ...collaborative and constructivist. They are also responsible for recruiting activity mentors and collaborating with the Education team to create their activitie
    10 KB (1,672 words) - 10:05, 7 February 2017
  • IRC conversation activity: Project Anatomy Activity
    5 KB (736 words) - 10:08, 7 February 2017
  • == IRC Activity == * Activity Team
    9 KB (1,404 words) - 10:07, 7 February 2017
  • ...ams have differing focuses and have non-intersecting sets of members. The activity and documentation teams are more outward facing and therefore have more inf * ''Tracker:'' There are three categories of tickets: immediate priority, urgent priori
    7 KB (1,177 words) - 10:06, 7 February 2017
  • == Project Anatomy Activity == Re ''bug tracking and tickets'', the types and categories of tickets listed for suga
    4 KB (567 words) - 10:05, 7 February 2017
  • '''Project Anatomy Activity''': - Only the activity and doc. team have mailing lists
    3 KB (501 words) - 10:08, 7 February 2017
  • Distinct: Activity team as opposed to other two teams is more structured and action oriented. '''Tracker'''
    3 KB (418 words) - 10:04, 7 February 2017
  • ...roviding a reasonable alternative to Photoshop is therefore a humanitarian activity. ====CS1 Activity: Contribute a Plug-In to GIMP====
    20 KB (3,335 words) - 10:08, 7 February 2017
  • * describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as ...two weeks and another in the last two months. I can tell this from the “activity” page.
    16 KB (2,559 words) - 01:34, 7 February 2017
  • {{Learning Activity Overview Bug Tracker Activity-MouseTrap
    4 KB (681 words) - 19:19, 7 September 2018
  • | IRC and Meetbot Activity ** locating the project's bug/issue tracker
    6 KB (928 words) - 13:51, 29 January 2017
  • === Intro to IRC (Activity) === == Intro to FOSS Project Anatomy (Activity) ==
    24 KB (3,685 words) - 06:22, 16 June 2019
  • Sugar uses github to post bugs. Issue tags are bug, design, errata, feature, needs SLOBS, needs work. The last commit in the c Activity Not Available indicates that the activity tracking data cannot be captured - perhaps the code location is down or the
    10 KB (1,587 words) - 00:21, 12 June 2019
  • #'''Tracker''' ...r repo component; go to the issues tab; press the green button to submit a bug.
    23 KB (3,418 words) - 22:11, 12 June 2019
  • === Intro to IRC (Activity) === === Intro to FOSS Project Anatomy (Activity) ===
    3 KB (388 words) - 15:58, 16 June 2019
  • * Bug Gardening ** [[Intro to Bug Trackers (Activity)]]
    8 KB (1,237 words) - 15:25, 19 June 2019
  • ...or students:''' Writing API documentation, Testing and potentially fixing bug. All roles allows students to get used to work with code they did write the ...ined. Sugar have policies and plans for releases while Eden have an issue tracker where discussion happen and code changes are proposed via pull requests.
    17 KB (2,475 words) - 11:21, 6 August 2020
  • ... The newer version is [http://foss2serve.org/index.php/Project_Evaluation_(Activity) here] </span>= {{Learning Activity Overview
    15 KB (2,199 words) - 17:44, 8 March 2017
  • A. 4 Intro IRC Activity A.6 Anatomy of a FOSS Project Activity
    9 KB (1,520 words) - 09:50, 7 February 2017
  • Intro IRC Activity Community Activity
    12 KB (1,966 words) - 09:50, 7 February 2017
  • Activity team: develops and maintains activities for Sugar as well as interacting wi ... on documentation although at a different scale. Also, the Development and Activity teams both do development, but they develop different things.
    16 KB (2,599 words) - 09:26, 7 February 2017
  • * Activity Team: develops and maintains many of the activities; there are 2 coordinato ...here is no coordinator and 4 "people" listed; there is no overlap with the Activity team
    15 KB (2,418 words) - 14:39, 19 June 2018
  • ...channel. When I joined the channel for openMRS, it didn't seem to have any activity, making me wonder if I am in right place. 2. --- Project Evaluation Activity
    11 KB (1,872 words) - 09:36, 7 February 2017
  • ; Activity Team ==== Tracker ====
    30 KB (5,015 words) - 09:37, 7 February 2017
  • The three teams, Activity, Development, and Documentation, all have similar structures with positions ...cation channels such as emaillists and irc channels the teams monitor. The activity team, due to the size of the contributor list, seems more active than the o
    12 KB (1,965 words) - 09:26, 7 February 2017
  • ...owing the #ushahidi channel periodically, but it seems to have very little activity. *# Activity Team
    12 KB (1,906 words) - 09:34, 7 February 2017
  • ===Intro to IRC Activity === '''''Activity Team''''' - Detailed review of project, tools and links to be successful, l
    17 KB (2,676 words) - 09:49, 7 February 2017
  • === Bug Tracker Activity === ID - id number of bug
    49 KB (7,951 words) - 15:27, 7 September 2015
  • | [[Intro to Bug Trackers (Activity)]] | Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a
    2 KB (252 words) - 13:05, 8 February 2017
  • {{Learning Activity Overview Solving a Bug
    5 KB (762 words) - 12:10, 8 September 2018
  • {{Learning Activity Overview Write a Bug Report
    4 KB (656 words) - 18:56, 8 March 2017
  • {{Learning Activity Overview Bug Grooming / Bug Triage / Bug Zapping / Bug Wrangling
    9 KB (1,434 words) - 21:19, 3 July 2019
  • 1. Introduction to FOSS (2 hrs) - Completed 10/5. (Repeated activity from prior workshop. Notable elements were: 2. TOS Activity
    17 KB (2,625 words) - 12:13, 25 October 2017
  • '''Part A, Part 1, Activity 4: [http://foss2serve.org/index.php/Intro_IRC_Activity Introduction to IRC] '''Part A, Part 3, Activity 3: [http://foss2serve.org/index.php/Intro_IRC_Activity Introduction to IRC]
    8 KB (1,195 words) - 12:54, 16 October 2017
  • === Answers to "Intro to IRC Activity" questions: === === Answers to "Project Anatomy Activity" questions: ===
    20 KB (3,136 words) - 01:47, 7 February 2017
  • === Intro IRC Activity, Answers to Part 1 questions === === Intro to IRC Activity Part 3 – Join and Observe Channel Discussion ===
    32 KB (5,316 words) - 01:49, 7 February 2017
  • Answers to Activity A.4 "Introduction to IRC" - Part 1 : Observations from Activity A.4 "Introduction to IRC" - Part 3 :
    4 KB (516 words) - 01:47, 7 February 2017
  • ...ing system in the PC world. Their responsibilities also include recruiting activity developers, working with the development team to support developers, and th ''Sugarlabs Bug Tracker''
    23 KB (3,906 words) - 01:52, 7 February 2017
  • Intro to IRC Activity ... I found the logs of the channel. The OpenMRS channel had a fair amount of activity, limited to a few users for a while. It looks like a new user setting up th
    9 KB (1,485 words) - 01:52, 7 February 2017
  • == Response to IRC Activity == ==PartB: Project Evaluation Activity==
    10 KB (1,446 words) - 01:50, 7 February 2017
  • ...evelopment team was much smaller (4 - I didn't notice any overlap with the activity team list) and did not have a coordinator. There was a posting about vacanc ...bugs are "defect" and "enhancement" - I am guessing those are pretty much "bug"/"feature" (or feature request). For every ticket in the system, you can se
    14 KB (2,482 words) - 01:49, 7 February 2017
  • == Stage 1 - Part A - Intro IRC Activity == ... meeting is about to end. It appears if some minutes have gone by without activity that the meeting is simply ended without comments about the next meeting.
    34 KB (5,610 words) - 01:48, 7 February 2017
  • ==Intro IRC Activity Notes== ...erstand conversation happening there... but I found that there wasn't much activity in these channels. So then I tried #openMRS and was able to observe a lot m
    20 KB (3,186 words) - 01:49, 7 February 2017
  • Project Anatomy Activity - Sugar Labs Tracker -- The Sahana Eden bug tracker
    14 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>enhanc
    9 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 bug
    18 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 Sa
    13 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 as
    5 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 o
    11 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 Selection
    3 KB (541 words) - 17:53, 8 March 2017
  • {{Learning Activity Overview Project Evaluation Activity
    15 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 acti
    19 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 listi
    9 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 design
    5 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 kno
    10 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_S
    2 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 Tracker
    0 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 Tracker
    0 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 as
    5 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 a
    24 KB (3,599 words) - 14:56, 3 November 2017
  • '''Tracker''' Bug submission: Identify relevant component repo, and then submit through Githu
    6 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 Pr
    21 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 report
    15 KB (2,309 words) - 02:51, 16 April 2017
  • | Bug gardening | http://foss2serve.org/index.php/Comparable_Interface_-_Code_Reading-Activity
    3 KB (445 words) - 20:44, 18 June 2019

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

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