Differences between revisions 9 and 10
Revision 9 as of 2014-03-17 22:37:44
Size: 3063
Editor: ?RileyShaw
Comment:
Revision 10 as of 2014-03-19 18:57:22
Size: 3110
Editor: ?RileyShaw
Comment:
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
   * It will take as long as it needs to reach the deliverable goals. Start on March 19th, 20-3 UTC mon-fri, 13-2 UTC sat-sun, until June 19th, when I can be available at all times.    * It will take as long as it needs to reach the deliverable goals. Start on  May 19th, where I will only be available from 20-3 UTC mon thru fri, and 13-2 UTC on sat+sun, until June 19th, when I can be available at all times.

Riley Shaw

WIP

  • Contact/Email:rlyshw@gmail.com, IRC: rlyshw, http://rlyshw.dyndns.org, Github: https://github.com/rlyshw

  • Background: I'm a Senior in high school, majoring in computer engineering at a university this fall. I know Python, javascript, HTML/CSS, C++ (beginner), basic BASH scripting, and I'm a self-proclaimed Debian sysadmin (I host a local Debian server).


  • Project: Debian Continuous Integration(info from https://wiki.debian.org/SummerOfCode2014/Projects/DebianContinuousIntegration)

  • Project details:

    • Improve current ruby/bash scripts.(keeping project in ruby, unnecessary to rewrite)
    • WebUI improvements(in no particular order),
      1. Port to Sinatra/Rails app(Probably Sinatra, as it is more lightweight than rails).
      2. Process and directly display important bits of the log-file.
      3. Add filtering/improve search for browsing packages.
      4. Display blame list with hyperlinks to dependency data pages.
      5. Show reasons for package failure, other information that the package maintainers would need to make fixing things easier. Confer with the other student if possible.
    • Add multi-arch support(ARM, et al)
    • Improve scalability and expand support(make sure it is easy to add new backends).
    • Stay in contact with the Ubuntu CI system guys and package maintainers for tips/solutions
  • Synopsis: Expand upon the current Debian continuous integration system

  • Benefits to Debian: Decrease the amount of time it will take to release new versions of Debian

  • Deliverables: multi-arch support, improved web interface, add documentation, improve efficiency where possible


  • Project schedule:

Now-May 19th

investigation research, learning, greeting, bug fixes

May 19th-May 26th

Multi-arch support

May 26th - June 9th

Webui rewrite/improvements(log file information, stderr information)

June 23rd-27th

Mid-term Bug fixes, polish webui

June 30th-July 14th

Add multi-suite support

July 14th - July 28th

Further webui improvements, listen to maintainer feedback (improved search/filtering, blame lists)

July 28th - August 11th

Documentation, further backend improvements (efficiency, log/json additions), Scalability and deployability, finish TODO list

August 11th - 18th

Pencils Down Add polish, documentation, squash all bugs

Throughout

Documentation, code improvements

  • It will take as long as it needs to reach the deliverable goals. Start on May 19th, where I will only be available from 20-3 UTC mon thru fri, and 13-2 UTC on sat+sun, until June 19th, when I can be available at all times.
  • Exams and other commitments: School until June 19th

  • Other summer plans: None


  • Why Debian: I use Debian for hosting many of my remote services like VoIP server, HTTP, FTP, SSH, et al. Debian has worked very well for me, I would like to return the favor.

  • Are you applying for other projects in SoC? Yes