Ruby on Rails: Sublime Text Packages

I’ve finally moved from Vim (which is still awesome) to Sublime Text as my primary editor for Ruby on Rails development, here are some of my favorite packages.

Sublime Text Package Manager

Thanks to the package manager, installation of packages is straightforward.  More details on installation and usage of the package manager can be found here: 

[list_icon color=”blue” type=”icon_arrow”]


Bracket Management

Bracketeer provides some bracket manipulation, selection, and insertion commands, whilst BracketHighlighter assists with, bracket matching and highlighting.

[list_icon color=”blue” type=”icon_arrow”]


SideBar Enhancements

The SideBarEnhancements package provides useful enhancements to the operations on the Side Bar of files and folders for Sublime Text.

[list_icon color=”blue” type=”icon_arrow”]


Related Files

The Related Files package provides a quick list of related files to the currently open file, and can be used for any kind of project.  Rails Related Files is geared towards Rails specific projects, and uses some basic assumptions to easily navigate project files.

[list_icon color=”blue” type=”icon_arrow”]



The EasyMotion package is inspired by Vim’s EasyMotion, and allows you to move to any character within the view.

[list_icon color=”blue” type=”icon_arrow”]


Trailing Spaces

Sublime Text provides a way to automate deletion of trailing spaces upon file saving with the following setting:

“trim_trailing_white_space_on_save”: true

However, it is sometimes handy to highlight spaces and remove them manually, using the Trailing Spaces package.

[list_icon color=”blue” type=”icon_arrow”]


Color Schemas

Sublime Text has some good default color schemes, here are some more:

[list_icon color=”blue” type=”icon_arrow”]



Even though I prefer the command line for git, visual indicators as provided by Git Gutter are useful.

[list_icon color=”blue” type=”icon_arrow”]


More Sublime Text Resources

[list_icon color=”blue” type=”icon_arrow”]



Enhanced by Zemanta

Favourite WordPress Plugins

At Webware Studios, our Internet Marketing division, we specialise in creating WordPress websites for small and medium-sized businesses who want a professional website that is still affordable and suits their limited budgets. WordPress is a content management system that allows one to constantly update content on their website and provides an easy-to-use user interface for novices wanting to blog or keep their websites fresh. WordPress is known for its functionality and abundance of themes and WordPress plugins, which allow you to customise your site to suit your needs.

We’ve rounded up a few of our favourite WordPress plugins for small business websites:


Usually already installed on all WordPress sites, Akismet is by far the best WordPress plugin to combat spam on your blog. All you need to do is activate it and register with them in order to receive your activation key. This is a must for every website that allows comments.

Under Construction

This WordPress plugin is our very first step when setting up a new live website. It allows you to create a “Coming soon” page that is visible to users that are not logged in. However, as the web developer, you are still able to see the front end of the website when logged in. This WordPress plugin is very useful when you don’t want outsiders seeing the changes you are making whilst building the website.

Better WP Security

Better WP Security adds that extra peace of mind in protecting your website against hackers and attacks by plugging as many security holes as possible. This WordPress plugin is easy to use for beginners as well as providing more advanced options for the more experienced user.

Contact Form 7

Contact Form 7 is a really popular WordPress plugin for users wanting to add a contact form to their websites. It is easily customisable, allowing you to specify what fields to add as well as error messages to be displayed when incorrect information is entered.

Google XML Sitemaps

Important for SEO, the Google XML Sitemaps plugin creates and XML sitemap for you that enables web crawlers to index your site. In addition, each time you create a new post, the plugin automatically notifies all major search engines. Super Neat, right!

Page Links To

One of our favourite WordPress plugins, Page Links To allows you to a point a page or post to a different URL that you specify. This comes in handy for menu structures, especially placeholder menu items that when clicked on, can direct to a specific page. 

Simple Backup

Simple backup creates and downloads backups of your site. This is a great tool to have, especially when it’s time to upgrade your WordPress version or create backups for safe-keeping.

WordPress SEO

