Navigation
Work procedures
Most EEA software projects use SVN to store the source code, Taskman for ticket, and a conference room called Riot to coordinate work.
EEA source code repositories
Subversion repos
| Airquality | SVN Repository | Project wiki and tickets |
|---|---|---|
| Eye on Earth dedicated repo | SVN Repository | Project wiki and tickets |
| DotNet Microsoft .NET applications | SVN Repository | Project wiki and tickets |
| EEA internal infrastructure | SVN Repository | Project wiki and tickets |
| EUNIS 2 | SVN Repository | Project wiki and tickets |
| GisLibrary (GIS, Map components) | SVN Repository | Project wiki and tickets |
| Naaya products | SVN Repository | Project wiki and tickets |
| Natura2000 | SVN Repository | Project wiki and tickets |
| Reportnet | SVN Repository | Project wiki and tickets |
| tableau-mobile | SVN Repository | Project wiki and tickets |
| WISE - Water Information System for Europe | SVN Repository | Project wiki and tickets |
| Zope products | SVN Repository | Project wiki and tickets |
Github repos
| EEA packages on github | Github organisation repository | Documentation homepage |
|---|
How to use GIT
All packages can be checked out (pull) from GIT anonymously over plain HTTP. But if you plan to update code (push), then you must have a GIT account (register on github.com if you don't have one), than you branch the EEA package and do a pull request against the EEA master repo. If you are a consultant or EEA Staff working for an EEA project you may apply for membership of the EEA organisation github account, than you automatically get push access to our packages. Contact demarant or sorenroug on http://github.com/eea.
New to git? It is easy to learn if you know svn already.
How to use SVN
Most packages can be checked out from SVN anonymously over plain HTTP. But if you plan to update code, then you must use the SSL-encrypted interface (HTTPS) and log in with your Eionet account name. Try svn co https://svn.eionet.europa.eu/repositories/Zope/trunk/RDFCalendar.
We have a quick tutorial on the Windows Explorer plugin TortoiseSVN. For Macintosh you can use SvnX, but command-line tools seem more popular.
An other Subversion aware IDE is Eclipse. It has the caveat that you might have to install the Globalsign root certificate into Internet Explorer before it will trust the repository.
The O'Reilly book Version control with Subversion is available online.
Subversion can automatically convert end-of-line standards and set the mime-type if you use auto-properties. This config file for Linux provides reasonable defaults. You install it in ~/.subversion/config
Editor settings
For all source code (and XML) use UTF-8 character encoding. For Python, you should declare the encoding as recommended by PEP-0263.
For Python code the indentation is 4 spaces. No tabs are allowed in the code, so set your editor to expand tabs to spaces.