DrupalCon News: Three Reasons to Send Your Team to DrupalCon

Planet Drupal - Wed, 18/03/2015 - 15:34

It can be difficult to decide whether to send representatives of your organization to DrupalCon. You may find yourself asking questions like, what's the ROI? What’s the value of being there in person? Is it really worth the money? There are tremendous benefits, measurable and immeasurable, to sending your employees to DrupalCon. Here are three reasons why going is a win-win for both your employees and your organization.

Categories: Elsewhere

Mario Lang: Call for Help: BMC -- Braille Music Compiler

Planet Debian - Wed, 18/03/2015 - 15:10

Since 2009, I am persuing a personal programming project. As I am not a professional programmer, I have spent quite a lot of that time exploring options. I have thrown out about three or four prototype implementations already. My last implementation seems to contain enough accumulated wisdom to be actually useful. I am far from finished, but the path I am walking now seems relatively sound.

So, what is this project about? I have set myself a rather ambitious goal: I am trying to implement a two-way bridge between visual music notation and braille music code. It is called BMC (Braille Music Compiler).

My problem: I am, as some of you might remember, 100% blind. So I am trying to write a translator between something I will never see directly, and its counterpart representation in a tactile encoding I had to learn from scratch to be able to work on this project. Braille music code is probably the most cryptic thing I have ever tried to learn. It basically is a method to represent a 2-dimensional structure like staff-notation as a stream of characters encoded in 6-dot braille.

As the goal above states, I am ultimately trying to implement a converter that works both ways. One of my prototypes already implemented reading digital staff notation (MusicXML) and transcribing it to Braille. However, to be able to actually understand all the concepts involved, I ended up starting from the other end of the spectrum with my new implementation: parsing braille music code and emitting digital staff notation (LilyPond and MusicXML). This is a rather unique feature, since while there is commercial (and very expensive) software out there to convert MusicXML to braille music code, there is, as far as I know, no system that allows to input un-annotated braille music code and have it automatically converted to sighted music notation.

So the current state of things is, that we are able to read certain braille music code formats, and output either reformatted (to new line-width) braille music code, LilyPond or MusicXML.

The ultimate goal is to also implement a MusicXML reader, and convert the data to something that can be output as braille music code.

While the initial description might not sound very hard, there are a lot of complications arising from how braille music code works, which make this quite a programming challenge. For one, braille music note and rest values are ambigious. A braille music note or rest that looks like a whole can mean a whole or 16th. A braille music note or rest that looks like a half can mean a half or a 32nd. And so on. So each braille music code value can have two meanings. The actual value can be caluclated with a recursive algorithm that I have worked out from scratch over the years. The original implementation was inspired by Samuel Thibault (thanks!) and has since then evolved into something that does what we need, while trying to do that very fast. Most input documents can be processed in almost no time, however, time signatures with a value > 1 (such as 12/8) tend to make the number of possible choices exploed quite heavily. I have found so far one piece from J.S. Bach (BWV988 Variation 3) which takes about 1.5s on my 3GHz AMD (and the code is already using several CPU cores).

Additionally, braille music code supports a form of "micro"-repetitions which are not present in visual staff notation which effectively allow certain musical patterns to be compressed if represented in braille.

Another algorithmically interesting part of BMC that I have started to taclke just recently is the linebreaking problem. Braille music code has some peculiar rules when it comes to breaking a measure of musical material into several lines. I ended up adapting Donald E. Knuth's algorithm from Breaking Paragraphs into Lines for fixed-width text. In other words, I am ignoring the stretch/shrink factors, while making use of different penalty values to find the perfect solution for the problem of breaking a paragraph of braille music code into several lines.

One thing that I have learnt from my perivous prototype (which was apparently useful enough to already acquire some users) is that it is not enough to just transcribe one format to another. I ultimately want to store meta information about the braille that is presented to the user such that I can implement interactive querying and editing features. Braille music code is complicated, and one of the original motivations to work on software to deal with it was to ease the learning curve. A user of BMC should be able to ask the system for a description of a character at a certain position. The user interface (not implemented yet) should allow to play a certain note interactively, or play the measure under the cursor, or play the whole document, and if possible, have the cursor scroll along while playback plays notes. These features are not implemented in BMC yet, but they have been impleemnted in the previous prototype and their usefulness is apparent. Also, when viewing a MusicXML document in braille music code, certain non-structural changes like adding/removing fingering annotations should be possible while preserving unhandled features of the original MusicXML document. This also has been implemented in the previous prototype, and is a goal for BMC.

