Differences between revisions 5 and 6
Revision 5 as of 2014-03-04 17:40:02
Size: 4739
Editor: JosephBisch
Comment:
Revision 6 as of 2014-03-05 17:39:56
Size: 5002
Editor: JosephBisch
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * '''Background:''' Currently a junior in college studying Electrical Engineering at University of New Haven in West Haven, CT, US. My main distro is currently CrunchBang.  * '''Background:''' Currently a junior in college studying Electrical Engineering at University of New Haven in West Haven, CT, US. My main distro is currently CrunchBang. I prefer to use VIM and Git. Some of my other interests are stamp collecting and Atari 8-bit computers.
Line 8: Line 8:
 * '''Deliverables:'''  * '''Deliverables (copied):'''
Line 26: Line 26:
 * '''My questions/comments:'''
   * I see that the metrics portal was a proposal for GSoC 2013 also. Was it not finished, or was it never started?
  • Name: Joseph Bisch

  • Contact/Email: joseph.bisch@gmail.com irc jbisch

  • Timezone: UTC-05:00

  • Background: Currently a junior in college studying Electrical Engineering at University of New Haven in West Haven, CT, US. My main distro is currently ?CrunchBang. I prefer to use VIM and Git. Some of my other interests are stamp collecting and Atari 8-bit computers.

  • Project title: Debian metrics portal

  • Project details: Create a Debian Metrics Portal to view, add, and maintain metrics in a uniform way.

  • Benefits to Debian: Make it easier to improve Debian by providing a single source of metrics to evaluate changes.

  • Deliverables (copied):

    • database structure to store all historical data points of all metrics
    • standardized declarative interface to add/remove metrics to be graphed. The interface should allow for both "local" metrics (e.g. data generated by scripts run on the machines hosting the metrics portal) and "remote" metrics (e.g. data generated by remote data sources which are then periodically gathered by the metrics portal)
    • cron jobs to periodically fetch new data and generate graphs
    • proof of concept: integration of (some of the) existing graphs in the metrics infrastructure
    • web interface to show updated graphs of the various metrics
    • client-side dynamic web interface to graph, on demand, specific metrics (possibly more than one at a time to look for correlations) over the desired time periods
    • (optional) produce a Debian Package of the portal code to ease deployment on Debian-based machines
  • Project schedule: I created a Gantt chart to illustrate my anticipated breakdown of the allotted time. I scheduled two days off, the Fourth of July and my birthday. I left one week at the end of Coding Period 1 to allow time to finish any unfinished tasks. I can use the week I allotted for producing the Debian package at the end of Coding Period 2 if I have any unfinished tasks at that point. I don't anticipate needing it and plan on finishing all tasks, including the optional packaging task. You can view the Gantt chart at http://josephbisch.com/debian-metrics-portal.html. The only other commitment, besides the two days off, is one summer class. It will be taken either the first or second half of summer and will require no more than 4 hours per week of my time. Those 4 hours include lectures and studying/homework. I don't believe the class will significantly affect my ability to complete this project. I can still dedicate at least 40 hours per week towards this project.

  • Why am I right for this project:

    • I am experienced with Python. For example, while working for my campus' tutoring center, I wrote a program that parsed the bookstore's website and generated a CSV file of all the books. I wrote it using urllib2 to get the webpages and ?BeautifulSoup to scrape the pages. I saved the center time by automating a task that had been done manually in past years.

    • I am willing to ask questions and learn. Prior to creating this application I never used ?TaskJuggler, but I learned it to create the Gantt chart. I already emailed the mentors to ask a question about the sources.history script. However, I will reserve asking questions for when sources such as the Debian Wiki and Google do not suffice.

    • I have experience working as a team. I am on my school's robotics team, and was also on my high school's robotics team. I frequently have to work as a team as part of my engineering education.
    • I have experience with ?JavaScript. I work(ed) on the websites for both robotics teams. I have also done some freelance web design/development. I know how to integrate libraries and how to do basic manipulation of elements (e.g., show/hide element with animation on mouse click of another element; change properties of an element such as color, innerhtml, etc.). If I discover that I need more advanced ?JavaScript for this project, I can learn as I go along.

  • What have I done so far: I wrote a script to create graphs from metrics on the UDD sources history table. I have read the Debian Wiki. I created a Gantt chart that estimates the breakdown of the GSoC timeline.

  • Potential challenges:

    • I don't have prior experience contributing to Debian. I am already familiarizing myself with Debian wiki, irc, mailing lists, etc. to minimize the impact of this.
    • I don't have prior experience with SQLAlchemy, the templating engine, or the ?JavaScript library. I have scheduled plenty of time to familiarize myself with those.

  • My questions/comments:

    • I see that the metrics portal was a proposal for GSoC 2013 also. Was it not finished, or was it never started?
  • Why Debian?: I run ?CrunchBang, which is heavily based off of Debian. So my work will have a large impact on the distro I run day-to-day and on many other people.

  • Am I applying for other projects?: No