From Fedora Project Wiki
(→‎Benefit to Fedora: Fixing typos)
No edit summary
Line 74: Line 74:


== Scope ==
== Scope ==
* Proposal owners: Kushal Das
* Proposal owners: To implement this change
<!-- 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?-->


Line 151: Line 151:
-->
-->


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAnnounced]]
<!-- 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 -->

Revision as of 16:32, 15 January 2016


Micro Bit

Summary

Enable the use of BBC Micro Bit on Fedora systems. Users will be able develop, and put in new code to their micro:bit devices using Fedora.

Owner

  • Name: Kushal Das
  • Email: mail@kushaldas.in
  • Release notes owner:

Current status

  • Targeted release: Fedora 24
  • Last updated: 2016-01-15
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Micro Bit (or micro:bit) is an ARM-based embedded system designed by the BBC for use in computer education in the UK. It will be given to every class 7 students in UK. This change will make sure that they simply use Fedora to use their devices.


Benefit to Fedora

Enabling the devlopment of Micro Bit programs will enable regular Fedora users to use their normal system for this. This change will also bring in more young developers to Fedora ecosystem as we will be the first distribution to fully support the development for the board.


Scope

  • Proposal owners: To implement this change
  • 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

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