Posts in category news

CodeResort.com service is now closed

CodeResort.com will no longer provide project and repository hosting.

All external projects & all external users are now deleted.

Scheduled downtime @ Monday 2017-10-02 14:00-22:00 CET

We are moving offices and infrastructure on Oct 2nd, so the service will be unavailable in the afternoon and evening.

Sorry for the inconvenience!

New SSL certificate

We have updated the SSL certificate and intermediate CAs again today.


  • SHA256: 39:B8:E5:9B:F1:39:92:33:99:EF:32:5A:9C:8E:14:58:42:63:83:F2:A2:2E:36:FE:33:E7:91:16:21:A8:F6:81
  • SHA1: B0:53:47:AB:EE:9F:A0:67:F8:9C:4A:CF:81:72:A2:A2:46:47:1F:32

New SSL certificate

The *.coderesort.com SSL certificate has been renewed.


  • SHA1: 1D:4A:4D:BD:07:E6:B0:7B:90:40:FA:1C:FE:D1:A1:12:9B:31:3E:08
  • MD5: DB:82:8A:4D:3D:FC:8A:CF:D0:65:E9:AD:A3:88:25:1D

Maintenance - OS Upgrades

We are scheduling OS upgrades and maintenance across our infrastructure this weekend.

Services will be unavailable from 23:30 CET Friday night, but we expect most things completed in 2-3 hours. However, we are keeping the maintenance window open across the weekend in case follow-up issues require reboots or service restarts.

Follow @CodeResort on Twitter for further status updates.

Update: Upgrades completed in 6 hours. All services fully operational again.

Introducing Git

We are moving with the times, and are now introducing Git as a supplement to our Subversion support. This post is not about the relative merits of each system, only to provide an overview of the new features we have added for Git.

  1. Git is optional. Each project still gets one Subversion project like before, but can now add additional Git repositories.
  1. Git repositories are not yet browsable via the web interface. The source, changesets and timeline of events are not yet enabled due to (lack of) performance. We don't quote get the performance we require with so many projects and repositories, and no size or content restrictions. However, we have made a small 'Browse Source' helper that lists Git repositories for each project with URLs to use with Git clients. We will enable the full source browsing functionality as soon as it is ready.
  1. Git clients can connect both through SSH and HTTPS. HTTPS being the most common and easy to get started with, but SSH adding both additional security and usefulness in certain situations by providing certificate-based access.
  1. To support SSH certificate-based access, we have made an administration interface for adding your public keys. The interface is available through your personal profile project, reachable via your name in the menu at the very top. If this still says "Create profile..." you need to click and create a profile first. Once accessed, the administration interface should be self-explanatory: It allows you to paste and add keys, or mark existing keys and delete them.
  1. All projects now have a Git/Repositories menu item under "Admin". However, like anything else this is restricted by permissions, so make sure users are assigned permissions REPOSITORY_CREATE, REPOSITORY_DELETE or VERSIONCONTROL_ADMIN as needed. With required permissions, just enter a name and create your first Git repository in seconds. And, you can even fork an existing repository as an identical copy of the original (a.k.a server-side clones). Permissions are managed through this same interface, as is the ability to delete projects.

 "Git repository administration."

Questions? Missing features? Bugs? Please let us know!

No Internet Link

Our Internet link broke twice this weekend (all times are CET):

  1. On Saturday August 27th at 11:42 the link went down. We called for emergency help and the ISP arranged for someone to come in and check cables. Unplugging and replugging cables, and as if by magic the link became active again at 16:36. 4h54m downtime.
  1. On Sunday August 28th in the evening the link started to become unreliable. Lots of packets not making it through the link, effectively slowing the service to a crawl. At 23:45 the link died completely. Contacted ISP emergency help again, but as it was now nighttime there was no real hope of immediate help. We scheduled a new visit first thing Monday morning. They arrived as promised, changed various cables and plugs, and measured all cabling for control. Link reconnected at 09:57, logging 10h12m of downtime.

We are quite confident the problem was related to cabling, and our ISP is quite confident that current cabling is OK. We sincerely hope the issue is resolved for good.

Note: When the service becomes unavailable, our Twitter account is the only reliable source of information. Do follow us if you want reliable status messages when issues arise.

DNS servers not reachable

