You are here

English

30-31 Mai 2015
ASEM Blocul F, Chisinau, Moldova

Workshop: Freelancers Unite! | Part 2

Sometimes freelancers must decline projects because they are fully booked, sometimes because they can not tackle them alone. And sometimes freelancers have a gap and could need one of the projects which others are just rejecting.

Many of this projects would not be lost if they were approached together. If we cooperate we can improve freelancing for all stakeholders including the customers.

Workshop: Freelancers Unite! | Part 1

Sometimes freelancers must decline projects because they are fully booked, sometimes because they can not tackle them alone. And sometimes freelancers have a gap and could need one of the projects which others are just rejecting.

Many of this projects would not be lost if they were approached together. If we cooperate we can improve freelancing for all stakeholders including the customers.

Danish Broadcast Corporation - case study.

The Danish Broadcast Corporation is the largest media content provider in Denmark. 85% of the danes tune in for their TV channels for an hour or more every week and their home on the web is by far the most visited danish website with millions of visits every week. In 2012 DBC decided to move their online content to Drupal. With 400 journalists writing articles, millions of nodes and millions of end users, Drupal have to perform to its utmost and the volume of the article production makes most workflow optimizations worthwhile.

The Drupal fever of the north

In Denmark the use of Drupal CMS exploded over the last 7 years. This session will be about why the danish companies started using Drupal a lot, what they use it for and the kind of large scale projects, that are being done and where we think the needs of the clients are headed in the future and some thoughts on what challenges Drupal will meet from the professional market in the future.

Multidimensional Testing Development Platform

Have you ever had a situation when developer with 100% confidence (works on my local) broken your master branch right before the release. We all were there. I know.

Would it be great to run tests on his changes before they get merged? Would it be nice to actually "test" as site with his changes being applied?

Lately we were improving process of github pull requests by using CI Jenkins to spin up separate environments per pull requests so QA can be done on each pull request before it gets merged.

We will talk about:

Pages