This is my HFOSS home page.
Some things about me. I'm a sociologist, I teach at Lehman College, I coordinate data science at Lehman, I have a crazy amount of github repositories. Currently my main open source work is maintaining two R packages, skimr and qcoder. In the past I was a contributor and maintainer for the Joomla CMS.
My website is elinwaring.org.
Guided tour responses
The Sugar Labs Project (http://sugarlabs.org/)
Read the information found here to get an overview of the goals of the project and the latest news.
Contributions -- Getting Involved
This is really going to depend on what kinds of students I get. For example I think that it's unlikely I will have students who are designers (although you never know) but documenters and other content writers are possible and developers are definitely possible. I like the tone of these descriptions and the way each one is an umbrella for a number of possibilities. IT worries me that so much of the wiki content is from 2009.
I love the "what can you do an an hour" concept.
The main tracker now seems to be on github issue tabs. The basic process is to describe what you were trying to do, what you did, what you expected to happen and what did happen. I like that they also include "workaround" as part of this. Probably there are other users using the workaround. Repository -- https://github.com/sugarlabs/sugar/
date of last commit :
Oct 24, 2018 Release cycle -- Information about Sugar's release cycle and roadmap can be found here. On your wiki page:
- Describe how the release cycle and roadmap update are related.
According to the documentation the roadmap for a release is defined at the start of the release (just after the release of ta version)
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, bug marshalls, newsletter writes (no link), documenters (no link), translators, designers, sysadmins, GIS specialists.
Tracker -- The Sahana Eden bug tracker can be found here.
The tickets seem very old. There are 37 categories of tickets, including one that is easy bugs for beginners. It looks to me like they may have moved to github issues.
Comparing the bug trackers for the two projects, they tend to contain similar information.
Repository -- https://github.com/sahana/eden Click the "Commits" link and determine the date of last commit (an update of the repository).
Dec 3, 2018
Release cycle -- here.
7 years late ... that's a bit worrisome, but maybe its sardonic? Is that how old the project is? Interesting that the others don't have dates. Also there are not a lot of details, it's more like a todo list with assignments
Edication; How many repositories are there in this category? 24,719
Click on the first project. Click on Graphs (Insights), then Commits. What information does this page provide?
How people contribute to and interact with the project.
How many repositories are there in this category? 457
Locate the HTBox/crisischeckin project. When was the last update?
How many projects are there in this category?
Identify the license for the following projects (look for a LICENSE file in the project's root; if it's not there assume no license):
Mozilla Public License, version 2.0 GPL compatible. Copyleft.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
The main thing with apache is the patent rights and allowable for "commercial" use. It is not GPL compatible
https://github.com/regulately/regulately-back-end doesn't seem to have one
Go to https://tldrlegal.com/ . Look up each of the above licenses. Identify the “cans” the “cannots” and the “musts” for each. For each license, state whether you would (or would not) be comfortable contributing code to that project and why (or why not). I'm basically comfortable with both though in general I would prefer GPL.
My course would be a potential new course that would have an open data/data for good focus, and the project would ideally be one where students could be doing something related to data such as creating a way to access the API for a project to feed into data analysis. The food project may be good for this but there may be others too.
One activity that's accessible is reading and making suggestions/edits to documentation. Have students follow the documentation for something and make suggestions for improvements. Also depending on the students, look at end user documentation or developer documentation.
I like some of the ideas for intro to git.
Interested to see gitlab ... the searching seems good and the UI seems fine.