From Fedora Project Wiki

Contact Information

NOTE: We require all students to blog about the progress of their project time to time.

You are strongly encouraged to register on the Freenode network and participate in our IRC channels. For more information and other instructions, see:

https://fedoraproject.org/wiki/GSOC_2012

Please answer following questions.

Why do you want to work with the Fedora Project?

Because I like the idea of working with the open source community. Built by everyone for everyone. I also feel that I could develop my skills as a computer engineer while helping the Fedora distribution move forward.

Do you have any past involvement with the Fedora project or with any another open source project as a contributor (if possible please add some references as well)?

Just started getting involved packaging for the JBoss project for Fedora. The process always seemed a bit daunting but I am hoping to get introduced to the culture and the community. In doing so I would increase my own knowledge while putting it to use for the Fedora community. I have started to get involved with the JBoss packaging effort and my most recent package was jboss-web.

Did you participate with the past GSoC programs, if so which years, which organizations?

No.

Will you continue contributing/ supporting the Fedora project after the GSoC 2012 program, if yes, which team(s)/area(s), you are interested with?

Yes, packaging for the near future. As I finish up my degree work, I will be adding skills to allow me to further help the project in other areas. Hopefully next semester I will be taking an operating systems course geared towards operating system development and a course on embedded development.

Why should we choose you over the other applicants?

Motivated, self-starter, with an insatiable desire to learn, help, and please others.

Proposal Description

  • Please describe your proposal in detail. Include:

An overview of your proposal

  • To help package JBOSS AS7 and similar components to help create a Fedora JBOSS spin.
  • To get Shrinkwrap packaged and able to successfully build, install, and run for the next release.
  • To get Arquillian packaged and able to successfully build, install, and run for the next release.
  • To pick up any other packaging tasks that are required to complete the packaging for the Fedora JBOSS spin project.

The need you believe it fulfills

  • JBOSS provides Java Enterprise developers with an option of a compact distribution via a Fedora JBOSS spin.
  • Shrinkwrap provides a simple mechanism to assemble archives like JARs, WARs, and EARs with a friendly, fluent API, for Java Enterprise developers.
  • Arquillian is a powerful testing platform that handles the plumbing of of managing the container lifecycle, deployment and framework initialization so you can focus on writing your integration tests.
  • These features would entice Java Enterprise developers to chose Fedora as their primary operating system.

Any relevant experience you have

  • Junior in the Computer Engineering program at University of Maryland Baltimore County. I have experience in developing, compiling, and submitting projects on a Linux distribution. I know C, C++, Python, Java, ant, cvs, and bash and I have used Fedora for years.

How do you intend to implement your proposal

  • Start by becoming a proven packager.
  • Do some research on using Maven.
  • Start packaging the dependencies required by Shrinkwrap.
  • Separate the Shrinkwrap source into separate build-able modules.
  • Try to build against rawhide.
  • And, test, test, test.
  • Then start seperating Arquillian into seperate build-able modules.
  • Try to build Arquillian componenets against rawhide.
  • Then test, test, test.
  • Repeat as necessary.

Final deliverable of the proposal at the end of the period

  • Shrinkwrap and Arquillian completely packaged and ready for the Fedora JBOSS spin.

A rough timeline for your progress

Any other details you feel we should consider

  • I have a lot of time to spend over the summer on this project.

Have you communicated with a potential mentor? If so, who?

  • Yes, Marek Goldmann.