User:Relkharboutly

(Difference between revisions)
Jump to: navigation, search
(Introduction to IRC)
Line 3: Line 3:
 
Prior to joining Quinnipiac, Dr. Ruby was a full-time Professor at University of Connecticut. She has four years of industrial experience working as a software engineering and IT consultant.
 
Prior to joining Quinnipiac, Dr. Ruby was a full-time Professor at University of Connecticut. She has four years of industrial experience working as a software engineering and IT consultant.
 
In her spare time, Dr. Ruby is mostly spending time with her kids, in the kitchen or at the gym.
 
In her spare time, Dr. Ruby is mostly spending time with her kids, in the kitchen or at the gym.
 
----
 
  
 
== Introduction to IRC ==
 
== Introduction to IRC ==

Revision as of 19:47, 14 October 2014

Ruby ElKharboutly is an Assistant Professor of Software Engineering at Quinnipiac University. The Software Engineering Program is offered in the newly established School of Engineering. Dr. Ruby's research interests include software design and architecture, reliability and performance and software data analysis. Prior to joining Quinnipiac, Dr. Ruby was a full-time Professor at University of Connecticut. She has four years of industrial experience working as a software engineering and IT consultant. In her spare time, Dr. Ruby is mostly spending time with her kids, in the kitchen or at the gym.

Introduction to IRC

  • How to people interact? By sending instant messages to all meeting participants.
  • What is the pattern of communication? No specific pattern. It seems to be a long meeting where each participant sends a message whenever they have something to say.
  • Are there any terms that seem to have special meanings? Yes, all the hash tags such as #info, #action, #topic,
  • Can you make other observations? The time stamp, text after hash tags is bold.

Intro to Project Anatomy: Sugar Labs Project

Teams: Each team has a mission and specific set of responsibilities. Team pages are structured differently for each team.

Bugs: Each ticket has a number, summary, status, owner, type priority and release milestone. Bugs belong to components and are categorized according to priority, severity and bug status.

Repository: Web-based or local? web-based

Release cycle: The roadmap is updated at the beginning of each release cycle

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