User:CLiu

Revision as of 20:41, 14 November 2016

Chunmei Liu

Chunmei Liu is a Professor in the Department of Electrical Engineering and Computer Science at Howard University, Washington, DC.

Dr. Liu has been working at Howard University since 2006. Her research interests include algorithms, computational biology, bioinformatics, and data mining. She has been teach undergraduate and graduate courses such as theory of computation, advanced algorithms, computational biology, and computability and complexity.

Part A

The Sugar Labs Project Anatomy

Contributions

Depending on the students' background, the students can be a content writer, people person, developer, designer, and translator.

Tracker

The general process for submitting a bug: "If you find a bug or would like to report 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 know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github. Then visit the issues tab of the repo, and hit the big green button to report your issue."

There are two types of tickets: defect and enhancement.

The information available for each ticket include the ticket number, summary, status, owner, type, priority, and milestone.

Repository

The last commit is at 13:50 on August 22, 2016. It seems to be a both web-based and local repository.

“Activities

   Monday August 22 2016

   Repository  13:50    gabrielleanderson cloned turtleart/mainline

   New repository is in gabrielleandersons-mainline

”

Release cycle

This is an entry: "Sugar platform release version cycle: | 0.82 | 0.84 | 0.86 | 0.88 | 0.90 | 0.92 | 0.94 | 0.96 | 0.98 | 0.100 | 0.102 | 0.104 | 0.106 | 0.108 | 0.110 | "

The roadmap is updated at the beginning of each release cycle by the release team.

The Sahana Eden Project Anatomy

Contributions

Depending on the students' background, they can be developers, testers, sys. admin, documenters, designers or translators.

Tracker

The tracker page is very similar to the Sugar Labs project, but it can list all active tickets by priority, and color each row based on priority.

There are four types of tickets: defect/bug, enhancement, documentation, and task.

The information available for each ticket include the ticket number, summary, component, version, priority, type, owner, status, and created date.

Repository

Sahana Eden can be installed on several different operating systems. It seems to be a local repository.

Release cycle

I did not find a release cycle. There is a roadmap that shows three milestones.

An example entry： ” Milestone: 0.9.0 "Medway"

5 years late (12/01/11 18:00:00) 92%

Number of tickets: closed: 98 active: 9 Total: 107 “

Part B

Part 1 - SourceForge

2. I used gaming to search in the center of the screen;

3. There are 839 programs under this category.

4. Fifteen different programming languages are used to write software in this category.

5. The top four programming languages used to write programs in this category: C++, Java, PHP, C;

6. Identify the meaning of each of the statuses below:

   Inactive: 
   Mature
   Production/Stable
   Beta
   Alpha
   Pre-Alpha
   Planning 

7. Compare two projects in this category that have two different statuses. Describe the differences between the statuses.

8. Which projects are the most used? How do you know?

9. Pick a project in your category. Answer the questions below:

1) What does it do? 

The Neverhood is a 1996 point-and-click adventure game that is entirely composed of claymation. This does a few things. The project was discontinued in 2013 and has not been updated in years.

2) What programming language is the project written in?

Unix Shell, C++, VBScript, Java

3) Who is likely to use the project? How do you know this?

4) When was the most recent change made to the project?

Last Update: 2015-04-24

5) How active is the project? How can you tell?

It was discontinued in 2013.

6) How many committers does the project have?

7) Would you use the project? Why or why not?

No, it was discontinued.

Part 2 - OpenHub

3. For the OpenMRS Core project, identify when the data in OpenHub was last analyzed and the last commit date. How much difference is there?

It was analyzed about 2 months ago; The last commit date is 3 months ago.

4. What is the main programming language used in OpenMRS Core?

Java

5. How many lines of code does OpenMRS Core have?

3.73M

7. Click on "User & Contributor Locations" (lower right side of screen). List some of the locations of the developers.

Cannot be loaded.

8. Go back to the main OpenMRS page. Click on the "Languages" link. How many languages is OpenMRS written in?

15 different languages.

9. What language has the second highest number of lines of code?

Javascript.

10. Of the programming languages used in OpenMRS , which language the has the highest comment ratio?

Java

12. What is the average number of contributors in the last 12 months?

About 10.

13. Scroll down to the Top Contributors section. How long have the top three contributors been involved in the project?

6 months, 3 years, and 5 years.

14. Use the information on the project summary page to compute the 12-month average of commits. What is the average number of commits over the past 12 months?.

https://www.openhub.net/p/openmrs/commits/summary. 443.

Part C:

Bug-Tracker Activity

2. Define what each of the column names below indicate. Include the range of possible values for 2-7 below. Feel free to explore beyond the page to find more information.

1). ID: a unique ID for each bug

2). Sev: the severity of the bug; normal, minor, major, critical, enhancement, blocker, trivial

3). Pri: priority; low, normal, high, urgent

4). OS: operating system; all, Linux, open, Windows, Solaris, Mac, other

5). Product: which product the bug affects; lots of possible values

6). Status: current status of the bug; unconfirmed, new, assigned, reopened, need info

7). Resolution: no possible values listed; maybe a link to a description of how it was resolved?

8). Summary: summary of the bug

3. Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link)? I sorted each category to see the possible options, and then opened up a bug report and read the longer description to see what was there

4. Identify the order in which the bugs are initially displayed? seems like they're sorted by status

5. What is the meaning of the shading of some bug reports? hmmm… I can't tell; seems like every other entry is shaded, unless it's an enhancement

6. What is the meaning of the colors used when describing a bug (red, gray, black)? red is for blocker or critical status; gray is for enhancements

7. Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number). -- I chose 561837

1). Identify when the bug was submitted. -- 2008-11-21

2). Identify if there has been recent discussion about the bug? -- not since 2013-08-14

3). Is the bug current? -- doesn't seem like it

4). Is the bug assigned? To whom? -- to At-spi maintainer(s)

5). Describe what you would need to do to fix the bug. -- it looks like someone created a patch but no one confirmed it, so I guess I'd need to know whether the patch is okay

8. Repeat the previous step with a different kind of bug. -- I chose 437375

1). submitted 2007-05-10

2). no recent discussion since 2011-06-23

3). doesn't seem current

4). assigned to ATK maintainer(s)

5). this bug describes an ambiguity in the doc; I'd need to make sure that the description is unambiguous using the terminology expected by the intended audience

Source Code Management/Control Activity

FOSS in Courses Planning 2