From Foss2Serve
Jump to: navigation, search

Suzanne Mello-Stark studies digital forensics, cryptography, security and networking implementations in current election technologies. She is an affiliated faculty member at University of Connecticut’s Center for Voting Technology Research (VoTeR Center) as well as a faculty member in the Computer Science and Statistics department at the University of Rhode Island.

Suzanne is an ardent supporter of the Anita Borg Institute. She currently serves as the co-chair for the security track committee for the Grace Hopper Celebration of Women in Computing Conference (GHC). The Inspiring Women Scientists Conference at the CUNY Graduate School and University Center, and the Feminist Press recently invited her to speak about her career path to young women interested in STEM.

Dr. Mello-Stark’s broad range of experience in academics, business development, hardware/software, and network and security management has landed her positions in both the public and private sector.

Suzanne holds a PhD in computer science from the University of Rhode Island, a MBA from Babson College, and a graduate level certificate in Digital Forensics from University of Rhode Island’s Digital Forensics and Cyber Security Center.

Suzanne is passionate about improving computer science education, k-12 and college level, through research interests and modern teaching pedagogy. She is a member of the Association for Computing Machinery (ACM) and the Society of Women Engineers (SWE).

Intro IRC Activity

Part 1 - Questions How do people interact? - very much like text messaging What is the pattern of communication? - It seems to go over a long period of time. Are there any terms that seem to have special meaning? - Yes, I see many in the sample chat. I have not seen a real conversation yet. Can you make any other observations? - I love that the meeting agenda can be automatically drawn up from the meetbot.

Part 3 Summarize your observations (of your selected HFOSS project) on your faculty wiki page.

I selected the GNOME project. I sat on the channel for awhile and watched people join and leave the chat room. I also am participating in Google Summer of Code and am hanging out on that channel. Same story. I will keep all the channels open over night and see if something happens.

Sugar Labs

Community Activity

Summarize the information for (show commonalities and differences):

Activity Team - Goal is to provide high quality activities for Sugar. This site lists responsibilities and tips. On their contact page they have many contributors and 2 coordinators. There is a mailing list and IRC channel. Development Team - Goal to build and maintain the environment. Works closely with design team. There is currently no coordinator and 4 developers.The IRC channel is also listed. Documentation Team - This is the most extensive page as expected. There are many manuals maintained here. On the contact page there is a mailing list and the IRC channel information. Two editors are listed.

All three teams list the players and how to get in touch with them. There seems to be a lack of coordinators.

Tracker Activity

indicate the types/categories of tickets listed on this page as well as the information available for each ticket:

A ticket can be accepted, assigned, closed, new and/or reopened. If you click on a ticket you can get more information. For each ticket you can find out the Ticket #, Summary, Status, Owner, Type, Priority, Milestone. You can organize the list by category. For example if you want to find all the high priority defects or create a list of enhancements by priority.

Repository - Web-based or local repo? web-based

Release cycle - Describe how the release cycle and roadmap update are related: The roadmap is updated at the beginning of each release cycle.

The Sahana Eden Project Activity


Are there any commonalities? Is there something distinct for each type of contributor? How is this structure different than the one you found on the Sugar Labs website?

Developers -This group does not have a contact list, but a mailing list and IRC Chat. They have lots of guidelines and training available. Testers - They are also looking for non-techies to help assist in testing. Information on system integration also available. Designers - There are looking for graphic designers to help with the application and website. They have guidelines on themes and usability available.

This community seems to be more focused on guidelines and less focused on the players.

Tracker Activity

How is the information here different than the information found on the Sugar Labs tracker page? - This page has the bugs broken down into reports.

Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket. When you click on a report you get the same information as sugar labs.

Repository - web-based or local repo? local-repo

Release cycle -They have a very basic roadmap available right on the release cycle page. They seem to be two years late on their milestones.

FOSS Field Trip Notes Part 1 SourceForge – I searched for voting since this is one of my research areas. There are 11 pages of projects listed. There are 15 programming languages. The most popular is PHP, Java, JavaScript and Python. 1. Compare two projects in this category that have two different statuses. Describe the differences between the statuses.

Php simple voting system – alpha state 90 weekly downloads - This application is written in php to create a php+mysql based voting system. There are no reviews.

Tunez - Tunez is an MP3/Ogg Vorbis jukebox that works with a voting system. It is ideal for LAN parties since it allows all users to have input into what is played (or streamed). Beta status – 4 downloads. This system is further along that the above but is not as popular.

2. Which projects are the most used? How do you know? Php simple voting system because of the number of downloads.

