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 package the Gradle build system for Fedora so that Hibernate and other like projects can be built on Fedora and be included with JBoss.
  • To package and include everything to produce a JBossAS7 full-profile Fedora spin release.

The need you believe it fulfills

  • Packaging the Gradle build system would allow packagers to build packages for Fedora that were written with gradle scripts.
  • Gradle is important if the goal is to have a full-profile installation of JBossAS7.
  • Provide a full-profile JBossAS7 Fedora spin to provide Java Enterprise developers an option of a compact distribution with all or most of their application needs met.

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. Have packaged and submitted a few packages towards the JBoss project.

How do you intend to implement your proposal

  • Investigate and research the different methods and possibilities to create the Gradle package so that it can properly install and work correctly.
  • Possibly collaborate with Gil Cattaneo who has worked towards packaging Gradle for the Mageia distribution and recently for the Fedora Project.
  • Once Gradle is correctly packaged, start including tools like Hibernate for the Fedora JBoss spin.
  • Make sure everything follows the requirements for creating the Fedora JBoss spin.
  • Create the full-profile Fedora JBoss spin.

Final deliverable of the proposal at the end of the period

  • The Gradle build system packaged and working on Fedora.
  • Complete packaging the sources that use Gradle build system and packages that are needed to provide a full-profile installation of JBossAS7.
  • Create a JBoss Fedora spin that will include everything a Java Enterprise developer would need to; build, test, and deploy their applications.

A rough timeline for your progress

  • Present-Start of GSOC
    • Do some research on Gradle and Maven build systems and also on creating spins. Make a list of packages that use gradle that would nice to have on the JBoss spin. Keep up contact with mentors. Keep contributing to the JBoss project.
  • Weeks 1-6
    • Start gathering the dependencies required for building Gradle.
    • Build Gradle and its dependencies.
    • Do the same for Hibernate, Shrinkwrap, Arquillian, etc.
  • Midterm Evaluation
    • Submit work to date: Gradle, Hibernate, Shrinkwap, Arquillian, etc.
  • Weeks 7-12
    • Gather all of the packages to create the Fedora JBoss spin.
    • Write the scripts and kickstart files needed.
    • Test remove bugs from the spin.
  • Final Evaluation
    • Submit a complete and tested full-profile JBoss Development Spin.

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.