One of the all-round best SEO plugins, WordPress SEO by Yoast covers all bases and provides great insight on areas to improve. It is perfect for beginners or SEO experts and ensures that you optimise each page. The Page Analysis feature is one of our favourites, where it reminds you of easily forgotten items such as adding images to your posts and optimising your permalink.

Related Posts & Images by Zemanta

Zemanta makes blogging easier. This WordPress plugin adds related posts, in-text links as well as suggests images and tags that are related to your topic. 



Enhanced by Zemanta


Permissions and Security

What is an issue ‘security level’?

Issue security levels allow you to control who can see individual issues within a project.

A security level’s members may consist of:

[list_icon color=”blue” type=”icon_arrow”]

  • Individual users
  • Groups
  • Project roles
  • Issue roles such as ‘Reporter’, ‘Project Lead’, and ‘Current Assignee’
  • ‘Anyone’ (eg. to allow anonymous access)
  • A (multi-)user picker custom field.
  • A (multi-)group picker custom field.


Here is a list the different global permissions and the functions they secure:

[list_icon color=”blue” type=”icon_arrow”]

  • JIRA System Administrators – Permission to perform all JIRA administration functions.
  • JIRA Administrators – Permission to perform most JIRA administration functions. A user with JIRA Administrators will be able to log in to JIRA without the JIRA Users permission, but may not be able to perform all regular user functions (e.g. edit their profile) unless they also belong to a group that has the JIRA Users permission.
  • JIRA Users – Permission to log in to JIRA.
  • Browse Users – Permission to view a list of all JIRA user names and group names.


Creating an issue security scheme

1. Depending on the Jira version, Choose Issues > Issue Security Schemes to open the ‘Issue Security Schemes’ page, which lists all the issue security schemes currently available in your JIRA installation.

JIRA permissions and security - admin

2. Click the Add Issue Security Scheme button

JIRA permissions and security - security schemes

3. In the Add Issue Security Scheme form, enter a name for the issue security scheme, and a short description of the scheme. Then click the Add button.

4. You will return to the Issue Security Schemes page, which now contains the newly added scheme.

JIRA permissions and security - issue security schemes

Adding a security level to an issue security scheme

[list_icon color=”blue” type=”icon_arrow”]

  • Choose Issues > Issue Security Schemes to open the ‘Issue Security Schemes’ page.
  • Click the name of any scheme, or the link Security Levels (in the Operations column) to open the Edit Issue Security Levels page.
  • In the Add Security Level box, enter a name and description for your new security level and then click Add Security Level.


Setting the Default Security Level for an issue security scheme

You can choose to specify a Default Security Level for your issue security scheme.

The Default Security Level is used when issues are created. If the reporter of an issue does not have the permission ‘Set Issue Security’, then the issue’s security level will be set to the Default Security Level. If the project’s issue security scheme does not have a Default Security Level, then the issue’s security level will be set to ‘None’. (A security level of ‘None’ means that anybody can see the issue.)

1. Choose Issues > Issue Security Schemes to open the ‘Issue Security Schemes’ page.

2. Click the name of any scheme or the link Security Levels to open the Edit Issue Security Levels page.

[list_icon color=”blue” type=”icon_arrow”]

  • To set the ‘default’ security level for an issue security scheme, locate the appropriate Security Level and click its Default link (in the Operations column).
  • To remove the ‘default’ security level from an issue security scheme, click the ‘Change default security level to “None”‘ link (near the top of the page).


Adding users/groups/project roles to a security level

[list_icon color=”blue” type=”icon_arrow”]

  • Choose Issues > Issue Security Schemes to open the ‘Issue Security Schemes’ page.
  • Click the name of any scheme or the link Security Levels to open the Edit Issue Security Levels page.
  • Locate the appropriate security level and click its Add link (in the Operations column), which opens the Add User/Group/Project Role to Issue Security Level page.
  • Select the appropriate user, group or project role, then click the Add button.
  • Repeat steps 4 and 5 until all appropriate users and/or groups and/or project roles have been added to the security level.


Assigning an issue security scheme to a project

1. Choose Projects > Projects to open the ‘Projects’ page. Select the name of the project of interest. The Project Summary page is displayed.

JIRA permissions and security - projects