Pick a project in your category. Answer the questions below: E-Voting Application 3. What does it do?

e-Voting Application is an open source project aiming to create an e-voting system which complies to European e-Voting standard and EML specification. 4. What programming language is the project written in?


5. Who is likely to use the project? How do you know this? End Users/Desktop, Government – that is the intended audience 6. When was the most recent change made to the project? Last updated 2012-05-29 7. How active is the project? How can you tell? There are 2 people and have performed 3 commits 8. How many committers does the project have? It looks like 2 people are using this project 9. Would you use the project? Why or why not? I need to investigate more.

Part 2 – Ohloh 10. What is the main programming language used in Mifos? Java 11. How many lines of code does Mifos have? 2.67 m 12. Click on "User & Contributor Locations" (lower right side of screen). List some of the locations of the developers. 13 US, Europe one from Asia 13. Go back to the main Mifos page. Click on the "Languages" link. How many languages is Mifos written in? 19 14. What language has the second highest number of lines of code? XML has 515,397 15. Of the programming languages used in Mifos, which language the has the highest comment ratio? Perl has 28% 16. Click on the “Contributors” link under "SCM Data" menu. 17. What is the average number of contributors in the last 12 months? 10 contributors 18. Scroll down to the Top Contributors section. How long have the top three contributors been involved in the project? Lukasz Gasior 1 year 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?. 215 commits

Part 3 - Uploaded Mission Critical Template Media:Mello-Stark_Template.xlsx

Part 4 - I would like to incorporate many of the activities from this course in my software engineering course. In the Fall, I already have 40 students and 2 on the wait list. I may have all students learn about FOSS. I think one of the best ways to begin is to work on documentation and possibly bug fixes and testing. That is how you mostly start (at least that is how I started) in the real world. What I need to work on is establishing real milestones that are measurable for students. It is certainly an interesting and valuable learning experience for everyone.

Bug Tracking Activity

1. 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. ID – Bug Number Sev – Severity Level – critical, major, normal, enhancement, Pri – Priority – Urgent, Normal, High OS – Operating Systems – All, Linux, Mac, Solaris Product – the product name Status - New, Assigned, need info, unconfirmed, reopened Resolution – how it was fixed, couldn’t find an example Summary – gives a summary of the issue. 19. Describe how you discovered the definitions and How did you find the information from above? I just looked for examples. I am familiar with bugs so know how to track them. But then I found the link after I was done:

20. Identify the order in which the bugs are initially displayed? I don’t know. I have been moving them around. 21. What is the meaning of the shading of some bug reports? I can’t find the meaning. 22. What is the meaning of the colors used when describing a bug (red, gray, black)? Red is critical, gray is normal, don’t see a black one. 23. 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 picked bug 36343 because it was documentation. Identify when the bug was submitted. 2006-10-19 15:36 UTC by Aaron Leventhal Identify if there has been recent discussion about the bug? Is the bug current? No Is the bug assigned? To whom? ATK maintainer Describe what you would need to do to fix the bug. Change the documentation Part 2 - Collective Reports 1. Click on the “Reports” link on the top of the page. 2. How many bug reports were opened in the last week? How many were closed? 378 were opened and 372 were closed. 3. What was the general trend last week? Were more bugs opened than closed or vice versa? More were open but it was close. 4. Who were the top three bug closers? Why is this important to know? Matthias Clasen, Michael Schumacher and Jim Nelson. It is important to know because they are active and could help you. 5. Who were the top three bug reporters? Jim Nelson, Kat and Yosef Or Boczko. Are these the same as the top three bug closes? Jim is overlapped. What is the overlap in these two lists? People who find, report and fix bugs. 6. Who are the top three contributors of patches? Yosef Or Boczko, Florian Mullner, Egmont Koblinger 7. Who are the top three reviewers of patches?Sebastian Droge, Bastien Nocera, Matthias Clasen. What is the overlap between these lists and the bug closers and bug reporters? People actively working on fixing and releasing new versions of the products. What is the overlap between patch contributors and patch reviewers? There is some overlap here as well. Some people are both creating and reviewing patches. 8. Click on the “Generic Reports” link. 9. Plot the Severity of each Version of the Accessibility features of Empathy.

   I created a nice bar chart but it doesn't show up here.

What other reports can you generate? There are too many to count.

Git Hub Activity

I completed the GitHub activity and received my badge. I have used this tool before on real projects.

Course Activities

In my software engineering course, students will have in class activities to use git hub and bug tracker.

Personal tools
Learning Resources
HFOSS Projects