I need your help

The reason why I am explaining all of this here is that I need your help for this project to succeed. Helping the blind to more easily work with traditional music notation is a worthwhile goal to persue. There is no free system around that really tries to adhere to the braille music code standard, and aims to cover converting both ways. I have reached a level of conformance that surpasses every implementation of the same problem that I have seen so far on the net.

However, the primary audience of this software is going to be using Windows. We desperately need a port to that OS, and a user interface resembling NotePad with a lot fewer menu entires. We also need a GTK interface that does the same thing on Linux. wxWindows is unfortunately out of question, since it does not provide the same level of Accessibility on all the platforms it supports. Ideally, we'd also have a Cocoa interface for OS X. I am afraid there is no platform independent GUI framework that offers the same level of Accessibility on all supported platforms. And since much of our audience is going to rely on working Accessibility, it looks like we need to implement three user interfaces to achieve this goal :-(.

I also desperately need code reviews and inspiration from fellow programmers. BMC is a C++11 project heavily making use of Boost. If you are into one of these things, please give it a whirl, and emit pull requests, no matter how small they are. While I have learnt a lot in the last years, I am sure there are many places that could use some fresh winds of thought by people that are not me. I am suffering from what I call "the lone coder syndrome".

I also need (technical) writers to help me complete the pieces of documentation that are already lying around. I have started to write a braille music tutorial based on the underlying capabilities of BMC. In other words, the tutorial includes examples which are being typeset in braille and staff notation, using LilyPond as a rendering engine. However, something like a user manual is missing, basically, because the user interface is missing. BMC is currently "just" a command-line tool (well enough for me) that transcribes input files to STDOUT. This is very good for testing the backend, which is all that has been important to me in the last years. However, BMC has reached a stage now where its functionality is likely useful enough to be exposed to users. While I try to improve things steadily as I can, I realize that I really need to put out this call for help to make any useful progress in a foreseeable time.

If you think it is a worthwhile goal to help the blind to more easily work with music notation, and also enable communication between blind and sighted musicians in both ways, please take the time and consider how you could help this project to advance. My email address can be found on my GitHub page. Oh, and while you are over at GitHub, make sure to star BMC if you think it is a nice project.

It would be nice if we could produce a end-user oriented release before the end of this year.

Categories: Elsewhere

Drupal governance announcements: Proposal: Changes to the project application review process

Planet Drupal - Wed, 18/03/2015 - 13:43

For the past few months, members of the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers have been working on proposed changes to the project application review process.

The proposed changes have been posted for public review. https://www.drupal.org/node/2453587

If you have any comments or questions, please add them to the issue. This proposal is open for feedback until the end of March. We will then incorporate the feedback and start working on implementing these changes.

Categories: Elsewhere

DebConf team: DebConf15 Call for Proposals (Posted by Michael Banck)

Planet Debian - Wed, 18/03/2015 - 12:00

We’re now calling for proposals for DebConf15. Proposals are accepted from now until 15 June 2015. To submit an event, go to the Propose an Event page once you are registered for the conference.

The DebConf Content Team will decide on a first round of submissions in May, so be sure to submit your proposal soon if you need it to be accepted by then, e.g. for sponsorship requests.

The current, non-exhaustive list of proposed topics is:

  • Debian Packaging, Policy, and Infrastructure
  • Security, Safety, and Hacking
  • Debian System Administration, Automation and Orchestration
  • Containers and Cloud Computing with Debian
  • Debian Success Stories
  • Debian in the Social, Ethical, Legal, and Political Context
  • Blends, Subprojects, Derivatives, and Projects using Debian
  • Embedded Debian and Hardware-Level Systems

For all further information, please see the Proposals page of the DebConf15 website.

Categories: Elsewhere

PreviousNext: To Alter or Dispatch: Drupal 8 Events versus Alter Hooks

Planet Drupal - Tue, 17/03/2015 - 22:46

Drupal 8 comes with two extension points for module developers to allow other modules to interact with their code.

The trusty alter hook, the linchpin of Drupal versions past is still there - allowing other modules to interact and intervene in the behaviour of your module.

But there is a new kid on the block, the event system.

So as a module developer how do you decide whether to use the alter system or the event system.

Categories: Elsewhere

Drupal Association News: Calling all Community Organizers

Planet Drupal - Tue, 17/03/2015 - 21:39