2. In the Permissions section of the Project Summary page, click the link corresponding to the Issues label to open the Associate Issue Security Scheme to Project page. This will either be the name of the project’s current issue security scheme, or the word None.

JIRA permissions and security - permissions

3. Select the issue security scheme that you want to associate with this project.

JIRA permissions and security -associate scheme

4. If there are no previously secured issues (or if the project did not previously have an issue security scheme), skip the next step.

5. If there are any previously secured issues, select a new security level to replace each old level. All issues with the security level from the old scheme will now have the security level from the new scheme. You can choose ‘None’ if you want the security to be removed from all previously secured issues.

6. Click the ‘Associate‘ button to associate the project with the issue security scheme.

JIRA permissions and security -associate security

Deleting an issue security scheme

1. Choose Issues > Issue Security Schemes to open the ‘Issue Security Schemes’ page, which lists all the issue security schemes currently available in your JIRA installation.

2. Click the Delete link (in the Operations column) for the scheme that you want to delete. You cannot delete an issue security scheme if it is associated with a project. To do so, you must first remove any associations between the issue security scheme and projects in your JIRA installation.


Enhanced by Zemanta

How to write a simple plugin that adds a new tab in JIRA

How to write a simple plugin that adds a new tab (section) to JIRA’s top-level menu, with a number of menu items in the section. The menu items link to specific web pages. 

You can use this sort of plugin to add links from JIRA to other locations in your environment, such as your company’s intranet or your Confluence site.

In order to do this, you will create a JIRA plugin consisting of the following components:

[list_icon color=”blue” type=”icon_arrow”]

  • A plugin descriptor to enable the plugin module in JIRA.
  • The required plugin modules that define the new menu section and menu items.


Step 1. Create the Plugin Project

Use the appropriate atlas-create-application-plugin command to create your plugin. For example, atlas-create-jira-plugin or atlas-create-confluence-plugin.
[list_icon color=”blue” type=”icon_arrow”]

  • Follow the instructions in the above SDK documents to set up your plugin development environment.
  • Follow the instructions in the above SDK documents to run atlas-create-jira-plugin. This will create your skeleton plugin. You will be prompted for some information to identify your plugin. Enter the following information:

group-id: com.infowarestudios.plugins.MaintainSLA
artifact-id: jira-MaintainSLAMene-items
version: 1.0
package: com.infowarestudios.plugins.MaintainSLA


When the script finishes, open your new local instance of JIRA in your browser at http://localhost:2990/jira.

Your plugin skeleton is already installed and running in JIRA. Take a look at it now, by following these steps:
[list_icon color=”blue” type=”icon_arrow”]

  • Click the downward-pointing arrow next to ‘Administration‘ in JIRA’s top menu bar.
  • Select ‘Plugins‘ from the dropdown list.
  • The ‘Current Plugins’ page opens. Search for ‘jira-menu-items‘ and click the link.

The detail for the plugin will appear

Step 2. Add Plugin Metadata to the POM

Now you need to edit your POM (Project Object Model definition file) to add some metadata about your plugin and your company or organisation.
[list_icon color=”blue” type=”icon_arrow”]

  • Edit the pom.xml file in the root folder of your plugin.
  • Add your company or organisation name and your website to the <organization> element:
<organization>    <name>Infoware Studios</name>    <url></url></organization>
  • Update the <description> element:
<description>This plugin adds a new section and items to JIRA's menu</description>
  • Save the file.


Step 3. Register the Plugin Modules in the Plugin Descriptor

Next you will add the required plugin modules to your plugin descriptor at src/main/resources/atlassian-plugin.xml. The plugin descriptor is an XML file that identifies the plugin to JIRA and defines the functionality that the plugin requires.

Here’s a basic plugin descriptor:








Note that some of the information from the POM is transferred to the plugin descriptor using variable names such as${project.artifactId}.

You will need the following plugin modules:

[list_icon color=”blue” type=”icon_arrow”]

  • web section to define the new tab (section) in your JIRA top navigation bar.
  • A number of web items to add the links and menu items to the new section.


Follow these instructions to add the new section and menu items:

