User:Mellostark

(Difference between revisions)
Jump to: navigation, search
Line 43: Line 43:
 
For each ticket you can find out the Ticket #, Summary, Status, Owner, Type, Priority, Milestone.   
 
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.
 
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

Revision as of 19:16, 14 April 2014

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.


Project Anatomy

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

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