Do you plan meet-ups, camps, sprints, or trainings for your local community?  The Drupal Association is creating a new Community Organizer Newsletter, so be sure to sign up on your Drupal.org profile. Read on to find out more!

This past January, I celebrated my one-year anniversary of employment at the Drupal Association. I came to the Association from a community management background, working with multiple stakeholders in a distributed community; the role as Community Outreach Coordinator itself appealed to me because I knew the Association serves a strong, active, and connected community. I thought that the community aspect of my job would be nothing I hadn’t encountered before, as I knew I’d be working with very similar community models.  What I did not know at the time was the astonishing amount of effort that our volunteers put in to better their local communities and therefore enhance a global community.

Over the past year, I’ve been fortunate enough to visit several camps, attend and participate in planning DrupalCons, sit in on Community Summits, and have countless interactions with volunteers from around the world.  One thing that has resonated with me as I started to connect to volunteers globally is that many community organizers often ask similar questions about other communities and volunteers.  What are others doing for camps? What are others doing for hosting a sprint? Do others struggle to get people to meetups? How do we engage new leadership? Does the Drupal Association have resources to support our local community groups and user groups?

The frequency with which I have encountered these questions got me thinking: how do we highlight the efforts of our volunteers and share best practices with everyone.  After all, we’re open source, and sharing is how we do things. We’re a do-ocracy! After a lot of thought, I realized that the best way to accomplish this task will have to be collaborative. 

I’ll be working with our talented staff at the Association and volunteers to create a quarterly Drupal Community Organizers Newsletter full of tips, tricks, and news for anyone who runs, organizes, or wants to help grow their local community. The best part is that this newsletter will be mostly curated content from you all, our organizers! Who better to help others than our troops in the trenches? I’ll be including blogs, upcoming camps and sprints, best practices, highlights from communities, volunteer recognition and more information. 

I anticipate that we will release the first issue in the beginning of April, at the start of this year’s Second Quarter. As part of this effort, I need your help. Would you like to receive the newsletter? Sign up HERE , and contact me HERE if you have content (or know of content) that would be great to share with our community organizers. Know other community organizers? Spread the word and get them on the list! Let’s work together to share and support each other in our global Drupal Community.

Categories: Elsewhere

Mediacurrent: Mediacurrent Dropcast: Episode 2

Planet Drupal - Tue, 17/03/2015 - 21:17

No Bob this week but we soldier on in this week's episode.

Your browser does not support the audio element.
Episode 2 Audio Download Link


Categories: Elsewhere

VM(doh): Drupal Module Marconi Renamed to Openstack Queues

Planet Drupal - Tue, 17/03/2015 - 21:08

When originally building the Marconi module, I did not realize that Openstack project names change. Most recently, the name of the queue project in Openstack was renamed to Zaqar. To avoid further renaming issues, I have renamed the Drupal module to Openstack Queues.

Openstack Zaqar provides a queuing service similar to Amazon SQS for Openstack-based providers. It is currently known to be running in production at Rackspace. This site as well as several sites that we host currently use the Openstack Queues module.

The Openstack Queues module allows Drupal to use Openstack Zaqar as a queue backend.

Categories: Elsewhere

Commerce Guys: The Revolution in eCommerce

Planet Drupal - Tue, 17/03/2015 - 18:53

You know It's coming - you can feel it, hear it, and see it - the low but powerful rumbling of change - the next big wave of innovation in ecommerce.

Buying and selling online has become second nature and a core part of our lives - yet there is fundamental change underway in how people are thinking about ecommerce and how transactions of all kinds should be woven into the fabric of an engaging online user experience.

Content Sells

The importance of content in creating online experiences that drive people to buy is becoming increasingly important to online merchants and brands. Is there any doubt that this next wave of innovation will in part be centered around a more fluid content driven commerce experience?

Companies who are using a traditional catalog based ecommerce solution are realizing the importance of content to online revenue growth and that simply integrating their ecommerce solution with a separate CMS solution is ultimately not a great solution and creates unnecessary complexity. As a result, many companies with mature online revenue channels are beginning to define their next generation systems.

Ingredients of a Revolution

Fundamental change and a common vision are key ingredients for any Revolution. Mix in a large and growing community of stakeholders who all stand to benefit from this change and you begin to see momentum shift.

But it all starts with needs that are not being met.

Talk to anyone who has been using or delivering ecommerce solutions over the past view years and you will hear a discontent with their current system and in general the future of ecommerce.