[list_icon color=”blue” type=”icon_arrow”]

  • Edit your plugin descriptor at src/main/resources/atlassian-plugin.xml.
  • Add the following web section into your plugin descriptor. This defines the top-level section where we will put all our menu items and links:
<web-sectionkey="my_links_section"name="My Links MainSection”location=”my_links_link”weight=”10″/>
  • The weight attribute determines the order in which web items appear. Items are displayed top to bottom or left to right in order of ascending weight. The ‘lightest’ weight is displayed first, the ‘heaviest’ weights sink to the bottom. The weights for most applications’ system sections start from 100, and the weights for the links generally start from 10. The weight is incremented by 10 for each in sequence so that there is ample space to insert your own sections and links.
  • Add the following web item. This defines the link on the top-level section, with text ‘My Company’. We have pointed the link at the company website:
<web-itemkey="my_links_link"name="Link on My Links MainSection”section=””weight=”47″>    <label>Maintanance</label>


  •  The linkId is optional, and provides an XML id for the link being generated.
  • Add another web item, to create a single menu item with text ‘Web Site’ that links to your company website.
<web-item key="website_link" name="my client" section="my_links_link/my_links_section" weight="10"><label>Client details</label><link linkId="website_link">http://localhost:8084/MaintainClient/</link></web-item>
  • Add another web item, to create a menu item with text ‘Documentation’ that links to your documentation website.
<web-item key="documentation_link" name="my SLA" section="my_links_link/my_links_section" weight="10"><label>SLA</label><link linkId="documentation_link">http://localhost:8084/MaintainSLA/</link></web-item>
  • Save the file.


Here’s what your atlassian-plugin.xml file looks like now:

<atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${}" plugins-version="2"><plugin-info>



<vendor name="${}" url="${project.organization.url}" />

<param name="plugin-icon">images/pluginIcon.png</param>

<param name="plugin-logo">images/pluginLogo.png</param>



      <web-section key="my_links_section" name="My Links Main Section" location="my_links_link" weight="10"/>


<web-item key="my_links_link" name="Link on My Links Main Section" section="" weight="47">





<web-item key="website_link" name="my client" section="my_links_link/my_links_section" weight="10">

<label>Client details</label>

<link linkId="website_link">http://localhost:8084/MaintainClient/</link>



<web-item key="documentation_link" name="my SLA" section="my_links_link/my_links_section" weight="10">


<link linkId="documentation_link">http://localhost:8084/MaintainSLA/</link>



      <web-item key="documentation_link" name="Line of Business" section="my_links_link/my_links_section" weight="10">

<label>Line of Business</label>

<link linkId="documentation_link">http://localhost:8084/MaintainLOB/ </link>



<web-item key="documentation_link" name="Application" section="my_links_link/my_links_section" weight="10">


<link linkId="documentation_link">http://localhost:8084/MaintainApplication/ </link>



      <web-item key="documentation_link" name="Root Cause" section="my_links_link/my_links_section" weight="10">

<label>Root Cause</label>

<link linkId="documentation_link">http://localhost:8084/MaintainRootCause/ </link>



Step 4. Build, Install and Run the Plugin

Follow these steps to build and install your plugin, so that you can test your code. If you have not already started the application, start it now:

[list_icon color=”blue” type=”icon_arrow”]

  • Open a command window and go to the plugin root folder (where the pom.xml is located).
  • Run atlas-run (or atlas-debug if you might want to launch the debugger in your IDE).



Enhanced by Zemanta

Agile: A Journey

Every journey has a start and an end destination. In life we tend to focus so hard on the end destination that we forget about the journey itself.

Agile is a lifestyle

With agile people tend to think it’s a quick fix or the silver bullet instead of a journey.  Or we start the journey and then decide it takes too long or it simply isn’t working and then start all over on a different journey.  But we forget that any journey takes time and effort. And with everything new that must be learned, minds that must be changed and attitudes to adjust we forget to enjoy the journey we are taking.  Not just the journey that an organization is taking but also the journey that you as an individual are taking. 

Once you start on the agile journey you will learn that it is never ending and that it isn’t something you can simply leave at the office. Agile becomes part of your life and the more you invest in getting to know about agile the more you want to learn about it. 