Provider of our domain and DNS services, NetworkSolutions.com, is experiencing repeated distributed denial-of-service attacks. The DNS servers that map www.coderesort.com to address has at times not been available. We are sorry about this and any problems you may be experiencing, but it seems that the worst is now passed as the servers have started responding again.

If you are not already following us on Twitter, please follow us now:

Follow CodeResort on Twitter

Any issues will be reported and tracked on Twitter as they happen. If our service is unavailable for any reason, @CodeResort will be our only reliable channel for reaching you with the latest status.

Using svnsync to make a local project mirror

You may at any time make a full local backup of your Subversion repository using the svnsync tool that is part of Subversion.

Much information about this tool is published on the interwebs, but we've made a how-to that is as simple as it can possibly get. As always this information is available in the 'Help' section of all projects, and of course by direct link:


Together with web project backups, this lets you keep local copies of ALL your CodeResort project information.

100.000 Changesets Committed

We are fortunate to enjoy a steady rise in users, projects and activity. Our most recent landmark is passing 100.000 Subversion commits!

There is room for more, so keep them coming :-)

New Talk features: View-only & Offline notification

We've made some very useful additions to our Talk feature - available to all projects.

Offline support with notification

Screenshot showing 'Remember me...' for Talk.

As a user, you can now mark your membership in the room as permanent. If you are not presently available in the room, you will still be listed in a new 'Offline' users list.

The really useful extension of this is that we will notify you by email if someone speaks to you in the room when you are offline. That way others can bring you into the discussion, and you can bring in others as needed.

The format for addressing users is to start the line with an explicit reference to the user:

steve: Got an opinion on this new suggestion from john?

User 'steve' would be notified if not online.

View-only access to talks

It is now possible to assign read-only permission to users, and TALK_VIEW allows viewing full transcript and follow ongoing discussions. With the exception of posting new messages or uploading files.

As an extension of this feature, the view-only policy has also been enforced for rooms marked as 'closed'. Only TALK_ADMIN permission will allow posting in closed rooms.


Why not create a Talk to host your next project meeting?

Logins & Profiles

At CodeResort we provide various features and services to our users, based on various tools and technologies. It is our intention to present this largely as a unified whole, but sometimes that is hard to do - and sometimes it just makes no sense to do it.

For logins we made a very early decision to base it on email address. That allowed us to only require 2 pieces of information from our users; email + password. It was the lowest common denominator for all the tools and clients needed to work with CodeResort, and it provided the lowest level of entry for users to get started.

This makes email address the key for a dimension of our users infrastructure, and as such it cannot be changed. As any key, we could of course change it if we really, really wanted to. However, that would mean rewriting all parts of project history and would be both incorrect and dangerous to do. If we change person@companyA.com to person@companyB.com for all commits and all wiki and ticket history, would that really be correct? If person leaves Company A to take on a job at competing business Company B, would that make a new natural location for sending ticket notifications for old Company A issues that gets updated? Would it be right to reassign credit for thousands of hours of changes paid for by Company A onto Company B? Should the person retain access to all Company A projects in new role? We don't think so.

Any user that changes email needs to create a new login, and re-apply for access to the projects that now makes sense to participate in.


A natural consequence of the simple email-based key is of course that many decide to use a 'personal' email when registering, so that trivial things like changing workplace need not be an administrative burden. That's fine with us of course, you are free to use any valid email you want.

For project owners, however, this is somewhat less ideal. Being presented with a prdffdd13@hotmail.com address makes it harder to determine who this may be, a challenge that usually only becomes harder over time as people come and go in projects.

So, we came up with the concept of an optional "Profile". 'Optional' in so far that we do not require that you make one, but 'optional' in the sense that project owners may require it and only accept applications for access if you have such a profile that details your full name, place of work and basic contact details.

Link profile screenshot.

Your login is linked to this profile, and in fact the profile is a separate project just for you and your login where you may store your own information in the Wiki or use the Blog to publish facts and trivia. Through the personal project we also provide a 'My Tickets' overview page, and we hope to further extend personal projects with useful features soon.

Link several logins to one profile

A recent change we made is to add the ability to link more than one login to a profile. That means you can keep your profile ('person') and share it and access it from any of the logins you create. Moving from Company A to Company B does not mean you shouldn't be allowed to keep your own information. The details of this is available in the Admin->Logins page in your profile project.

