User:PLee

Patricia Lee

Patricia Lee is an Adjunct Professor in the Computer Science Departments at the University of California Irvine (UCI), California State University Fullerton (CSUF), and Orange Coast College (OCC). All three colleges service the Orange County area in Southern California. She has had the opportunity to work with a diverse group of students, mentors, and colleagues.

Dr. Lee's scholarly interests include (but are not limited to) computing education, hardware design verification, and software engineering in the areas of security, database, and operating systems.

Before teaching, Dr. Lee worked in various technical companies and organizations for over 20 years, mainly in the Southern California area. She is thankful for having had the opportunity to have worked in many different capacities within the computer industry including as software, firmware, and hardware engineer.

In her spare time, Dr. Lee loves the outdoors and enjoys camping, hiking, and mountain biking/road cycling for exercise and transportation. She is a big advocate for public transportation; however, she wishes transportation was more accessible/available, more bike and pedestrian-friendly, and safe for all modes of transportation. She also enjoys indoor activities like reading, playing instruments, and listening to live music (although a lot of this can also be done outdoors, too!).

POSSE_2016_11: Activities

http://foss2serve.org/index.php/POSSE_2016-11
http://foss2serve.org/index.php/Stage_1_Activities

POSSE_2016_11, Stage 1, Part A: Due Oct 5th

To do: Any one with similar interests? http://teachingopensource.org/index.php/Roll_Call

Wikis play the role of a central place where information can be created and disseminated freely. It is flexible and transforms as communities and needs change regarding information needed and available.

To do: Deciding between two projects: Mifos: I like this project because it's such a simple idea that can really help make a difference in someone's life. MouseTrap: I like this project for not just its social impact but also for its interesting aspects with respect to both hardware and software.

To do: Possible deliverables for use with students

• Paper summarizing what students learned about open source
• Description of the difference in the philosophies of the Free Software Foundation and the Open Source Initiative
• Brief description of open source project to which they would like to contribute including possible contributions and why they chose the project

1. How do people interact? They interact like they are in a meeting together in person.
2. What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix? The pattern of communication is a mix of one-to-many and one-to-one. It's fairly linear but sometimes branches into other topics. It is somewhat informal except when certain #info and #action commands are made.
3. Are there any terms that seem to have special meaning? The words with a hash before them appear to have meaning as they are bolded. Also, member names. Basically, anything color coded.
4. Can you make any other observations? It's a great method for holding meetings as everyone can talk without interrupting the other.
5. Why didn't Heidi and Darci's actions get picked up by the meetbot? They seemed to be picked up, but maybe because Darci started the meeting?
6. IRQ commands:

/join #<channelname>
/me <does something>
/msg <nickname> <message>
/nick <new nickname of 9 chars or less>
/notice <nickname> <short message no private window>
/part = leave one channel
/partall = leave all channels in 
/query = like msg with open window
/quit <msg> = leave IRC disconn from svr
/ignore <nickname>
/ignore -r <nickname> = reverses ignore
/whois nickname = for more information
/chat <nickname> (do not accept dcc/chats nor dcc/gets from people you don't know--chat even if server is disconnected)
/help
#startmeeting 
#action #agreed #help #info #idea #link #topic

Projects

Sugar Labs

1. Summarize the roles that you think would be most applicable for your students on your faculty wiki page. If you think that more than a single role is applicable, indicate why. What are the commonalities across roles? What are the differences? All are important. They all communicate with each other through different methods. Even the educator communicates via explanations.
2. Repository -- http://git.sugarlabs.org/sugar-base Scan the "Activities" section on the repository and determine the date of last "Commit" (an update of the repository). Place your answer on your wiki page. Monday March 10 2014, Push, 10:27, dnarvaez pushed 1 commit to sugar-base/mainline:master. View diff, master changed from fb2344a to 39e470e
3. Entry on how the release cycle and roadmap update are related. Each release cycle will include development, beta, release candidate and final releases. The Development Team's Roadmap is updated at the beginning of each release cycle by the release team.

The Sahana Eden Project

1. Roles: Developers, Testers, Bug Marshals, Community Outreach, Designers, Documenters, GIS Specialists, System Administrators, Translators
2. Community -- In the section titled Want to Contribute to Sahana Eden?, you will find a list of ways in which one can contribute. Again, you will note that there are a variety of distinct groups, each with a distinct responsibility. Follow the links to each of the groups listed below and summarize the information you find there on your faculty wiki page. For example, 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? All mainly technical, but similar to the other side, working together for a common goal. This structure is different from Sugar Labs in that it is a bit more like the way a corporation would be structured. Good way to get students comfortable with more "professional" environment. Other one looked good, too, but was a little more like a learning environment where it seemed more egalitarian and less corporately structured somehow.

Comparison

1. Tracker -- The Sahana Eden bug tracker can be found here. Place your answers to the following on your wiki page. How is the information here different than the information found on the Sugar Labs tracker page? This information seems more sortable and well-thought out with respect to sectioning things off in certain ways.
2. Types of tickets: Active, by version, by milestone, by owner (accepted), longer/shorter version, my tickets, etc. A lot of sorting reports are available. Maybe too many?
3. Categories in a ticket: Ticket, Summary, Component, Version, Priority, Type, Owner, Status, Resolution, Creation Date, Modification Date
4. Release cycle -- Information about Sahana Eden's release cycle and roadmap can be found here. Include an entry on your wiki page that describes the information you find here. Shows how versions move from one version to the next and all the work done for each version.