What is the source of this discontent and what do they want their ecommerce solution to do that it isn't doing now? Here is what we hear.

  • My current ecommerce solution doesn't provide me with powerful enough CMS functionality to deliver the type of experience that I need to attract and keep users on my site.
  • I have too many systems to manage and maintain - one for content, one for online transactions, one for orders, fulfillment, and inventory and it's hard to integrate them and expensive to support - and even harder to create a unified experience for my users.
  • I need to be much more agile and timely in adapting to changes in the market and responding to the changing behavior of my customers. My technology needs to support this iterative approach that is critical for my business.
  • Technology is way too complex so I really would like a service that insulates me from the complexities of technology so that I can focus on my business - BUT - I don't want to sacrifice flexibility and control over the functionality my business needs and I CAN'T be locked into a single vendor who doesn't have my interests in mind.
  • I need ecommerce functionality that is more modular - rather than an all-in-one solution that resides in a large and separate codebase - so that I have greater flexibility in how and where commerce exists on my site.
Drupal + Drupal Commerce

While Drupal + Drupal Commerce won't solve all of your problems, it will address many of these fundamental challenges, and it will solve them far better than most ecommerce solutions today.

Why? Because it is built, supported, and extended on a massive scale by the largest open source community to address the needs of users just like you.

Join the Revolution

Want to be part of this change? Join us for the first Commerce Revolution on Monday afternoon, May 11 right before the start of DrupalCon Los Angeles. This is a great opportunity to learn, engage, and hear how customers, integrators, and agencies are addressing the shifing needs in ecommerce with Drupal + Drupal Commerce. This is an exclusive, invitation only event. If you would like to receive more information when we officially announce the Commerce Revolution on March 30, please let us know by completing the form below.

Categories: Elsewhere

Raphaël Hertzog: Freexian’s report about Debian Long Term Support, February 2015

Planet Debian - Tue, 17/03/2015 - 17:42

Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In February, 58 work hours have been equally split among 4 paid contributors. Their reports are available:

Evolution of the situation

During the last month, we gained 3 paid work hours: we’re now at 61 hours per month sponsored by 28 organizations and we have one supplementary sponsor in the pipe that should bring 4 more hours.

The increase is not very quick but seems to be steady. Hopefully at some point, we will have enough resources to do a more exhaustive job. For now, the paid contributors handle in priority the most popular packages used by the sponsors and there are some packages in the end of the queue which have open security issues for months already (example: CVE-2012-6685 on libnokogiri-ruby).

So, as usual, we are looking for more sponsors.

In terms of security updates waiting to be handled, the situation looks a little bit worse than last month: the dla-needed.txt file lists 40 packages awaiting an update (3 more than last month), the list of open vulnerabilities in Squeeze shows about 58 affected packages in total (5 less than last month). We are getting a bit more effective with CVE triage.

A logo for the LTS project?

Every time that I write an LTS report, I remember that it would be nice if my LTS related articles could feature a nice picture/logo that reminds people of the LTS team/initiative. Is there anyone up for the challenge of creating that logo?

Thanks to our sponsors

The new sponsors of the month are in bold.

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

Categories: Elsewhere

Drupalize.Me: Dependency Injection with Traits in Drupal 8

Planet Drupal - Tue, 17/03/2015 - 14:04

Part of learning Drupal’s API is learning about “what’s in the pantry.” In Drupal 8, that pantry is configured quite a bit differently than before. Instead of getting the whole warehouse of Drupal functions on every page load, functions—well, now methods—are contained in objects which are defined by classes. Most, if not all, of these classes, which exist in their own PHP files, can be extended and many of them are specifically designed to be extended. These extensible classes are the pantries. They contain properties and methods that we can just use in the classes that extend them. When we extend these classes, we need to make sure we peek inside to see what’s available before we go elsewhere for something that might already be in the cupboard.

Categories: Elsewhere

ComputerMinds.co.uk: Drupal Queues

Planet Drupal - Tue, 17/03/2015 - 14:00

Queues are a wonderful way of separating different parts of a system. Once you have separated those parts you can do lots of interesting things, like be more fault tolerant or have a more responsive front end for your users.

For example, lets suppose that we have a website on which we can book a holiday. We can choose lots of different options and at the end of the process when we've booked the holiday we'd like to send the customer a nice PDF detailing all the options they've chosen.

Categories: Elsewhere

ComputerMinds.co.uk: Drupal Queues

