Trac, together with svn is the code repository and bug tracking system we use for almost all of our projects. It is a secure online code storage system, coupled with some usefull project tracking tools allowing multiple developers and designers work together on one project and managing the progress.

Subversion (svn) is a central organized code repository. This means that multiple people can concurrently work on the same code, independent of each other, while supplying tools to see and track conflicts and merge the code back into a central online storage. It also allows you to go back in time and revert certain changes, might the current changes break previous achieved goals. Giving all team member a clear oversight of all the code that has been committed, together with comments on a timeline, does not only provide insight into and track the progress of a project, it also strengthens the teams collaboration and commitment on the project.

Trac is a web portal on top of this code repository, yielding even more tools for collaboration, documentation and managing the progress of a project. The parts of which Trac consist are a wiki, the timeline, the code repository, an issue trackers and an agenda, as organized in milestones.

The wiki is the documentation part of the system. Using a wiki markup (simpler than HTML) the user can directly edit the page they are looking at, create new pages and make links between different pages. Thus a web of cross-referencing pages is easily made.

The issue tracker in Trac is a ticket system, which gives different users —with varying levels of privileges and responsibilities— the opportunity to submit tickets: issues, bugs or feature requests. Each ticket can then be rated to its priority, organized as belonging to a particular milestone, version or component and assigned to somebody specific. This makes for a system in which these tickets and priorities can be managed adequately and the overall progress can be followed throughout the team.

The Trac system we have running on our servers, can have private closed projects, to which access is secured through passwords, and open projects which are public and visible to everybody.

List of public projects on our Trac: *

Warning of insecurely signed certificate

Though we do safely secure our servers and the Trac projects we have running on them, we don’t believe buying a secure certificate for each (sub)domain is beneficial to us or to our clients. That is why you will see a warning when you visit one of our Trac sites. Read on why and how to disable the warning in the future.

To secure a website and be able to have its traffic follow the safe https:// (s for secure) protocol, a website must have a valid signed sercurity certificate. This certificate ensures the visiting browser that it is indeed talking to the server on the domain it says it is. However, purchasing a certificate signed by an official internet security authority does not come cheap. Moreover, for each subdomain that needs to be secured with https:// a separate certificate must be issued. That is why we chose not to use an official signing authority, but use our own:

Hence you will see a warning when you first visit one of our secured domains, telling you the identity of the signing authority cannot be confirmed. This is not a problem, because we’re confirming it here for you: every certificate signed by our own is valid and safe.

If you don’t want to see these messages the next time you visit this same domain, all you have to do is to have this (unsigned) certicate be remembered in your Keychain (if your on a Mac or iOS device). This makes sure the next time you visit this secured (sub)domain, it’s identity is confirmed by your computer, instead of one of these expensive signing authorities.

Just follow these steps if you are using Safari, Firefox or Chrome. You must have access to your Keychain to be able to complete these steps.