From Fedora Project Wiki
< Changes
(→Scope) |
Ankursinha (talk | contribs) (Change is now ready for wrangler) |
||
| Line 10: | Line 10: | ||
System Wide Changes are: | System Wide Changes are: | ||
* changes that does not fit Self Contained Changes category touching | * 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.) | * changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) | ||
* changing system defaults | * 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). | 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. | We request that you maintain the same order of sections so that all of the change proposal pages are uniform. | ||
| Line 24: | Line 24: | ||
== 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. | <!-- 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?". --> | 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 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. | 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. | 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]] | ||
| Line 46: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/32 | Fedora 32 ]] | * Targeted release: [[Releases/32 | Fedora 32 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
ASSIGNED -> accepted by FESCo with on going development | ASSIGNED -> accepted by FESCo with on going development | ||
| Line 74: | Line 74: | ||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- 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: | Be sure to include the following areas if relevant: | ||
If this is a major capability update, what has changed? | If this is a major capability update, what has changed? | ||
| Line 89: | Line 89: | ||
For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly. | 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? | 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. | 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. | When a Change has multiple benefits, it's better to list them all. | ||
| Line 112: | Line 112: | ||
* Release engineering: Not currently sure. | * Release engineering: Not currently sure. | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 125: | Line 125: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
N/A (not a System Wide Change) | N/A (not a System Wide Change) | ||
== 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. | <!-- 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. | 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. | ||
| Line 143: | Line 143: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Download the new installer Live image. | |||
* Install it. | |||
* Use it, file bugs if some software does not work as expected. | |||
== User Experience == | == User Experience == | ||
| Line 157: | Line 159: | ||
--> | --> | ||
Users will see a new Lab on https://labs.fedoraproject.org | Users will see a new Live Lab image on https://labs.fedoraproject.org | ||
== Dependencies == | == Dependencies == | ||
| Line 163: | Line 165: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
N/A (not a System Wide Change) | N/A (not a System Wide Change) | ||
== Contingency Plan == | == Contingency Plan == | ||
| Line 182: | Line 184: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
The NeuroFedora SIG maintains user-documentation at https://neuro.fedoraproject.org | 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 == | == 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 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. | <!-- 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. | 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: | [[Category:ChangeReadyForWrangler]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- 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) --> | <!-- 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--> | <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--> | ||
Revision as of 09:15, 17 September 2019
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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Comp Neuro Lab
Summary
This Change will add a new Fedora Lab image to the Fedora repertoire for users working in Computational Neuroscience.
Owner
- Name: Alberto Rodriguez Sanchez, Danny Lee, Ankur Sinha "FranciscoD", NeuroFedora SIG
- Email:
sanjay DOT ankur AT gmail.com,neuro-sig AT lists.fedoraproject.org
Current status
- Targeted release: Fedora 32
- Last updated: 2019-09-17
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
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 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
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)
- Trademark approval: Approved by the Council
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.