Difference between revisions of "Automate Pidora Kernel"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= Automate Pidora Kernel and Firmware Building = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == The Raspberry …')
 
Line 9: Line 9:
 
== Project Leader ==
 
== Project Leader ==
  
Ronald Hernandez
+
[[User:Ronald Hernandez | Ronald Hernandez]]
 +
 
 
<!-- Name(s) of primary person working on the project.
 
<!-- Name(s) of primary person working on the project.
  
Line 32: Line 33:
 
=== Tracking ===
 
=== Tracking ===
  
Progress can be tracked in my blog
+
Progress can be tracked in my [http://http://rsbr600.blogspot.ca/ Blog]
 
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
 
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
  
 
=== Key contacts ===
 
=== Key contacts ===
  
Chris Tyler  
+
Chris Tyler,
 
Andrew Green (soon)
 
Andrew Green (soon)
 
<!-- Add links to any mentors or key participants in the community. -->
 
<!-- Add links to any mentors or key participants in the community. -->

Revision as of 23:57, 9 October 2013

Automate Pidora Kernel and Firmware Building

Project Description

The Raspberry Pi Foundation maintains a kernel fork that is updated frequently. We would like to package kernel and firmware changes on a daily basis, and have these available in a testing repository so that anyone can use them. Periodically, we will select a kernel-firmware combination from this testing repository and make it available as the main Pidora kernel.

Project Leader

Ronald Hernandez


Project Contributor(s)

Project Details

Use Python or Bash to create a script that will be automate the process of compiling the newest kernel. This will be done by checking Github for the latest kernel, downloading it, updating the spec file and sending the build to koji. This build will stay in a testing repository.

Project Plan

Tracking

Progress can be tracked in my Blog

Key contacts

Chris Tyler, Andrew Green (soon)

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1 Prototype build in either python or bash able to retrieve package from github and send it to koji
  • 0.2 Finish code, add options if I find they could be helpful in some way. Comment code and do lots of testing.
  • 0.3 Create man page, perform tweaks and send for release.

Communication

Email: rhernandez2@myseneca.ca IRC: rhernandez2

Mailing Lists

fedora fedora-devel fedora-arm


Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News