Questions and Answers

Q: Why no Forms login? Why no descriptive forms? Why not use state-of-the-art web technologies such as OpenID / OAuth to perform authentication, instead of plain authentication requests? The simple answer is that the tools support just isn't there. There is no way to make a Subversion client perform a redirect or have it impersonate by accepting tokens and cookies. All it knows is the Basic and Digest authentication protocols. Same with the WebDAV support that allows you to connect file shares and map them as local disks. And the API that allows you to use simple tools to pull and push information. Whatever else we provided for our web-frontend we would still need to make a duplicate system that would work with all possible tools. So we have ended up sticking to the one simple way of doing it.

Q: Why can't I login using my 'handle' / shortname? We could have done that, but with profiles supporting more than one login this is not really feasible. Should we test password against any of the logins? Do we pick the first login that matches? The last? Or just make it random? What if you forgot your password, do we reset all logins or just pick one again?

Q: What if my company change name? So, what if the change from Company A to Company B is not about you changing but your employer changing? What if you get sold or merged into some new entity - or your employer just decides on a corporate name change? That is the one real-world scenario that complicates our simple rule, but we still do not have any tools to make such pervasive changes. Sorry.

Q: What's next? From the perspective of users and logins? Not much really. We'll keep using our simple scheme for logins and profiles, but keep enhancing the user experience as we did by introducing the option to link several logins to same profile.

  • Posted: 2011-03-21 02:50 (Updated: 2011-03-29 21:59)
  • Author: simon
  • Categories: news
  • Comments (0)

Subversion How-To: Develop, Branch, Merge

Ever been hard at work at something in your Subversion working copy when you realize that this really, really should have been done in a branch instead...? Whatever the reason, this situation always tends to add a level of anxiety as it really should be done without loosing hours worth of changes...

Here is our tried & tested how-to guide: HowTo/Subversion/DevelopBranchMerge

As our other documentation and guides it can always be found in the 'Help' section of your project.

Happy branching!

We are 'Open'

CodeResort is built using open source. Software made available by others, and software developed and/or maintained by our help. See for instance osimons for some pointers.

We have now added the new project open as an initiative to publish more source code - and making it available using the best project solution we know: CodeResort.com ;-)

Today we announced availability of TracTalkPlugin, and over time we will collect and publish more modules via that project. Be sure to subscribe to the 'open' RSS Timeline feed if you want to keep up-to-date on our open source activities.


  • Posted: 2010-11-11 14:58 (Updated: 2010-11-11 15:09)
  • Author: simon
  • Categories: news
  • Comments (0)

Agile CodeResort

We have considered adding 'Agile' features to CodeResort for a long time - estimation, burndown charts, sprints and so on. We have evaluated, tested and coded, but as we operate a hosted service with many projects from many organisations we cannot make any general assumption about 'method' usage. No single best-practice method can be enforced onto the thousands of developers that use CodeResort.

What we have decided on is a simple, general, non-obtrusive, optional implementation that:

  1. Adds a 'remaining' field to Tickets.
  2. Allows it to be queried with inplace edit.
  3. Allows it to be charted as status and as progress over time.

For any grouping of tickets, using any grouping/selection available in Ticket Query, the change in 'remaining' over time can be tracked to produce a nice Burndown view that can be embedded anywhere inside the project:

Example Burndown chart.

Curious? For all the details of configuration and use, see HelpUser/Estimation - also always available in the 'Help' section from inside your projects.


Batch Modify Tickets

We've added the BatchModifyPlugin to our Ticket Query module. All users with TICKET_BATCH_MODIFY or TICKET_ADMIN permission now also get a custom interface for batch modification of tickets directly from the Query interface. Queries are made via 'View Tickets -> Custom Query submenu', and have /query?... as part of the URL.

Any ticket in a Query result will get a checkbox next to it, and for any item checked the 'Batch Modify' section provides a simple interface to change ticket fields:

Batch Modify screenshot

This make it easier to manage open tickets, and even using a Query as a 'whiteboard' in project meetings to change schedule, assignment and other ticket classifications.


Improved Web Projects (Trac 0.12)

Mini Trac logo.