Enhanced by Zemanta

SpecFlow – Agile Testing with Visual Studio


SpecFlow supports TDD (Test Driven Development) and BDD (Behavior Driven Development) concepts, and integrates very well with Visual Studio.

Installing SpecFlow

Installing SpecFlow is straightforward, simply go to the Visual Studio Gallery site, download the SpecFlow extension and then install it.

Creating a new SpecFlow project

Once SpecFlow is installed, follow these steps to create a new project as part of your solution:

Create a new Unit Test project in Visual Studio, and Add SpecFlow as reference using the menu options: Tools -> Library Package Manager -> Manage NuGet Packages for Solution.

Select Online, then search for SpecFlow. Now select and install it.


New feature files can either be added via Add New Item, or Add Existing Item. A corresponding #C file will be generated for each .feature file.

Edit the feature file, then (inside the edit window) open the context window (right-click inside the file). From the menu, select ‘Generate Step Definitions’


A dialog will be presented, from where step definition skeletons can be selected for automatic generation:


The following will be added to each method in the step definition file, remove these whilst adding the actual code



Remember to add a reference (in the Project Explorer) to the existing project to be tested, this will be used when completing the step definition files.

Add the following to the newly created step definition file, also with references to the modules to be tested:

using System;
using TechTalk.SpecFlow;
using Microsoft.VisualStudio.TestTools.UnitTesting;

There are various scenario runners available, we’ve found that MSTest offers one of the better solutions. Change application config as follows:

<unitTestProvider name=”MsTest” />


Right-click on the project, and select ‘Run Scenarios’.

If all scenarios are completed successfully, this will be the resulting display:


Pending or failed scenarios will be marked accordingly, and drill-down options are available to find the point of failure.


It offers a very good solution for introducing BDD and agile testing to Visual Studio solutions.


SpecFlow –

Visual Studio Gallery –

Modify default SpecFlow templates –


Enhanced by Zemanta

Setting up Torquebox on Rails as a webserver

Rails and Microsoft Azure

Preparing your Rails application for running on Microsoft Azure

If you are using a Mac (obviously as Rails just works so good with it!) you will install the command line tools for connecting to your Azure server.

 This link explains how to do that:

We already have Azure accounts so we skipped that step.

Then pull settings from your Azure server over to your local machine to enable publishing to the Azure server. See on the above link: How to download and import publish settings

Getting Torquebox up and running as a Rails webserver

 First: check and upgrade rvm version

If you do not have the right rvm version you will get the following error:

jruby-1.7.2 – Error: Your application used more stack memory than the safety cap of 2048K.

Instructions for setting up Torquebox

The link below provides detailed instructions on setting Torquebox up:






Enhanced by Zemanta

Writing content for your website

You know that you need a website, but other than the name of your business, you don’t have a clue of where to start in terms of writing content for your website pages.

Does this situation sound familiar?

Your website is the first place that people go to find out more information about your business and how it can fulfill their needs. So keep that in mind when developing your website content and the rest should follow.

Tips on developing content for your pages

Here are a few tips on developing and writing content for your website:

Writing Content Tip 1:

Start with the basics. All websites should have a home page, about page and contact page at the very least.

Writing Content Tip 2:

Your home page is usually the first page that visitors see. Write a paragraph about what your business does, focusing on the products or services that could most benefit the person visiting your site. In short, you want to explain what your business is/does in a few sentences that are easy to understand. Also remember to add a call to action on your home page. Tell people to “Contact you now”, “Get a free quote”, “Buy now” etc. Make it a noticeable button on your home page to help convert visitors to clients.

Writing Content Tip 3:

Believe it or not, but the about page is one of the most visited pages on a website. People want to know about you and your company. They want to feel as if they know the person and/or business that they are engaging with. So include the history of your business, how you came up with the idea and who you are as a person. It is also great to add the business’s vision, mission and goals to this page in order to give people a sense of what you stand for.

Writing Content Tip 4:

