Accessing the Code Repository
In-Portal uses Subversion (SVN). It can be accessed through svn://source.in-portal.org OR you can browse the repository with your browser: http://source.in-portal.org
For those who need a kick-start on SVN, please take a look at this guide: http://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html
NOTE: In-Portal uses SVN 1.6 version which means that your SVN client must support/have SVN 1.6.x connector in order to properly communicate with the repository.
Repository Structure
Before you can work with In-Portal’s Code Repository, you'll need to understand its structure. When accessing it you see a tree similar to the one below:
[svn]
- in-portal (In-Portal CMS)
- branches (latest development branches, not releases)
- 5.0.x
- 5.1.x
- releases (official releases)
- 5.0.0
- 5.0.1
- 5.0.2-B1 (Beta 1)
- trunk (not used, so we won't be listing it)
- modules (Modules of In-Portal, Open Source)
- custom (Development Kit)
- branches (latest development branches, not releases)
- 1.0.x
- 1.1.x
- releases (official releases)
- 1.0.0
- 1.0.1
- 1.0.2-B1 (Beta 1)
- in-bulletin (Form Management module)
- branches (latest development branches, not releases)
- 5.0.x
- 5.1.x
- releases (official releases)
- 5.0.0
- 5.0.1
- 5.0.2-B1 (Beta 1)
- in-link (Directory Management module)
- branches (latest development branches, not releases)
- 5.0.x
- 5.1.x
- releases (official releases)
- 5.0.0
- 5.0.1
- 5.0.2-B1 (Beta 1)
- in-news (News Management module)
- branches (latest development branches, not releases)
- 5.0.x
- 5.1.x
- releases (official releases)
- 5.0.0
- 5.0.1
- 5.0.2-B1 (Beta 1)
- profiles
- in-portal.community (externals to the real modules so you can checkout all Open Source modules at the same time)
- in-portal.directory (externals to In-Portal CMS and In-Link module, plus Directory theme located in themes/directory)
- new profiles coming soon...
- themes (Themes of In-Portal and Modules)
- advanced (Advanced theme that contains templates for all In-Portal modules)
- branches (latest development branches, not releases)
- 1.0.x
- 1.1.x
- releases (official releases)
- 1.0.0-B1 (Beta 1)
- 1.0.0
- default (Default theme that is shipped with In-Portal distribution)
- branches (latest development branches, not releases)
- 5.0.x
- 5.1.x
- releases (official releases)
- 5.0.0-B1 (Beta 1)
- 5.0.0
- directory (Directory theme for In-Link module)
- branches (latest development branches, not releases)
- 1.0.x
- 1.1.x
- releases (official releases)
- 1.0.0-B1 (Beta 1)
- 1.0.0
- onlinestore (Onlinestore theme for In-Commerce module)
- branches (latest development branches, not releases)
- 1.0.x
- 1.1.x
- releases (official releases)
- 1.0.0-B1 (Beta 1)
- 1.0.0
- simple (Simple theme for In-Portal CMS)
- branches (latest development branches, not releases)
- 1.0.x
- 1.1.x
- releases (official releases)
- 1.0.0-B1 (Beta 1)
- 1.0.0
Getting the Source Code
All Community Members are welcome to download the code from the In-Portal Code Repository. Please use the following credentials for Checkout, Export and Update operations:
Username: guest
Password: [blank]
Checkout In-Portal CMS 5.0.1 release
svn checkout --username guest svn://source.in-portal.org/in-portal/releases/5.0.1
Checkout In-Portal CMS 5.0.1 release + all modules
svn checkout --username guest svn://source.in-portal.org/profiles/in-portal.community/releases/5.0.1
Checkout In-Portal CMS 5.0.x latest development
svn checkout --username guest svn://source.in-portal.org/in-portal/branches/5.0.x
Checkout In-Portal CMS 5.0.x latest development + all modules
svn checkout --username guest svn://source.in-portal.org/profiles/in-portal.community/branches/5.0.x
More information on other SVN commands like Export, Update and Commit can be found here http://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html
Browsing the Code Repository
In some cases it may be convenient to browse the source code through your browser. This can be done by pointing your browser to http://source.in-portal.org
Additional features include the ability to Compare files, see Annotations (who edited what), Diff and many others.
Committing Your Code
In order to maintain In-Portal’s code integrity, committing into the Repository is only performed by members trusted by the Community with special commit privileges. Commit privileges are by invitation only and are earned through participation and assigned by leading members of the Development and Bug Teams.
We are using a well known PATCH => TEST => COMMIT approach for all development work without exceptions. This is done to avoid issues when untested or conflicting code gets committed into the repository.
The easiest way to get your work (bug fix or feature) committed into the repository is to attach a Patch (Diff) file with your code changes in the Issue Tracker so it can be tested by Community members and then committed by users with commit privileges.