We have upgraded the web project software (Trac) to the latest version, and our web projects got some nice new features:

  • Improved Wiki and Ticket editors, including auto-preview while editing.
  • Edit and delete ticket comments and whole tickets.
  • Renaming of Wiki pages.
  • Much improved flexibility in Ticket Query module, allowing advanced 'and' + 'or' queries to be configured. Also query and view tickets based on created and modified timestamps.
  • Filter Timeline by author.
  • Enhancements for WikiFormatting syntax and capabilities, including improved support for the WikiCreole flavour.

Depending on your browser and its language settings, you may also see that CodeResort provides partial interface support for other languages than English. 'Partial' as not all modules are translatable or have translations yet. Internationalization of all parts of the site is a long-term effort, so be patient...

Please let us know if you experience any problems.


  • Posted: 2010-09-04 02:07 (Updated: 2010-09-09 12:58)
  • Author: simon
  • Categories: news
  • Comments (0)

DAV File Share with improved support for Web Browsers

All projects come with a project-internal file share based on the WebDAV standard.

The main scenario for use has so far been for operating systems to map the share as a drive, and for Microsoft Office and other applications with DAV support to read and write the files directly. That is still the most useful way to access the share, and the only method that allows adding, changing or deleting files.

However, we have now also configured a much improved support for using Web Browsers as clients for reading files in the project file shares. Directories will now provide listings, and files that render in browsers will be rendered directly. It allows for easy overview of the content on the share, and also makes it easier to use project-internal mini websites and similar - for instance for publishing documentation or otherwise presenting content that are intended for a 'browser-audience'.

If DAV is enabled for your project (Admin->Features), URL and your permissions to the project share are available under the File Share menu item.


Disruptions to Service and Trouble Committing Changes

We have had some trouble with a "standby" (backup) slave this weekend.

We experienced a short power loss across our server infrastructure, and in the subsequent automatic reboots an offline "standby" (virtual) slave has also been mistakenly powered on - allowing it to receive direct traffic intended for the main server. When the standby-slave periodically synced from its master, any changes recieved by slave directly was cleaned out.

Your changes between Sunday January 31st ~04:00 CET and Monday February 1st 14:00 CET may be affected by this. Please check your project to see if anything is missing.

If you have committed new revisions to a repository, or updated your working copy with changes from others, your local working copy may well be out of sync. The safest option is to check out a new, clean working copy and then transfer any missing changes to the new working copy and commit them there. Please Contact Us if you are unable to resolve this easily, and we'll help you take corrective actions.

For any non-repository changes and registrations affected by the incident, the only real solution is to re-type and post the new/updated information.

We are really sorry for any inconvenience this may have caused you, and have now taken measures to prevent this situation from arising again.

Unexpected Downtime & New Internet Connection

We experienced an unexpected downtime this afternoon - roughly from 16:00 CET to 17:00 CET. The error occured when a new planned link was configured by our ISP before it was planned to be physically connected, making it impossible to reach our network.

After locating the error we also then connected the new fiber-based line. With the recent server upgrade and this new fiber-based Internet connection, the site should now have very good performance.

Sorry for any inconvenience the downtime may have caused.

Server Upgrade Friday Oct 9th

We will be upgrading our server infrastructure on Friday night, and this will likely involve some downtime as we migrate. The window for making the changes is Friday Oct 10th 21:00 CET to Saturday Oct 11th 06:00, so during this time the services may not always be available. Naturally we will try to keep the actual downtime to a minimum.

Update: The upgrade is completed and everything should be working normally. The site was offline for approx. 25 minutes during the upgrade time window. Hopefully you will all notice that the site is much more responsive now, and please contact us if you experience any problems.

Remote Procedure Call (RPC) interface revamped - JSON-RPC added

The CodeResort API is based on the http://trac-hacks.org/wiki/XmlRpcPlugin with some custom extensions. We have now taken over maintenance of this open source plugin, and have recently put a lot of effort into upgrading and improving it.

Today we have launched the updated API, and among other things it includes a new JSON-RPC interface in addition to the XML-RPC interface we've had for quite some time.