The contact page is vitally important. Try to provide as many ways as possible for potential clients to contact you. Supply an email address, phone number, postal address (or physical address if you have offices), as well as a contact form. Make sure that the contact form works, that the email address you provide works and that the phone number works. Providing a map to your offices or directions also adds a nice touch for people who might not know how to find you.

Writing Content Tip 5:

Once you have covered the basic 3 above, it is time to focus on your services or products. This is the heart of your site as it provides information that will hopefully lead to a sale. Try to explain your service/product offering in the most easy to understand way, so that people who are completely new to your offering can understand what it is that you sell/provide. If there is a lot of information about your product, rather give readers the option of reading more by going to another page. Steer clear from too much content as visitors can be fickle in terms of not wanting to read everything. Write based on what your target market want to read, or the information that they are likely to ask you in person.

These are just the minimum basics in terms of content to have on your website pages and would obviously change according to your specific business and its needs. Examples of other pages could be testimonials, your portfolio, your list of clients, your team, the techniques that you use, FAQs etc. Follow these basics to begin with and you’re already on your way to a good website.


Enhanced by Zemanta

Agile Tool Support: JIRA System Administrator Guide – JIRA Workflows

JIRA Training

As part of our JIRA training modules, we have developed instruction guides to assist users when making use of JIRA as an Agile tool. In this blog series, we will be providing tutorials for JIRA System Administrators on how to perform certain functions in JIRA. Part 1 deals with the Issues and Fields elements in JIRA. In Part 2, we take a look at JIRA Workflows.

JIRA Workflows

A JIRA workflow is the set of steps (or statuses) and transitions that an issue goes through during its lifecycle. Workflows typically represent business processes.

JIRA ships with a built-in workflow called ‘jira’. This workflow, also known as the ‘system workflow’ cannot be edited, but you can customise the issue lifecycle by initially copying the system workflow or creating new workflows from scratch. Each workflow can be associated with particular projects and (optionally) particular issue type(s), via a workflow scheme.

JIRA’s system workflow

JIRA Workflows system

JIRA workflows consist of steps and transitions:

step represents a workflow’s current status for an issue. An issue can exist in one step only at any point in time. Each workflow step corresponds to a linked status. When an issue is moved into a particular step, its status field is updated to the value of the step’s linked status. In the diagram above, the blue boxes represent steps/statuses.

transition is a link between two steps. A transition allows an issue to move from one step to another step. For an issue to be able to progress from one particular step to another, a transition must exist that links those two steps. Note that a transition is a one-way link, so if an issue needs to move back and forth between two steps, two transitions need to be created.

About ‘Open’ and ‘Closed’ issues

Within JIRA an issue is determined to be Open or Closed based on the value of its Resolution field not its Status field.

[list_icon color=”blue” type=”icon_arrow”]

  • An issue is determined to be Open if its Resolution field has not been set.
  • An issue is determined to be Closed if its Resolution field has a value (e.g. FixedCannot Reproduce).


This is true regardless of the current value of the issue’s Status field (OpenIn Progress, etc).

So if you need your workflow to force an issue to be Open or Closed, you will need to set the issue’s Resolution field during a transition. There are two ways to do this:

[list_icon color=”blue” type=”icon_arrow”]

  • Set the Resolution field automatically via a post function.
  • Prompt the user to choose a Resolution via a screen.



Adding a new status

Select Administration > Issues > Statuses to open the View Statuses page, which lists all statuses, along with a form underneath to add a new status.

JIRA Workflows - view statuses

Complete the Add New Status form towards the end of the page. The View Statuses page can be used to edit and delete Statuses.

Adding a new workflow

Select Administration > Issues > Workflows to open the Workflows page, which shows a list of all existing workflows in your system.

JIRA Workflows - existing workflows

Create a new workflow in JIRA using either of the following methods:

1. Create a ‘blank’ workflow by first clicking the Add Workflow button and in the resulting Add Workflow dialog box:

[list_icon color=”blue” type=”icon_arrow”]

  • Type a Name (usually 2-3 words) to identify your new workflow.
  • (Optional) Type a detailed Description of your new workflow.
  • Click the Add button. The workflow will open in edit mode, showing your new workflow containing a step called Open. If you are viewing your workflow inDiagram edit mode, you will see which has an incoming transition called Create.


