From Fedora Project Wiki
No edit summary
No edit summary
Line 8: Line 8:
Data Engineering ecosystem heavily consist of software that would not go well with Fedora Packaging Guideline. The software tend to be Java/Python/etc software that rely on bundled JARs/Eggs/dependencies which in no way matches with what provided in Fedora.
Data Engineering ecosystem heavily consist of software that would not go well with Fedora Packaging Guideline. The software tend to be Java/Python/etc software that rely on bundled JARs/Eggs/dependencies which in no way matches with what provided in Fedora.


This SIG would not attempt to create packages to be included into the core Fedora repositories, but instead we would be creating "vendor" packages that install these software in `/opt/`, while still providing integration to the rest of Fedora/CentOS ecosystem (`systemd` service files, configs in `/etc` with sane default, `.desktop` file for GUI apps, howtos, etc). For cluster type softwares, we would also create packages of ansible scripts to help deploy the cluster.  
This SIG would not attempt to create packages to be included into the core Fedora repositories, but instead we would be creating "vendor" packages that install these software in `/opt/`, while still providing integration to the rest of Fedora/CentOS ecosystem (`systemd` service files, configs in `/etc` with sane default, `.desktop` file for GUI apps, data directory in `/var/lib`, logs in `/var/log` or `systemd-journald`, howtos, etc). For cluster type softwares, we would also create packages of ansible scripts to help deploy the cluster.  


How we would do this is, we'll create our packages in COPR, and upload them into the SIG COPR group.  
How we would do this is, we'll create our packages in COPR, and upload them into the SIG COPR group.  

Revision as of 04:16, 8 February 2021

Note.png
In process.
We need more participants to help.

Mission

Make Fedora and CentOS a pleasant platform for Data Engineering.

Packages

Data Engineering ecosystem heavily consist of software that would not go well with Fedora Packaging Guideline. The software tend to be Java/Python/etc software that rely on bundled JARs/Eggs/dependencies which in no way matches with what provided in Fedora.

This SIG would not attempt to create packages to be included into the core Fedora repositories, but instead we would be creating "vendor" packages that install these software in /opt/, while still providing integration to the rest of Fedora/CentOS ecosystem (systemd service files, configs in /etc with sane default, .desktop file for GUI apps, data directory in /var/lib, logs in /var/log or systemd-journald, howtos, etc). For cluster type softwares, we would also create packages of ansible scripts to help deploy the cluster.

How we would do this is, we'll create our packages in COPR, and upload them into the SIG COPR group.

We plan to package:

Participants

How you can help

If you have no idea how to help us with making Data Engineering toolings into Fedora here are some proposals where we need help:

  • Packagers: There are so many interesting packages that are not yet packaged for Fedora or need to be updated.
  • Testers: If you want to try the rpms that we prepared and report bugs, We need your feedback to improve it.
  • Documentation: If you would like to make howtos and documents to make the process easier for others to adopt the tools.

Communications

As of now, we are in Fedora Malaysia Discord server. We probably will request an official mailing list if the team get bigger.

Resources

  • TBD. Link to Copr group once we have a FAS group