Service Grid Open Source Community Site
English | Japanese

Source Code Repository

The Subversion source code repository of this project is hosted on SourceForge. The latest version of source code is available at the following URL. Refer to the page of each software for the repository URL for the software.

  • http://svn.code.sf.net/p/servicegrid/code (View)

Only Core Members and Developers are allowed to commit source code to the repository. If you need the permission, please send us your SourceForge account and the reason you need the permission to oss-project [at] langrid.org (replace [at] with @).

For Subversion novice, instructions on SourceForge will help.

Component Types

In terms of code management, components of software in the source code repository of this project are classified as follows.Refer to page of each software for which components of the software belong to which categories.

Core Component

  • Core components provides core functions of each software. They are designed to be used from Optional Components described below.
  • Development of core components are controlled following project policies to maintain compatibility with optional components.
  • Only core members can commit source code of core components to the source code repository.
  • When you want to add or modify functions of core components, post your request on the multilingual BBS first. You can post a patch on the BBS, but it is required to be reviewed by core members before it is merged with the existing source code.

Optional Component

  • Optional components are developed independently with Service Grid Open Source Project, but by using core components.
  • Members of this project can post their request on the multilingual BBS on the community site, but it is left to the developers whether or how the developer deals with.
  • Optional components are classified into the following two categories.
    • Authorized Component: Core members check the quality and watch development status.
    • Unauthorized Component: Core members are not involved in managing the quality and development status.
  • The developer of optional components or their derived software can commit the source code to the source code repository after he/she joins the project as a developer.

Development Process

We show the general development processes below. Though all the source code is published under the open source license, you are encouraged to follow the guideline to make your contribution useful for more people and to improve the quality based on feedback. The guidelines are defined for core/optional components.

Development of Optional Components

Development of an optional component consists of the following steps.

  1. Setting up an environment

    Check out source codes from the source code repository first. You need a Subversion client. For Subversion novice, instructions on SourceForge will help. The repository URL is shown on the page of each software.

    Next setup an environment for the software on your local machine. Install instructions are available on "Download" page.

  2. Development

    Develop a component and check if it works on your local machine. Please refer to page of each software about granularity of the components you develop.

    The name of the developed component should be different with existing ones. This makes it possible for other developers to install your component into the existing environment. Moreover, you can avoid the conflict in the source code repository.

  3. Committing source code and announcement

    Commit your source code to the source code repository after you check that your component works properly. develop the first version of your component. Only developer can commit source code to the repository. If you don't have the permission, please send us your SourceForge account and the reason you need the permission to oss-project [at] langrid.org (replace [at] with @).

    For each software, the location you can commit your optional component to is defined for each software.

    Then announce that your code is committed at "Announcement" forum on BBS. Include the location in which you commit your code and instructions to use it.

  4. Feedback

    Discuss feedback and revision to be applied at "Request/Proposal" forum on the multilingual BBS. You shoud also check "Bug Report" forum. We recommend you enable notification of new posts.

Development of Core Components

Development of an optional component consists of the following steps.

  1. Setting up an environment

    Check out source codes from the source code repository first. You need a Subversion client. For Subversion novice, instructions on SourceForge will help. The repository URL is shown on the page of each software.

    Next setup an environment for the software on your local machine. Install instructions are available on "Download" page.

  2. Designing specification

    We strongly recommend that you discuss specification before you start start development of core components at Request/Proposal forum on the multilingual BBS.

    You are not allowed to commit your modification of core components without agreement by community members. This is because the modifications may prevent other modules from working properly.

  3. Development

    Develop a component and check if it works on your local machine. Please refer to page of each software about granularity of the components you develop.

    Carefully check if other modules work properly after you modify the core components. You may not commit your code which causes problems with other modules.

  4. Committing source code and announcement

    Commit your source code to the source code repository after you check that your component works properly. develop the first version of your component. Only developer can commit source code to the repository. If you don't have the permission, please send us your SourceForge account and the reason you need the permission to oss-project [at] langrid.org (replace [at] with @).

    Multiple versions of a core component do not work in the same environment. Please create a new branch and commit your code toto it.

    Please post an announcement at "Announcement" forum when you create a new branch.

  5. Feedback

    Discuss feedback and revision to be applied at "Request/Proposal" forum on the multilingual BBS. You shoud also check "Bug Report" forum. We recommend you enable notification of new posts.

After community members check that the component is stable enough, the branch is merged into trunk and a release package.

Fixing Existing Components

If you make a small modification or fix bugs, please post a message with the patch on the multilingual BBS. The developer of the component will merge the patch after they check it. Core members can substitute if allowed by the developer.

For modification, however, we recommend you should propose at "Request/Proposal" forum first and agree with the developer or core members before you start development. Your modification would not be merged if the developer rejected.

For bug fix, please post a message with the patch you developed at "Bug Report" forum at the multilingual BBS. But the developer or core members may not accept the patch for some reason.

Last update: 10-Mar-2011