User:Marcos

From Foss2Serve
Revision as of 09:42, 9 June 2017 by Marcos (Talk | contribs)
Jump to: navigation, search

Marcos Sanchez-Elez is a Assistant Professor at Arquitectura de Computadores y Automatica Department at Complutense University (UCM), SPAIN. And Computer Engineering Degree coordinator. Marcos is deeply involved in all aspects of the Computer Science program including content, review, and assessment. Moreover, he is part of the university free and open software advisory council, it promotes the usage of FOS in the subjects and.

- ResearchGate Profile [1]

Contents

Part A

Intro to FOSS Project Anatomy

The Sugar Labs Project

  • Community

The roles that I think would be most applicable for my students are:

- Educator: They are used to study through digital media and interetsing in teaching digital concepts. Moreover, the teaching activity ensures that the students who explain the concepts to a third party acquire those concepts better.

- Translator: They could translate technical and non technical concpet to Spanish

- Developer: they can programn in Python, C, and JavaScript, they know about web app development and GNU/Linux system administration.

  • Tracker:

The general process for submitting a bug:

1) If you would like to find a bug, first check if that part of the project is beeing modified

2) Then download the last version

3) Finally visit the issues tab of the repo, and hit the big green button to report your issue (https://github.com/sugarlabs/sugar/issues)

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

The types of tickets are: defect, enhancement, task. It is also necessary to indicate the priority (Low, Medium, High, ...).

Inside each ticket you have to indicate severity, bug status, version, description ...

  • Repository

Record the date of the last commit: June 5 2017

  • Release cycle

Describe how the release cycle and roadmap update are related.

The Release cycle and the Roadmap updated are related because the roadmap is aupdate at the beginning of each release cycle. Then the roadmap includes detailed schedule of release dates while the realse cycle have to ensure that all the module releases are available by this scheduled.

  • Communication

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


The Sahana Eden Project

  • Community

Developers, Testers, Bug Marshals, Newsletter Report Writers, Documenters, Translators, Designers, SysAdmin and GIS Specialists.

Broadly speaking, the two projects have the same roles but with different names. However, there are three specific roles related with bug, test and SysAdmin that in Sugar-Lab project is inside the Developer role. In sugar-lab project there is a people person role that should have more social skills and have more responsibility than the role of Newsletter Report Writers

The roles that would be most applicable for my students are developers, testers, translators and Bug Marshals

  • Tracker

There are more information than in the Sugar-Lab page, I found the component column very interesting. Inside each ticket the information is very similar in the two analayzed projects.

The types are: enhancement, task, documentation, and defect/bug

  • Repository

Record the date of the last commit: June 5 2017

  • Release cycle

There are three different roadmap, related with three different milestone. But the roadmap schedule is not as clear as in the case of sugar-labs project.

  • Communication

IRC: http://eden.sahanafoundation.org/wiki/Chat Mailing lists:

Wiki: http://wiki.sahanafoundation.org/community/mailing_lists

Google Groups: https://groups.google.com/forum/?fromgroups#!forum/sahana-eden

Part B

FOSS Field Trip (Activity)

Part 1 - GitHub

https://github.com/

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? The commits stored by date. You can also access to the two branches. You can also check the colosed pull request and the closed issues. 28 commits, 2 branches


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.

- How many repositories are there in this category? 300

- Locate the HTBox/crisischeckin project. When was the last update? 04/22/17 - Use the Search feature to look for disaster management applications. Type the phrase disaster management the search box and click Search. How many projects are there in this category? 150

Project Evaluation

Evaluation Factor Level (0-2)

Aspect Score Comments
Licensing 2 Copyleft License
Language 1 Java
Level of Activity 2 Last quarter very good activities
Number of Contributors 2 It seems that there are only 6 contributors really active
Product Size 1 Not sure
Issue Tracker 0 No issue tracker found
New Contributor 2
Community Norms 1 Not very easy to locate
User Base 2 https://atlas.openmrs.org/
Total Score 13

Intro to Copyright and Licensing (Activity)

Identify the license for the following projects:

Project License
https://github.com/openmrs/openmrs-core Mozilla 2.0 Free
https://github.com/apache/incubator-fineract Apache 2.0 Open
https://github.com/regulately/regulately-back-end It seems (c)

FOSS in Courses

This work is the result of a very nice discussion with Sara Roman with whom I share an Ethics and Law course at UCM (Course wiki in English (created by the students))

The contents of this course deal with Social and Ethical issues in Computer Science Professional Practice. Our students have to develop a Social Impact group Project as part of the course. We encourage them to participate in a FOSS project and we think that any of the HFOSS projects we are reviewing are very suitable for them.

We believe our students could participate in the following activities:

  • Activities related with their programming background (they are in their last year of CS):

Diagnose a bug

    • Test a beta or release candidate
    • Fix a bug: for very motivated students only
    • Report bugs
    • Run usability studies

Non-technical activities in which their technical background is very valuable:

f) Suggest new features and options

g) Build a glossary of technical terms (already done projects like this)

h) Package the application for a particular Linux distro (or other OS)

i) Read relevant standards and make sure the program follows them

Non-technical activities that we believe they would enjoy to collaborate with:

j) Translate the documentation (and program text) to another language

k) Correct spelling and grammar mistakes in documentation – Check the information pages in Spanish

l) Submit graphics (icons, backgrounds) to use in the program: for very motivated students only

m) Provide training to new Linux users (already done projects like this)

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