How to use your github.com repository on the eZ Publish extension forge : projects.ez.no

Step 3 : create a project space on projects.ez.no

(if you already have one, skip to Step 3).

The first step is to have a valid account on projects.ez.no. This is the same as your share.ez.no account. In other words, if you don't have one, visit share.ez.no and hit the “Register” link at the top-right corner of the page. The received credentials will let you sign-in to projects.ez.no too.

Creating a project space on the eZ Publish extensions forge empowers your project with the following :

A Forum,

A News section, for announcements, also made available on the platform's home page and through a global RSS feed, both well-indexed by search engines,

RSS feeds,

Reviews and Rating : always good to get some stars by other Community members,

An Image gallery (“an image is worth thousand words”),

A Downloads section where you can propose packaged releases of your extension,

A Subversion repository, which we will not use in our case,

A Team management tool,

This all helps you get attention from the eZ Publish Community and generate more collaboration around your extension, the very open-source way. I highly encourage you to create a project space on projects.ez.no on top of having a github.com repository.

Navigate then to projects.ez.no, sign-in, and hit the “Create a new project” button, as shown here :

Step 4 : enter the URL to your github.com repository

If you are creating your project, you will need to fill-out all required fields, and once submitted, the project will have to be approved by the site moderators (takes a few hours usually).

When editing the project home page, scroll one and you will reach the field entitled :

From now on, all commits on the master branch of your github repository will be reflected in your project space on projects.ez.no, pushed through the RSS feeds. People who have subscribed to your project's notification will be notified as when the Subversion repository was used. But let's have a look at it in step 5.