Loading...

Posts for the month of January 2008

Annotate (Blame) for source code

One of the recently available features is the ability to annotate the source code - most commonly called 'blame' support due to it's popular use of finding out who (and when) and error was introduced...

When browsing a source file, there is now a new 'Annotate' option:

The new menu option.

Selecting it will render the changesets for each line, and the tooltip will provide some basic information - selecting the changeset will take you directly to it:

Showing Annotate in use.

Ain't that nice?

  • Posted: 2008-01-24 13:54 (Updated: 2008-01-26 01:00)
  • Author: simon
  • Categories: howto
  • Comments (0)

Quick Links in Search field for easy navigation

Quick Link Example

Here is a tip for quickly navigating to a resource when you know its name. Just enter it as a link in the 'Search Project' field.

Here are some examples for you to try in your own project:

  • #42 - ticket number 1
  • [42] - for changeset 42
  • {3} - for report number 3
  • RecentChanges - for wiki page of that name

Pretty much all resources in your project is directly linkable - have a look at the HelpUser/Links help page to see the possibilities and review syntax.

  • Posted: 2008-01-24 13:54 (Updated: 2008-01-26 01:02)
  • Author: simon
  • Categories: howto
  • 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.

Feedback?

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)

The Official CodeResort Blog

Welcome to CodeResort, and the official CodeResort blog!

We will use the blog for any information about the service to our users, so make sure to check back often to get the latest news and how-to's to utilise the service for your project.

The blog is available for anonymous read access, and any RSS feed reader will be able to read our syndicated content.

As a CodeResort user you can also comment on the blog posts. Make sure you are logged in, and an 'Add Comment' field will be available. We do appreciate your feedback, so please let us know your opinion!



Best regards,

The CodeResort Team

  • Posted: 2008-01-17 22:54 (Updated: 2008-01-18 11:40)
  • Author: simon
  • Categories: general
  • Comments (0)