tac icon indicating copy to clipboard operation
tac copied to clipboard

Mainframe Software Hub for Linux

Open pleia2 opened this issue 8 months ago • 3 comments

Name of the project: Mainframe Software Hub for Linux

Project description:

The project will provide open source packages not available in distribution repositories or community-provided packages for easy consumption

  • It caters to Linux on Z customers' strong desire to experiment with new open source technologies that haven't yet reached several supported Linux distributions and CI of open source communities
  • The project builds, packages, and provides open source packages in their native form, including binary, RPM, DEB, or container images
  • Historically, since 2015, build instructions and scripts are provided to users on GitHub which are useful but sometimes hard to consume – this project aims to complement that by providing binary artifacts
  • Existing comprehensive build instructions and scripts are available on GitHub: https://github.com/linux-on-ibm-z/docs/wiki
  • The status of most packages is displayed on the IBM community page: https://community.ibm.com/zsystems/oss/

Statement on alignment with Open Mainframe Project Mission and Vision statements:

  • Since all the projects are open source, the project fits well within the Open Mainframe vision to make sure there's a simplified procedure for users to access a rich set of open source binaries on Linux on Z

Are there similar/related projects out there? If so, what is different about this project?

  • Not to our knowledge, though there have been some companies who have released open source binaries as part of their offering.

Sponsor from TAC: Joe Bostian

Proposed Project Stage: Incubation

License and contribution guidelines: Most of the Build Instructions and Scripts are Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)

Source control: GitHub

External dependencies (including licenses): None

Initial committers (coming soon, list will be in follow-up comment)

Infrastructure requests (CI / build infrastructure): Infrastructure to build and host generated artifacts

Communication channels

  • GitHub issues
  • Mailing list

Issue tracker: GitHub

Website: We only require a distribution mechanism for the binaries, which may have a centralized location on some kind of website.

Release methodology and mechanics: Based on community currency release cycle

Social media accounts: None planned

Community size and any existing sponsorship: At least 30 active contributors: IBM, Persistent Systems Limited (note: PSL involvement is managed by IBM)

pleia2 avatar Apr 09 '25 16:04 pleia2