User:Szelikovitz

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(8 intermediate revisions by one user not shown)
Line 96: Line 96:
 
| '''Community Norms'''
 
| '''Community Norms'''
 
|2
 
|2
|Data model: naming tables: all lowercase names with underscores (_) between words  Columns: Use lowercase with underscores (_) between words Auto-generated numeric primary keys are <table name>_id  Interaction that I read is respectful and casual
+
|database table naming conventions, primary key naming conventions
 
+
 
|}
 
|}
 +
'''License'''
 +
OpenMRS: Mozilla Public License 2.0
 +
Adobe: Adobe
 +
regulately_ MIT
 +
I would be comfortable to use any of these licenses for my work
 +
 +
'''Bug Trackers'''
 +
#Fields
 +
## ID
 +
## Product  way of classifying under top level of Classification
 +
## Comp  Component, classification under Product
 +
## Assignee person responsible for bug
 +
## Status current state of bug
 +
## Resolution  what happened to bug
 +
## Summary summary of what the bug is all about
 +
# See https://bugzilla.gnome.org/query.cgi?format=advanced and https://bugzilla.gnome.org/page.cgi?id=fields.htmlfor the possible values of these fields
 +
# By ID
 +
# Colors?
 +
 +
'''Reports'''
 +
 +
* How many bug reports were opened in the last week? How many were closed? 2 reports opened and 12 reports closed
 +
* More bugs were closed than opened.
 +
* List has only 2 closers, no reporters! Maybe because it was a holiday weekend?
 +
* Lists NO patch reviewers!
 +
* What class were the majority of the bugs for braille? Core, Infrastructure, Applications

Latest revision as of 17:01, 26 December 2018

Name: Sarah Zelikovitz

Position: Associate Professor, Department of Computer Science College of Staten Island of CUNY, 2800 Victory Blvd, Staten Island NY 10314

email: sarah.zelikovitz@csi.cuny.edu

Page: http://www.cs.csi.cuny.edu/~zelikovi


Sugar Labs Project Questions: At this point, most of my CS students would fit best into the role of developer. Some can be content writers or designers. For any of these roles, students would need to become familiar with Open Source Software community and norms -- ways of documenting, collaborating, contributing. Bug tracking is done through GitHub. Last Commit Latest commit 35e100f 13 days ago

Sahana Eden Project Questions:

Interesting that offers paid projects as well. Sahana Eden has dedicated pages to bugs and open problems -- these are stored in a database so that bugs that match specific criteria or types can be listed. Sahana also has RoadMaps and Timelines (with info on how much of it is done, but no concern about finishing?) Last Commit Latest commit d2f0925 2 days ago


GitHub Education Repositories:24,843 repository results

You can see a graph of commits by year/month/week

Humanitarian applications: 460 repository results

HTBox/crisischeckin project. Last update: Oct 24

Disaster management applications: 44 results

OpenHub Education 2260

KDE Education: Not on GitHub

Similar Projects: 4

OpenHub provides: lines of code, activity, community

Humanitarian: 30

Disaster management: 30

Projects do not have activity information available when data is not accessible by Open Hub (especially recent data).

Organizations: Foundations, organizations, agencies, communities

OpenMRS

OpenMRS Core: 10 month ago

GitHub OpenMRS Core: 1 day ago

Different people use the different platforms. Is code consistent?

Evaluating HFOSS


Evaluation Factor Level
(0-2)
Evaluation Data
Licensing 2 Mozilla Public License 2.0
Language 0 Java 96.2% SQLPL 2.9% Other 0.9%
Level of Activity 2 All quarters active, but much more activity in first quarter
Number of Contributors 2 313
Product Size 1 223.07 MB
Issue Tracker 2 Open 1318 Closed 13546 5th most recent: 2018-12-13 09:28:18 GMT
New Contributor 2 wiki, web presence, platform for download, email address, openmrs talk
Community Norms 2 database table naming conventions, primary key naming conventions

License OpenMRS: Mozilla Public License 2.0 Adobe: Adobe regulately_ MIT I would be comfortable to use any of these licenses for my work

Bug Trackers

  1. Fields
    1. ID
    2. Product way of classifying under top level of Classification
    3. Comp Component, classification under Product
    4. Assignee person responsible for bug
    5. Status current state of bug
    6. Resolution what happened to bug
    7. Summary summary of what the bug is all about
  2. See https://bugzilla.gnome.org/query.cgi?format=advanced and https://bugzilla.gnome.org/page.cgi?id=fields.htmlfor the possible values of these fields
  3. By ID
  4. Colors?

Reports

  • How many bug reports were opened in the last week? How many were closed? 2 reports opened and 12 reports closed
  • More bugs were closed than opened.
  • List has only 2 closers, no reporters! Maybe because it was a holiday weekend?
  • Lists NO patch reviewers!
  • What class were the majority of the bugs for braille? Core, Infrastructure, Applications
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox