JacobPeddicord

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2010-03-21 21:07:14 →
Size: 2610
Editor: 208
Comment:
← Revision 4 as of 2010-03-21 21:18:41 → ⇥
Size: 3378
Editor: 208
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * Your Name: Jacob Peddicord  * Your Name: [[JacobPeddicord|Jacob Peddicord]]
Line 26: Line 26:
     Upstart has replaced nearly all of the old boot scripts from /etc/init.d with newer, more concise jobs in /etc/init. The syntax of these files is easy to read, but powerful. That's the same idea in mind here: there should be an easy to use but powerful tool around to manage both Upstart jobs and older SysV scripts. It seems like something that would complement Upstart nicely.
     
     In addition, I'm a server administrator myself and have messed around with Upstart & boot scripts. I'd love to be able to bring this functionality to the desktop in the form of a nice interface.
Line 27: Line 30:
     There are a few main components that make up this idea:
       * Backends
       * Management
       * Configuration
       * Package integration

Jacob Peddicord

Contact information

Project

  • Project Name: Upstart compatible services-admin

  • Project Description:
    • The previous service administration tool was able to list available services and enable/disable them. I plan to create a new services tool from scratch with a few goals in mind:
      • Ease of use - it should display the necessities needed to manage services, while not getting too technical
        • (though some technical knowledge is assumed if a user is messing around with services)

      • Properly secured using PolicyKit

      • Compatibility with Upstart and old-style SysV scripts
      • Configurable - should be able to change properties of services and reload them
      • Package and Launchpad integration - provide methods to uninstall the services' package and to report a bug on it
  • If you would be willing and able to do other projects instead, which ones?
    • Clipboard improvements would be another idea that interests me, having been a victim of the "copy, close, paste, realize nothing happened" model.
  • Why did you like this idea?
    • Upstart has replaced nearly all of the old boot scripts from /etc/init.d with newer, more concise jobs in /etc/init. The syntax of these files is easy to read, but powerful. That's the same idea in mind here: there should be an easy to use but powerful tool around to manage both Upstart jobs and older SysV scripts. It seems like something that would complement Upstart nicely.

      In addition, I'm a server administrator myself and have messed around with Upstart & boot scripts. I'd love to be able to bring this functionality to the desktop in the form of a nice interface.

  • Please describe a tentative project architecture or an approach to it:
    • There are a few main components that make up this idea:
      • Backends
      • Management
      • Configuration
      • Package integration
  • Give us details about the milestones for this project
  • Why will your proposal benefit Ubuntu?

Open Source

  • Please describe any previous Open Source development experience
  • Why are you interested in Open Source?

Availability

  • How long will the project take? When can you begin?
  • How much time do you expect to dedicate to this project? (weekly)
  • Where will you based during the summer?
  • Do you have any commitments for the summer? (holidays/work/summer courses)
  • Please designate a back up student (in case you need to withdraw your application)

Other

  • Have you ever participated in a previous GSoC? (describe your project)
  • Have you applied for any other 2010 Summer of Code projects? If yes, which ones?
  • Why did you apply for the Google Summer of Code ?
  • Why did you choose Ubuntu as a mentoring organisation?
  • Why do you want to participate and why should Ubuntu choose you?

GSoC/2010/JacobPeddicord (last edited 2010-03-26 01:57:50 by 208)