From Fedora Project Wiki
Line 71: Line 71:


== Scope ==
== Scope ==
* Proposal owners: These are a set of mostly research packages that do not demand any changes from the main distribution. Any potential dependencies not currently available will be packaged and included.
* Proposal owners: {{User:ignatenkobrain|Igor Gnatenko}}


<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
These are a set of mostly research packages that do not demand any changes from the main distribution. Any potential dependencies not currently available will be packaged and included.


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 21:08, 10 November 2015


NeuroFedora

Summary

The focus of this SIG is to package and support neuroscience and neuroimaging applications, libraries and datasets on Fedora from the next release on. These packages will enable researchers to use Fedora in all aspects of their work from the design of experiments, data collection, data processing/analysis, data modeling and simulations through to visualization and report generation.

Owner

SIGs/NeuroFedora

Current status

  • Targeted release: Fedora 24
  • Last updated: 2015-11-10
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The goals of the NeuroFedora SIG were developed watching the success of the highly lauded | NeuroDebian project in promoting the usage of free and open source software in the neuroscience community. Their effort has not only provided an easy means for researchers to install packages but it has helped improve the software engineering practices of the community as well as spawn a number of spin off developments in terms of VM images, USB sticks and AMIs that have contributed to both scientific research and education. We hope to use and contribute to the work they have done to improve build systems, test harnesses and quality assurance procedures for the community.

As with any scientifically focused SIG, there will be a great deal of overlap with other SIGs. Like most researchers, we use Python, R and Octave computational environments for both rapid prototyping and established toolboxes. Each of these environments has large ecosystems of packages and toolboxes that are widely used and make up the basis of the Science Spin. We will complement these with the addition of big data and machine learning tools and toolboxes that are of use to all disciplines even though some of these developers are focused on neuroscience and neuroimaging in particular. Finally, scientific literature is more likely to utilize LaTeX for documents which requires its own set of associated tools (TeXLive, BibTeX, etc.). NeuroFedora will be an active contributor to many aspects of the Fedora Scientific community.

Benefit to Fedora

These packages bring potentially thousands of researchers and clinicians into the Fedora community as well as providing the basis for a possible Fedora Spin in the future. There is some overlap in the packages covered that include packages of interest to other SIGs such as Fedora Medical, Fedora SciTech as well as BigData and ML. Researchers are also very likely to use and test systems locally but production runs of analysis are usually managed on clusters using server or cloud instances and as such will see usage across all .


Scope

  • Proposal owners:
Igor Gnatenko
Personal information
Location: Brno, Czech Republic
Birthday: 23th December
Homepage: https://blogs.gnome.org/ignatenko/
E-mail: i.gnatenko.brain AT gmail DOT com
GPG key: 1BBC5F4C
Contact information
IRC: ignatenkobrain on irc.libera.chat
#fedora-devel, #fedora-rust, #fedora-python, #fedora-modularity, #rpm.org, #rpm-ecosystem, #fedora-releng, #fedora-admin​
Twitter: ignatenkobrain
Facebook: ignatenkobrain
LinkedIn: ignatenkobrain
GitHub: ignatenkobrain
GitLab: ignatenkobrain

Fedora-specific information
FAS name: ignatenkobrain
Fedora e-mail: ignatenkobrain@fedoraproject.org
Fedora homepage: ignatenkobrain.fedorapeople.org
 


Igor Gnatenko

General Info

My name is Igor Gnatenko. I am using Fedora since 2013. Since 2014 I am contributing into Fedora in different ways, but primarily as a package maintainer.

Contact

  • Email: ignatenkobrain AT fedoraproject DOT org
  • ignatenko AT gnome DOT org
  • i.gnatenko.brain AT gmail DOT com
  • Fedora Account: ignatenkobrain
  • IRC nick: ignatenkobrain
  • Location: Brno, Czech Republic

Activities within Fedora

  • Package Maintainer of 2000+ packages
  • Member of Fedora Packaging Committee
  • Provenpackager, Sponsor
  • Founder of Neuro and Rust SIGs
  • Member of Go, Python and Games SIG
  • One of few persons who is running fedscm-admin (to create dist-git repos and branches)
  • Contributor to hundreds of F(L)OSS projects (if even 1-line change counts), including RPM, DNF and libsolv in Fedora context
  • Participant of few Offline Test Days
  • Organizer of few Release Parties in Moscow

These are a set of mostly research packages that do not demand any changes from the main distribution. Any potential dependencies not currently available will be packaged and included.

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

There will be no problem to install this software on a system that has undergone a system upgrade.


N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Move this change to next release
  • Contingency deadline: Beta freeze
  • Blocks release? N/A (not a System Wide Change)
  • Blocks product? No

Documentation

N/A (not a System Wide Change)

Release Notes