2. Copy an existing workflow (useful if your new workflow can created by applying modifications to an existing workflow), by clicking the Copy link next to the existing workflow and in the resulting Copy Workflow dialog box:

[list_icon color=”blue” type=”icon_arrow”]

  • Type a Workflow Name (usually 2-3 words) to identify your new workflow.
  • (Optional) Type a detailed Description of your new workflow.
  • Click the Copy button. The workflow will open in edit mode, showing the layout of your copied workflow.


To access inactive workflows, click the Inactive list heading to expand the list of inactive workflows.

Once you have created your new workflow (especially if you created a ‘blank’ workflow) you may want to customise it by adding and/or editing steps and transitions as we discussed earlier.

When you have finished customising your new workflow it must be activated by following this steps:

[list_icon color=”blue” type=”icon_arrow”]

  • Create a workflow scheme that references your workflow and optionally associate it with the relevant issue type(s).
  • Associate the workflow scheme with the relevant project(s).




Enhanced by Zemanta

Protocon Convention 2013

Garden route mall George, 14-15 March

“The Garden Route is hosting the most unconventional convention for creators ever seen in our area on 14 and 15 March at the Garden Route Mall in George.

ProtoCon 2013 is all about getting creative thinkers together to learn about creativity techniques and idea development, rapid prototyping, technology to kick-start your concept development and even the legal pitfalls of coming up with the next big thing. We will have both local and national speakers sharing their experiences in an informal “jeans and tekkies” event that is sure to leave the delegates enlightened and inspired to take their ideas to the next level.”

Awesome Speakers – including us!

Marita Durr, creativity expert from the Kobus Neethling group will get the creative juices flowing with whole-brain creativity techniques that really work. Our very own Carli Bunding-Venter, Local Economic Development expert from the George Municipality will show you some of the greatest creative spaces in the world and why we believe the Garden Route is a fantastic place to start up an innovative business. Imel Rautenbach, chairman of the George Business Chamber and CEO of the Garden Route Technology Incubator will share his trials and tribulations on getting a new business off the ground and the support systems for entrepreneurs that can help. If you’re thinking of starting a new business in technology you don’t want to miss this.

If you’re the impatient kind when it comes to seeing results, Nathan Jeffery is your man. He will show you the tricks of the trade that puts the “rapid” in rapid prototyping. Expect to be amazed with what the world has to offer in terms of internet-based tools. Microsoft is uploading Tania van Wyk de Vries from Infoware Studios to us via the cloud to show you some tools and products that can kick-start your application development effort. Keep an eye out how the BizSpark program can launch your idea onto a global stage. Rudie Shepherd will bring you back to earth with a hard look at what corporates look for when they invest in your idea. If you like to get paid for work, listen to this. Advocate Liesl Briel will lay down the Cyber Law. No need to worry though… the only arresting thing will be the talk.

Being an unconventional convention, Dr. Ernst van Biljon will deliver the keynote address at the end and share his views on the process of taking a great idea global. If you don’t walk out inspired to go put a dent in the international economy you were either not listening or your idea really stinks!”

Awesome line-up

“Have you ever experienced a Hackathon before? It is when a bunch of talented people get together and intensely work on solving a common problem – and walk away with a working prototype. Well, at ProtoCon, YOU are those talented people and every delegate has the opportunity to join a ProtoThon team and work on some challenges laid down by the municipalities in the region.

Can you come up with a great way to save lives on our cycle and hiking trails? Do you have an idea how to make your neighbourhood safer using technology? Is it possible to live in Knysna, have an office in George and have your clients in Dubai – all using technology? Put your thinking cap on and come prototype with us and share in prize money of R50,000. All will be revealed in March.”


“ProtoCon is also a showcase for local talent and we want your business to exhibit your innovative and unconventional products and services to the public. We’re taking over the entire mall to give you a great opportunity to reach the thousands of shoppers with your idea at a very low cost. Don’t miss this opportunity!

Register today at !”


Enhanced by Zemanta
Page 4 of 6 «...23456