From Fedora Project Wiki
(Change is now ready for wrangler)
(Add trackers)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- Self Contained or System Wide Change Proposal?
Use this guide to determine to which category your proposed change belongs to.
Self Contained Changes are:
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
* limited scope changes without the impact on other packages/rest of the distribution
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
System Wide Changes are:
* changes that does not fit Self Contained Changes category touching
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
* changing system defaults
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
-->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Comp Neuro Lab =
= Comp Neuro Lab =


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->


This Change will add a new Fedora Lab image to the Fedora repertoire for users working in Computational Neuroscience.
This Change will add a new Fedora Lab image to the Fedora repertoire for users working in Computational Neuroscience.


== Owner ==
== Owner ==
<!--
 
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:bt0dotninja| Alberto Rodriguez Sanchez]], [[User:Dan1mal| Danny Lee]], [[User:Ankursinha| Ankur Sinha "FranciscoD"]], [[SIGs/NeuroFedora| NeuroFedora SIG]]
* Name: [[User:bt0dotninja| Alberto Rodriguez Sanchez]], [[User:Dan1mal| Danny Lee]], [[User:Ankursinha| Ankur Sinha "FranciscoD"]], [[SIGs/NeuroFedora| NeuroFedora SIG]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: `sanjay DOT ankur AT gmail.com`, `neuro-sig AT lists.fedoraproject.org`
* Email: `sanjay DOT ankur AT gmail.com`, `neuro-sig AT lists.fedoraproject.org`
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* Responsible WG:
-->


== Current status ==
== Current status ==
Line 55: Line 21:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1758209 #1758209]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/398 #398]


== Detailed Description ==
== Detailed Description ==
Line 70: Line 36:
* the CNS*2019 conference: https://www.cnsorg.org/cns-2019-poster-presentation-guide
* the CNS*2019 conference: https://www.cnsorg.org/cns-2019-poster-presentation-guide
* The Open Source Brain workshop: http://www.opensourcebrain.org/docs/Help/Meetings#OSB_2019
* The Open Source Brain workshop: http://www.opensourcebrain.org/docs/Help/Meetings#OSB_2019
The kickstart files are here: https://pagure.io/neuro-sig/neuro-scripts/


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
    When a Change has multiple benefits, it's better to list them all.
    Consider these Change pages from previous editions as inspiration:
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


This change provides computational neuroscientists with a ready-to-use Fedora based image to use in their work.
This change provides computational neuroscientists with a ready-to-use Fedora based image to use in their work.
Line 128: Line 68:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Download the new installer Live image.
* Download the new installer Live image.
* Install it.
* Install it.
Line 188: Line 114:


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
-->


A mention of the new Lab image would be very useful.
A mention of the new Lab image would be very useful.


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF32]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->

Latest revision as of 14:47, 3 October 2019

Comp Neuro Lab

Summary

This Change will add a new Fedora Lab image to the Fedora repertoire for users working in Computational Neuroscience.

Owner

Current status

Detailed Description

The NeuroFedora SIG is working on leveraging the excellent resources provided by the Fedora community to enable and improve the use of FOSS in (neuro) science. This Lab image is aimed at computational neuroscientists---many of which use complex tools but hail from non-computing backgrounds. By providing this software to them in a pre-packaged, ready to install Lab image, we hope to enable their work.

NeuroFedora has been presented to the research community at various gatherings and has received positive feedback:

The kickstart files are here: https://pagure.io/neuro-sig/neuro-scripts/

Benefit to Fedora

This change provides computational neuroscientists with a ready-to-use Fedora based image to use in their work. By doing so, it aims to encourage more users to use FOSS, specifically Fedora, in their scientific work.

Scope

  • Proposal owners: A limited change---it introduces a new kickstart file for the generation of the Lab Image. It does not affect any other components of the Fedora community/life cycle. Additionally, we will have to communicate with the Websites team to create a new page for this change on https://labs.fedoraproject.org.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Not currently sure.
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

  • Download the new installer Live image.
  • Install it.
  • Use it, file bugs if some software does not work as expected.

User Experience

Users will see a new Live Lab image on https://labs.fedoraproject.org

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? N/A

The contingency would be to simply to push the image generation to the next release.

Documentation

The NeuroFedora SIG maintains user-documentation at https://neuro.fedoraproject.org We disseminate news and information about our work on the various mailing lists, and on the NeuroFedora blog at: https://neuroblog.fedoraproject.org. More information on our communication channels is here: https://docs.fedoraproject.org/en-US/neurofedora/communicating/

Release Notes

A mention of the new Lab image would be very useful.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Comp_Neuro_Lab&oldid=554173"