A simple illustration of what that the JSON-RPC interface looks like:

  1. Make a POST request to https://www.coderesort.com/p/<projectname>/login/jsonrpc with header Content-Type set to application/json and a request body like:
    {"method": "wiki.getPage", "params": ["WikiStart"]}
  2. Parse and use the response:
    {"id": 123, "error": null, "result": "= Welcome to....

There are clients that work with the API, like Eclipse Mylyn and some of our own tools we have made available. Further, the API can of course be used for any custom integration with your own information systems - for instance as an interface with a customer support system, or with internal reminder, scheduling, or publishing tools.

See the api project for all the details on how to get started.

Lots of exciting possibilities!

  • Posted: 2009-06-20 12:57 (Updated: 2009-06-20 13:03)
  • Author: simon
  • Categories: news
  • Comments (0)

Start Talking!

A project at CodeResort is a container for source, documentation, tickets, news and more. Our intention is being able to capture and track history for all formal and informal aspects of project progress.

With the addition of 'Talk' for all projects, there is now also a way for interactive group chats in projects. This new feature can be used for many cool things:

  • Do online project meetings. No travel needed. No typing of minutes with the full transcript always being available.
  • Make a Talk for general project chat, and have the project members 'hang out' there and post their questions for all to see and share. Enlighten everyone.
  • Make a Talk to act as a Twitter-like stream of notes from the project progress. Stay updated.
  • Create a Talk to act as a pasteboard, post snippets and insights for discussion, solve code problems, do code reviews.
  • Use a talk to log events - like a 'deployment log' or 'build log' for information and follow-ups.

Curious? See screenshot (from early testing at the Epicode chat).

Talk is enabled for all projects by default, but some configuration is needed to take full advantage of the feature:

  1. Users of talk rooms, need TALK_USE permission. Creators of rooms need TALK_CREATE.
  2. Create rooms. Start with as few rooms as possible to focus attention - increase as needed.
  3. Activity in Talk rooms are recorded at hourly basis, but remember to tick-off to include 'Talk logs' in your view. Not least if you already have added Timeline RSS feeds - if so you need to grab a new feed, or edit the feed adding &talk=on to the pre-existing query parameters.

As usual, the code for the Talk plugin will be made available as open source (soon) - based on our customer promise that any project created or used at CodeResort is yours to set up anywhere else, whenever you want.

We would welcome feedback on this feature - add a comment to the blog post, or contact us with your input.

New SSL Certificate

We have updated our SSL certificate. If you see a message similar to:

Error validating server certificate for 'https://www.coderesort.com:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.coderesort.com
 - Valid: from Fri, 13 Feb 2009 11:58:50 GMT until Mon, 04 Jul 2011 10:58:50 GMT
 - Issuer: Equifax Secure Inc., US
 - Fingerprint: ee:79:36:14:81:be:cb:d8:90:ca:80:3c:48:0d:32:0e:49:48:c5:e2
(R)eject, accept (t)emporarily or accept (p)ermanently?

... then please accept it.

It should not be an issue with browsers, but as Subversion clients usually come without any pre-approved Certificate Authorities, all certificates must be explicitly accepted.

Subversion 1.5 and Merge Tracking

We have been running Subversion 1.5 on the server for some time, and tonight we have also upgraded the repository format for all existing projects. If any users are still using pre-1.5 clients, now is the time to upgrade.

Subversion 1.5 brings many improvements and new features: http://subversion.apache.org/docs/release-notes/1.5.html

First and foremost is the automagic merge-tracking support. This has been a much-requested feature, and it basically means that Subversion stores properties on your branches to remember what revisions are already integrated between them. It makes for easy copying (branching), merging and reinterating.

Take a look at these short blog posts for a quick introduction to merge-tracking:

And for those keen to learn even more, there is always the definitive reference...: The Subversion Book

Do you have further links or insight? Add a comment!

  • Posted: 2009-05-21 04:18 (Updated: 2011-06-14 12:15)
  • Author: simon
  • Categories: news
  • Comments (0)

Speaking at GoOpen 2009

Today I did a talk at GoOpen 2009 - a two-day conference about sharing and open source.

My talk - and its description was in Norwegian:

Deling av egen kode

Et åpent tankesett har verdi for alle utviklingsprosjekter - uansett grad av faktisk ekstern åpenhet. Bli kjent med format og metoder for gjennomføring av åpne prosjekter, og erfaringer og praktiske hensyn knyttet til deling av egen kode med andre.

OpenOffice slides og alt som ble sagt som slide notater kan lastes ned her, alternativt som PDF (slide notater).

New Feature: Rendering README files when browsing repostiory

We have just released a new feature that allows 'README(*)' files to be rendered when browsing the source through the web interface ('Browse Source' menu item). This is a great feature for connecting the source with getting started and further information, licensing issues and similar.

The feature is documented in the 'Help' section as HelpUser/RepositoryReadMeFile, and it should provide the information you need to get started providing your users with better and more immediate information about your source code.

A simple example can be seen in the reiseregningen project.

As usual, we have made this feature available as Open Source - see ReposReadMePlugin by osimons.

Hope you like it!

New Public Project: 'reiseregningen' by the Norwegian Government

A new public project from Fornyings- og administrasjonsdepartementet (FAD) - a department of the Norwegian government - has just launched on CodeResort.

The site hosts a public project for the development of http://www.reiseregningen.no - the 'official' way to document your travel expenses in many Norwegian public and private institutions.

Visit the project (in Norwegian):

Error: Projectname not recognised.

Issue with sporadic hang is fixed

In recent weeks and months we have experienced an issue whereby the web projects become unresponsive - basically unable to serve your requests. During this time we have kept a very close watch to make sure we get it back online as soon as possible. Still, we know that some of you no doubt have been inconvenienced by these short downtimes.

The good news is: We have discovered and fixed the cause of the issue.

A bug in [[TOC]] wiki macro only appeared when requests where made to a page in a project that used the macro, and such a project would then permanently claim one database connection. It 'infected' a project on first view, but it did not get worse by itself. However, at random intervals pages with the macro was requested on other projects tying up new connections until at some point no further database connections could be established.

(Those that are technically inclined can read about the issue and see my fix at http://trac-hacks.org/changeset/4366)

Finding this bug has taken much longer than we had imagined. However, it has led us to review all the central parts of the code, and fixing and reworking some parts that were not optimal. Additionally, we have updated all server software to the latest and greatest versions. The service is now in very good shape.

We can only apologize, and thank you all for being patient with us trough this period.

Backups available!

We now have backups... Just joking - we have of course done central backups every day since doors opened back in 2006.

The big news is that if you are a project administrator, you can generate and download full backups of the web project yourself:

Backups screenshot.

The new Backups Admin page is available for all regular projects, and it also has pointers to Subversion syncronisation (svnsync) and WebDAV file share access.

Together this means that every single byte of data, history and settings related to your project is available to you whenever you want it.


  • Posted: 2008-07-30 02:04 (Updated: 2008-07-30 02:14)
  • Author: simon
  • Categories: news
  • Comments (0)

What You See Is What You Get

To make CodeResort even easier to use, we have today enabled a WYSIWYG-editor for all projects.

The editor is optional, allowing you to switch between viewing modes using the wysiwyg/textarea radio buttons that will now be available on all input textareas on the site:

The new WYSIWYG editor in action.

Ain't that nice?

Using the editor should be mostly self-explanatory - try out the buttons with or without selected text and see what happens.

Login, Profile and Project Membership changes

This week we have made some changes to how user registration and applications for project membership works.

As before, the minimum required to create a login is a valid e-mail address. However, very often the needs of project owners extend beyond that in order to evaluate and grant permission, and to get in touch with project members if needed.

Based on this we have made a setting in a new 'Memberships' admin page:

Screenshot of setting to 'require profile'.

The setting is optional for each project, and what is needed will be clearly stated on the application form. When granted access to such a project, your basic profile information (name, company and contact details) will be available to the owners of that project.

We have made a number of improvements to the registration and application forms when implementing this, and hopefully getting access to projects will be even easier than before.

  • Posted: 2008-02-19 19:36 (Updated: 2008-02-21 01:03)
  • Author: simon
  • Categories: news
  • Comments (0)

Blog feature available for all projects

Every project on CodeResort now has a Blog:

  • Regular projects (/p/projectname) have a project-internal blog, available to project members only.
  • User projects (/u/username) have a public blog for anonymous access - open to the world.

Blog for regular projects

The Blog is enabled by default for all projects, but only project administrators will actually see it due to their extended permissions. To let other in you need to set permissions. A typical setup based on our default permission setup is:

  • Grant BLOG_MODIFY_OWN to members ('@member' group) so they can view all the news, post their own news, but not modify the news of others.
  • Also, grant them BLOG_COMMENT permission so that the project members can comment on blog posts.

Why a project blog? Our motivation for this feature was to find a nice and simple way to bring any kind of 'news' into the project information - and documentation. It fills a much needed gap for information that does not fit nicely into either wiki, tickets, or changeset messages. We can't tell you how you should use it, but here are some ideas for inspiration:

  • News on project organisation, introducing new project members or new responsibilities.
  • Project deliveries such as releases / deployments and changeovers, announcing branches and the like.
  • Pulling together a number of tickets, changesets and wiki updates into a coherent overview of what has actually happened and why.
  • Notes on changes to developer setups, dependencies or similar information needed for people to do their work.

The blog has its own RSS feed for full-length messages, and it also puts all creations, edits and comments into the Timeline. Note that if you already have a Timeline RSS feed set up, you need to grab the URL again to get the blog events (blog=on needs to be added to the query string).

Try it out, and see what it can do for you and your project.

Blog for user projects

Having the blog feature available, we thought it would be a great idea for any user with their own project to also have a blog to share their findings and thoughts with others. The user project blog is all pre-configured and ready, so just get started posting.

Note: If you have a login but no user project, you basically only need to click 'Create Profile' in the top navigation menu. Fill in the form, and your own personal mini-project is created. Currently a 'user project' has the following main features:

  • A Wiki, only available for you.
  • 'My Tickets' - your own overview of all open tickets in all projects on CodeResort where you are somehow involved.
  • The Blog that is available to the world.

If you do start using your personal blog, let us know so that we can add a link to your blog in the sidebar here.

More Information

We've also added a help page with further information about the blog - see 'Help' form inside your project, or read the wiki page here if you are logged in: HelpUser/Blog

Open Source

Lastly, just a note to say that the blog feature is made available as open source - developed and maintained by CodeResort: http://trac-hacks.org/wiki/FullBlogPlugin

This is done to ensure that whatever data you enter into your project here at CodeResort, will also be available and accessible if you for some reason should want to move your project away from CodeResort later.


Do you like the blog? Does it make sense? Do you have requests for changes or new additions to the functionality?

We made it for you, and appreciate any help you can give us in making this a useful feature.

CodeResort upgraded - new features and important information

Last night we upgraded CodeResort to a new version bringing lots of shiny new features. There will be in-depth introductions to new features and usage examples shortly to get you started using them, so for the moment I just wanted to provide some important information to current users about some changes that may involve minor updates in your projects related to wiki syntax:

  1. The [[TOC]] macro has changed slightly, so for a list of pages 'starting with...' you now need to append a '*' to the partial pagename. Without the wildcard, it will only fetch the page with that exact name. Some of the other macros have also seen minor changes, so if they don't work as expected be sure to look at the Help page for HelpUser/WikiMacros.
  2. Syntax for project- and server-relative linking has now changed. [/somewhere] now uses the project as root for urls, so if you want to link to some resource in another project you use this syntax to base it on the server root: [//somewhere]. Or, even better is the new InterWiki syntax that lets you make your own custom links to external resources. Check HelpUser/InterWiki for now - I'll blog about this in not too long.
  3. The {{{#!html}}} syntax is still allowed, but each section now has to be valid html in order to render - if not, it will be skipped. The trick of embedding wiki inside some open and close html element sections now have a better solution using the new #!div and [[span]] syntax. Read up on this in Help; HelpUser/WikiAdvanced.

Updating all our own content, these were the most visible to us. If you find other issues that are not clearly covered here or in Help, please let us now. Perhaps by logging in and leaving a comment on this blog post.

Lastly, here are some of the new features that I have in my 'to-blog' list - make sure to check back soon or subscribe to the blog RSS feed:

  • Project Blog for project-internal news and information, and even a public blog for any users that have created a profile at CodeResort.
  • InterWiki link support.
  • Improved ticket workflow and ticket and query improvements in general.
  • Subversion 'Annotate' (Blame) of any file in the repository.
  • Turn off or on features for your project.
  • Wiki page templates for standardising content and structure of new wiki pages.
  • ...and more.

Hope you enjoy the new release! Stay tuned!

  • Posted: 2008-01-18 03:18 (Updated: 2008-01-18 22:19)
  • Author: simon
  • Categories: news
  • Comments (0)