Planet Drupal - Tue, 17/03/2015 - 14:00

Queues are a wonderful way of separating different parts of a system. Once you have separated those parts you can do lots of interesting things, like be more fault tolerant or have a more responsive front end for your users.

For example, lets suppose that we have a website on which we can book a holiday. We can choose lots of different options and at the end of the process when we've booked the holiday we'd like to send the customer a nice PDF detailing all the options they've chosen.

Categories: Elsewhere

Wunderkraut blog: A Medium like editor for Drupal 8

Planet Drupal - Tue, 17/03/2015 - 11:11

Ok, so now we have a wyysiwyg-editor in drupal 8 core, but if you want another editor, like something used on medium.com?

I have done som intial work to get the medium clone inside drupal 8, and have now setup a sandbox on d.o. Please test it out if you are interested. The further plan of the module is to get a working media solution working with it, and if you are skilled on js (I am not :-)), and you feel you want to contribute... 

Sandbox is over here: https://www.drupal.org/sandbox/mikkex/2453725

Categories: Elsewhere

Appnovation Technologies: BDD with Behat and Drupal

Planet Drupal - Tue, 17/03/2015 - 01:20

As a back-end developer, I had the chance to work on a project which required writing automated tests for a Drupal site using Behat.

Categories: Elsewhere

Daniel Kahn Gillmor: Bootable grub USB stick (EFI and BIOS for Intel)

Planet Debian - Tue, 17/03/2015 - 00:12

I'm using grub version 2.02~beta2-2.

I want to make a USB stick that's capable of booting Intel architecture EFI machines, both 64-bit (x86_64) and 32-bit (ia32). I'm starting from a USB stick which is attached to a running debian system as /dev/sdX. I have nothing that i care about on that USB stick, and all data on it will be destroyed by this process.

I'm also going to try to make it bootable for traditional Intel BIOS machines, since that seems handy.

I'm documenting what I did here, in case it's useful to other people.

Set up the USB stick's partition table:

parted /dev/sdX -- mktable gpt parted /dev/sdX -- mkpart biosgrub fat32 1MiB 4MiB parted /dev/sdX -- mkpart efi fat32 4MiB -1 parted /dev/sdX -- set 1 bios_grub on parted /dev/sdX -- set 2 esp on After this, my 1GiB USB stick looks like: 0 root@foo:~# parted /dev/sdX -- print Model: USB FLASH DRIVE (scsi) Disk /dev/sdX: 1032MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 4194kB 3146kB fat32 biosgrub bios_grub 2 4194kB 1031MB 1027MB efi boot, esp 0 root@foo:~# make a filesystem and mount it temporarily at /mnt: mkfs -t vfat -n GRUB /dev/sdX2 mount /dev/sdX2 /mnt ensure we have the binaries needed, and add three grub targets for the different platforms: apt install grub-efi-ia32-bin grub-efi-amd64-bin grub-pc-bin grub2-common grub-install --removable --no-nvram --no-uefi-secure-boot \ --efi-directory=/mnt --boot-directory=/mnt \ --target=i386-efi grub-install --removable --no-nvram --no-uefi-secure-boot \ --efi-directory=/mnt --boot-directory=/mnt \ --target=x86_64-efi grub-install --removable --boot-directory=/mnt \ --target=i386-pc /dev/sdX At this point, you should add anything else you want to /mnt here! For example: And don't forget to cleanup: umount /mnt sync

Tags: bios, efi, grub, tip

Categories: Elsewhere

Bits from Debian: Debian is now welcoming applicants for Outreachy and GSoC Summer 2015

Planet Debian - Mon, 16/03/2015 - 21:45

We'd like to reshare a post from Nicolas Dandrimont.

Hi all,

I am delighted to announce that Debian will be participating in the next round of Outreachy and GSoC, and that we are currently welcoming applications!

Outreachy helps people from groups underrepresented in free and open source software get involved. The current round of internships is open to women (cis and trans), trans men, genderqueer people, and all participants of the Ascend Project regardless of gender.

Google Summer of Code is a global program, sponsored by Google, that offers post-secondary student developers ages 18 and older stipends to write code for various open source software projects.

Interns for both programs are granted a $5500 stipend (in three installments) allowing them to dedicate their summer to working full-time on Debian.

Our amazing team of mentors has listed their project ideas on the Debian wiki, and we are now welcoming applicants for both programs.

