Hello everyone! Coming in hot, new edition is here! Well, actually it is a bit late isn't it? In this edition, we will talk about packaging, our website and documentation, cleanup crew, funding and some bonus stuff in the end.
Welcome to the sixth edition of Contributor Roundup!
Packaging
We have 18 authors that committed to the packages repository, amounting to 875 commits in the month of April.
There are few changes to the Packaging workflow in April. It is mostly about the debundling of pip from python3 package. Here is the changelog:
pip3 and setuptools debundled from python3
- pip3 and the python module setuptools are no longer provided by
python3
python-setuptools now provides the py3 version of setuptools instead of the py2 versionpip now provides the py3 version of pip instead of the py2 version- A temporary package
python2-setuptools provides the py2 version of setuptools pending full python2 deprecation
- A temporary package
pip2 provides the py2 version of pip pending full python2 deprecation
- PEP517 is now the preferred method to build python modules
- The
%python3_setup macro now attempts to build python modules with PEP517 if a pyproject.toml file is found, it will fallback to setuptools otherwise
- The
%python3_install macro now attempts to install python modules with PEP517 if a pyproject.toml file is found, it will fallback to setuptools otherwise
- If a python module contains a pyproject.toml file and now fails to build it'll minimally need
python-build and python-installer. Then, it'll need the python build system,
in 90% of cases it'll be python-setuptools, and, python-wheel may also be required. Note, however, there are several valid python build systems such as python-flit-core, python-poetry,
meson-python as well as others that may be used in place of python-setuptools. However, in the majority of cases only python-build, python-installer and python-setuptools are required
- If a python module doesn't contain a pyproject.toml file and instead contains a setup.py file it'll need
python-setuptools as a build dependency
All previous changes to packaging workflow are kept in "Packaging Changes" page in the help center.
We still have 8 open issues tagged as "Good First Issue". Grab one while it is still there!
Solus Cleanup Crew
There is a new cleanup task: fixing packages with insecure or dead homepage. Repology flagged this issue on our repository and we have to address it. This task is also newbie friendly, so if you want to try packaging for Solus, this is a good start.
We addedmonitoring.yaml files to 137 packages. We also added AppStream metainfo to 4 packages this month. Here are the tasks that still need to be done and their progress:
Website and Documentation
There are 9 authors that contributed 6 commits this month to the website and documentation repository. We also have a few open issues on our documentation and website repositories:
We are still looking for help with web development, especially someone withhugo experience. Please get in touch.
Contribute?
If you are interested in helping with packaging, cleanup crew, website or documentation, these are the steps:
- Join the Solus Packaging Room and Development Room on Matrix
- Read and practice our documentation
- Submit your first Pull Request. We recommend doing any of the issues labeled as "Good first issue" in the respective repository. (Packaging, Website, Documentation)
- Follow the review process until your PR gets merged.
- Don't hesitate to ask any questions in our Matrix rooms.
- Congratulations on your first contribution!
- Keep on contributing.
Funding
Your financial contributions make all of this possible. If you have the spare funds, we offer perks on our Open Collective page. Here are the number of people that support us regularly (at the time of writing):
- 8 people in Crew tier, +1
- 43 people in Release Testers tier, +2
- 14 people in Beta Testers tier, +1
- 30 people in Backers tier, +1
- 14 non-tiered donations, +0
Become a backer with just $1 USD!
The Year So Far
Bonus section! Going forward every four month period, we will be posting charts to show how much progress we made. It will (at least) recap the sections above or any other interesting statistics we can come up with. First off, the Cleanup Crew tasks progress chart:
We finally closed two long-standing tasks in this period. Hopefully we can close some more in the next period. Next is the commits count chart:
This chart covers commits that was committed to packages, website and help center repository. While commit count is not exactly a measure of project success, it does at least indicate the level of activity and maintenance. Good thing is we do have a pretty steady stream of commits each month. Hopefully, it will grow more with more contributors coming in. The last, we have chart for the donations on Opencollective:
There is a little bit of growth in the four month period. Right now, the donations can cover all of our infrastructure expenses and give a bit of compensation for contributor's time. We cannot say it enough that we are grateful for all the support the community gave us. Thank you!
That is all from us in this edition of Contributor Roundup. Until next time, cheers!
