From Fedora Project Wiki
No edit summary
No edit summary
Line 37: Line 37:
* Name: [[User:ignatenkobrain | Igor Gnatenko]]
* Name: [[User:ignatenkobrain | Igor Gnatenko]]
* Email: <i.gnatenko.brain@gmail.com>
* Email: <i.gnatenko.brain@gmail.com>
* Release notes owner: [[User:ignatenkobrain | Igor Gnatenko]] <i.gnatenko.brain@gmail.com> <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>

Revision as of 17:56, 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

Benefit to Fedora

These packages bring potentially thousands of researchers and clinicians into Fedora 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.


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.


  • 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?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes