Merge branch 'source' of github.com:neurofedora/neurofedora.github.io into source

Author: sanjayankur31

content/20250602-next-open-neurofedora-meeting-02-june-2025-1300-utc.rst

@@ -0,0 +1,55 @@
+Next Open NeuroFedora meeting: 02 June 2025 1300 UTC
+#########################################################
+:date: 2025-06-02 11:17:04
+:modified: 2025-06-02 11:17:04
+:authors: Ankur
+:category: Community
+:tags: meeting, IRC, Matrix, Element
+:slug: next-open-neurofedora-meeting-02-June-2025-1300-utc
+:summary: The next open NeuroFedora meeting is on 02 June 2025 at 1300 UTC. Please read the post for the agenda and information on how to attend the meeting.
+
+.. raw:: html
+
+   <center>
+
+.. figure:: {static}/images/20200112-image.jpg
+    :alt: Photo by William White on Unsplash
+    :width: 80%
+    :class: img-responsive
+    :target: #
+
+    Photo by `William White <https://unsplash.com/@wrwhite3?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText>`__ on `Unsplash <https://unsplash.com/s/photos/community?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText>`__.
+
+.. raw:: html
+
+   </center>
+   <br />
+
+
+Please join us at the next regular Open NeuroFedora team meeting on Monday 02 June 2025 at 1300 UTC.
+The meeting is a public meeting, and open for everyone to attend.
+You can join us in the `Fedora meeting channel on chat.fedoraproject.org (our Matrix instance) <https://matrix.to/#/#meeting:fedoraproject.org>`__.
+Note that you can also access this channel from other Matrix home severs, so you do not have to create a Fedora account just to attend the meeting.
+
+You can use `this link <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting&iso=20250602T13&p1=1440&ah=1>`__ to convert the meeting time to your local time.
+Or, you can also use this command in the terminal:
+
+.. code-block:: bash
+
+    $ date -d 'Monday, June 02, 2025 13:00 UTC'
+
+
+The meeting will be chaired by `@ankursinha <https://fedoraproject.org/wiki/User:Ankursinha>`__.
+The agenda for the meeting is:
+
+- New introductions and roll call.
+- `Tasks from last meeting <https://meetbot.fedoraproject.org/latest/neurofedora>`__.
+- `Open Pagure tickets <https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting>`__.
+- `Package health check <https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig>`__.
+- `Open package reviews check <https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro>`__.
+- `CompNeuro lab compose status check for Fedora 41/rawhide <https://koji.fedoraproject.org/koji/packageinfo?packageID=30691>`__.
+- Neuroscience query of the week
+- Next meeting day, and chair.
+- Open floor.
+
+We hope to see you there!

content/20250802-packaging-changes-at-neurofedora.rst

@@ -0,0 +1,57 @@
+Packaging changes at NeuroFedora
+################################
+:date: 2025-08-02 14:02:06
+:modified: 2025-08-02 14:02:06
+:authors: Ankur
+:category: News
+:tags: Computational Modelling, Computational Neuroscience, Documentation, Fedora Lab, Neuroscience, FOSS, Fedora
+:slug: packaging-changes-at-neurofedora
+:summary: The NeuroFedora_ team has decided to make a couple of changes to the artefacts that we produce and maintain. Please read the post for details.
+
+The NeuroFedora_ team has decided to make a couple of changes to the artefacts that we produce and maintain:
+
+- The Comp Neuro Lab ISO image has been dropped.
+- We are moving away from packaging Python software that is easily installable from PyPi_ into rpms for the Fedora repositories to testing it out on Fedora.
+
+Over the years that the NeuroFedora_ team has been maintaining neuroscience rpm packages for the Fedora repositories, we have amassed a rather large number, `almost ~500 packages <https://src.fedoraproject.org/group/neuro-sig>`__.
+That is great, and we are extremely pleased with our coverage of the neuroscience software ecosystem.
+However, given that the team is composed of a few volunteers who can only dedicate limited amounts of their time to maintaining packages, we were beginning to find that we were unable to keep up with the increasing workload.
+
+Further, we realised that the use case for including all neuroscience software in Fedora was no longer clear---was it really required for us to package all of it for users?
+
+An example case is the Python ecosystem.
+Usually, users/researchers/developers tend to install Python software directly from PyPi_ rather than relying on system packages that we provide.
+The suggested use of virtual environments to isolate projects and their dependencies also requires the use of software directly from PyPi_, rather than using our system packages.
+Therefore, for software that can be installed directly, we argue that it is less important that we package them.
+Instead, it is more useful to our user base if we thoroughly test that this set of software can be properly installed and used on Fedora---on all the different versions of Python that a Fedora release supports.
+
+So, a new guideline that we now follow is:
+
+- prioritise packaging software that cannot be easily installed from upstream forges (such as PyPi_)
+
+Following this, we have made a start on the Python packages that we maintain:
+
+- we made a list of software that is easily installable from PyPi_
+- we began dropping them from Fedora, and instead testing their usage from PyPi_
+
+The testing involves:
+
+- checking that the software and its extras can be successfully installed on Fedora using `pip`
+- checking that the modules that the software include can be successfully imported
+
+We `automate these tests using PyTest <https://pagure.io/neuro-sig/NeuroFedora/blob/main/f/python-package-usage-check>`__, and a daily report is published on `fedorapeople.org here <https://ankursinha.fedorapeople.org/neurofedora/package-status/>`__.
+
+Our `documentation <https://docs.fedoraproject.org/en-US/neurofedora/>`__ has also been updated to reflect this change.
+We now include two tables on each page.
+One table provides information about the software that can be installed from PyPi_, and so is not included in rpm form in Fedora.
+The other provides information about the software that continues to be included in Fedora, because it cannot be easily installed from PyPi_ directly.
+
+We will continue reporting issues to upstream developers as we have done before.
+The difference now is that we work directly with what they publish, rather than our rpm packaged versions of what they publish.
+
+You can follow this discussion and progress `here <https://pagure.io/neuro-sig/NeuroFedora/issue/580>`__.
+Please refer to the lists in the documentation for the up to date list of packages we include/test.
+
+
+.. _NeuroFedora: https://neuro.fedoraproject.org
+.. _PyPi: https://pypi.org