If you want to apply for an internship with Debian this summer, please fill out the template for either Outreachy or GSoC. If you’re eligible to both programs, we’ll encourage you to apply to both (using the same application), as Debian only has funds for a single Outreachy intern this round.

Don’t wait up! The application period for Outreachy ends March 24th, and the GSoC application period ends March 27th. We really want applicants to start contributing to their project before making our selection, so that mentors can get a feel of how working with their intern will be like for three months. The small task is a requirement for Outreachy, and we’re strongly encouraging GSoC applicants to abide by that rule too. To contribute in the best conditions, you shouldn’t wait for the last minute to apply :-)

I hope we’ll work with a lot of great interns this summer. If you think you’re up for the challenge, it’s time to apply! If you have any doubts, or any question, drop us a line on the soc-coordination mailing list or come by on our IRC channel (#debian-soc on irc.debian.org) and we’ll do our best to guide you.

Categories: Elsewhere

Enrico Zini: screen-dependent-geometry

Planet Debian - Mon, 16/03/2015 - 21:29
Screen-dependent window geometry

I have an external monitor for my laptop in my work desk at home, and when I work I keep a few windows like IRC on my laptop screen, and everything else on the external monitor. Then maybe I transfer on the sofa to watch a movie or in the kitchen to cook, and I unplug from the external monitor to bring the laptop with me. Then maybe I go back to the external monitor to resume working.

The result of this (with openbox) is that when I disconnect the external monitor all the windows on my external monitor get moved to the right edge of the laptop monitor, and when I reconnect the external monitor I need to rearrange them all again.

I would like to implement something that does the following:

  1. it keeps a dictionary mapping screen geometry to window geometries
  2. every time a window geometry and virtual desktop number changes, it gets recorded in the hash for the current screen geometry
  3. every time the screen geometry changes, for each window, if there was a saved window geometry + wirtual desktop number for it for the new screen geometry, it gets restored.


  1. Is anything like this already implemented? Where?
  2. If not, what would be a convenient way to implement it myself, ideally in a wmctrl-like way that does not depend on a specific WM?

Note: I am not interested in switching to a different WM unless it is openbox with this feature implemented in it.

Categories: Elsewhere

Phase2: Announcing New Release and Version Scheme For Open Atrium

Planet Drupal - Mon, 16/03/2015 - 21:17

For the last several months I’ve had the privilege of leading the new dedicated products team here at Phase2. Having a team solely focused on products does not mean we are shifting away from Open Source, but it does mean we are going to be changing our practices a bit to better support the community and our clients. We now have a more predictable development schedule for our products like Open Atrium, and we want to pass the benefits of that to the community and our clients. To that end, we will be working on regular releases with a more consistent version scheme.

Releases will have the following types:
  • Maintenance Releases –  these will happen regularly (approximately once a month) and will include bug fixes, security patches and minor feature improvements/tweaks. We’ll signal these with version numbers that end in 1-9 (e.g. the “1” in Open Atrium 2.31).

  • Feature Releases – these will happen once a quarter and will add major new functions. They will generally require a little more care in upgrade because they may include big updates. These releases will end in zero, like our recent Open Atrium 2.30 release.

  • Major Releases – we have big ideas and plans, and some of them will require that we break compatibility and/or force a migration. We will be working on these big ideas, and we’re aiming to have a new major release each year. Our next will be Open Atrium 3.0 in early 2016.

As we build our solutions, we want to be able to move fast and make lots of improvements, but we need to balance that with a strong testing/review cycle. Rather than keep our activities behind the curtain, we will still be working in public git repositories so that anyone can see where we are going. And, for folks that do not want to follow the day-to-day of development but want to be more involved, we’ll be following a release candidate strategy. Before new feature releases, as soon as we feel we’re feature complete, we’ll publish a release candidate (e.g. 2.30-rc1). We’ll then put the RC through its paces and if things go well and we get no reports of issues from the community, that will become the final release.

So, future releases will have versions that look like this:

By both developing in the open and putting our releases out for review before they are final, we hope to strike the right balance between being visible and collaborative in the community, and offering our clients access to well reviewed and tested releases. As we work to bring more solutions to market, rest assured that we’ll keep “open” as a strong part of our DNA.

Personally, I’m really excited to be working with a great group of folks, both on my team and in the community. Lets push it, and do something great together! If you would like to stay informed about Open Atrium developments, be sure to sign up for the Phase2 newsletter!

Categories: Elsewhere


Subscribe to jfhovinne aggregator - Elsewhere