User:Sroman

Revision as of 12:16, 8 June 2017

Sara Roman is an Associate Professor at Universidad Complutense de Madrid. She is teaching Operating Systems and Computer Security as part of the Computer Architecture Department. She has also been teaching Ethics and Law for the past 4 years, that is also a part of the CS Degree curriculum, and has developed an interest in FOSS and Free Culture movements.

She is part of the Advisory Council of the Free Software Office of the Universidad Complutense de Madrid (UCM) and has started to tutor FOSS projects for Grade Final Projects, contributing to CONSUL application being developed by Madrid Town Council to promote direct democracy.

She is also collabotarating with Unidad de Igualdad de Genero of the UCM organizing events to make women in Techs visible and to encourage young female students to engage in Techs. She has recently joined the Wikimujeres group in Spain as well.

Stage1 - Part A - Intro to FOSS Project Anatomy

Guided Tour (work in progress)

   Contributions

SugarLabs would be very suitable for the students in Ethics and Law course as thay have already done workshops to teach programming to children in schools as Social Impact Poject. They would be users, and from that experience (which they loved) I would encourage them to become translators, educators, content writers or developers.

   Tracker

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.

If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

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.

   Types/categories of tickets

Defect /enhancement + priority

   "Commits" 

Latest commit: Commits on Jun 5, 2017

   Release cycle and roadmap update 

Communication -- Sugar Labs promotes communication among its community members in the following ways.

   IRC: https://wiki.sugarlabs.org/go/Internet_Relay_Chat
   Mailing lists: http://lists.sugarlabs.org/
   Blog: http://planet.sugarlabs.org/
   Wiki: http://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki 

[edit] The Sahana Eden Project (https://sahanafoundation.org/eden/)

Read the information found here to get an overview of the goals of the project and the types of contributions one can make.

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. On your wiki page:

   Follow the links to each of the groups listed below and summarize the information you find there. 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?
       Developers
       Testers
       Designers 

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?
   Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket. 

Repository -- https://github.com/sahana/eden Click the "Commits" link and determine the date of last commit (an update of the repository).

   Record the date on your wiki page. 

Release cycle -- Information about Sahana Eden's release cycle and roadmap can be found here.

   Include a brief entry on your wiki page that summarizes the information you find here. 

Communication -- Sahana Eden promotes communication among its community members in the following ways.

   IRC: http://eden.sahanafoundation.org/wiki/Chat
   Mailing lists: http://wiki.sahanafoundation.org/community/mailing_lists
   Google Groups: https://groups.google.com/forum/?fromgroups#!forum/sahana-eden 

[edit]

Stage 1 - Part B - FOSS Field Trip

(work in progress)

1. Go to: https://github.com/ 2. Use the Search feature on the top right next to the Log In button to search for educational applications by placing the word education in the search box and click Search. 1. How many repositories are there in this category? 13,373 repository results 2. Click on the first project. Click on Graphs, then Commits. What information does this page provide?

I found contributions of people in this project from most recent to older ones, for both branches in the project. There were 28 commits. Graphs shows contributions by people during the lasta year.

3. Go back to the main page and use the Search feature to look for humanitarian applications. Type the word humanitarian in the search box and click Search. 1. How many repositories are there in this category? 300 2. Locate the HTBox/crisischeckin project. When was the last update? 04/22/17 4. Use the Search feature to look for disaster management applications. Type the phrase disaster management the search box and click Search. 1. How many projects are there in this category? 150 Keep this browser tab open while you move onto Part 2.

Stage 1 - Part B - Project Evaluation

Evaluation Factor Level (0-2)

Total Score: 13

I also found that: https://openmrs.gitbooks.io/developer-manual/content/en/ does not exist

Stage 1 - Part B - Introduction to Copyright and licensing

1. Identify the license for the following projects:

   https://github.com/openmrs/openmrs-core  --- Mozilla 2.0 Free   comfortable
   https://github.com/apache/incubator-fineract --- Apache 2.0 Open comfortable 
   https://github.com/regulately/regulately-back-end ((c) by default) not very motivated to contribute

2. Go to https://tldrlegal.com/ . Look up each of the above licenses. Identify the “cans” the “cannots” and the “musts” for each. 3. For each license, state whether you would (or would not) be comfortable contributing code to that project and why (or why not).