Follow up with third-party projects about packaging plans

[jwflory]

Summary

We need to follow up with some third-party projects about their plans for packaging and if we can include the software in TigerOS before the first release.

Background

Earlier, we reached out to various third-party projects that RIT uses for software in labs. Some of them had licensing issues or weren't packaged yet for Fedora. Some of them gave hard, "yes" "no" answers, others were interested but needed follow-up later.

Details

We need to follow up with some of these projects about any changes or updates before the next release. It will be helpful if we can include software that students are already familiar with, and if the upstream projects are cooperative, then we can help make it happen. To do this, we need to follow up with those projects.

Action

1. Identify projects to follow-up with
2. Find contact info for those projects, email asking for update on licensing / usage for TigerOS
3. If positive answer, work on packaging apps for Fedora, to be included in TigerOS (whether packages proper or via COPR)

[jwflory]

As a minor comment about JGrasp, if it's not feasible, check out DrJava.

[axk4545]

waiting to hear back from adviser about licensing before pursuing further

[jwflory]

Discussed in our weekly meeting.

Re-evaluate third-party packages

We want to re-evaluate our approach to third-party software in TigerOS. We want to make this third party software easier to manage from the TigerOS perspective while complying with license terms.

Next, we want to follow up with the upstream projects and have a new conversation about licensing. We want to ask upstreams if…

1. They are interested in making RPMs and hosting / sharing them for us, or
2. If we want to ask for a special exception to the license for packaging it ourselves.

The projects we want to follow up with are…

• JGrasp
• JFlap
• MIT Alloy (note: multi-licensed project, uses many libraries)