Hallway Tech is pleased to share that one of our community contributions is becoming part of the core Sakai CLE project.

In August 2011, the Sakai 2 Technical Coordination Committee (TCC) succeeded in passing a vote to include Mail Sender as a core tool in the Sakai CLE 2.9 release. Mail Sender began as a Georgia Tech contrib project to refine the user interface and functionality of Mailtool.

Carl Hall of Hallway Tech and Seth Theriault of Columbia University have been maintaining Mail Sender for last two years and the project has enjoyed continued improvements in quality and new features with two releases, 1.6.4 and 1.7.0, slated for November.

Hallway Technologies is pleased to announce the addition of Brian Young to our development team. Brian comes to Hallway Tech with a ten-year history in UI design and client/server software.

Brian will be leading all UI efforts and driving forward Hallway Technologies’ Drupal based projects. We are delighted to have yet another well-rounded, cross-trained developer on board.

Welcome Brian!

Hallway Tech is proud to announce that our co-owner and lead architect Carl Hall has been named a 2011 Sakai Fellow. 

Sakai Fellows are selected by a small committee for their special volunteer service to the Sakai community. 

We are thrilled to have one of our own singled out for this honor and look forward to celebrating with our friends at Sakai Conference 2011 in Los Angeles.

You can read more about the Sakai Fellow's program on the Sakai Community website.

Hallway Technologies is pleased to announce that our own Carl Hall has accepted an invitation from the Apache Sling PMC to be named a committer on the Apache Sling project. The Sling project is a foundation of the Sakai OAE framework.

Sling in a hundred words from the Sling website:

Apache Sling is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content.

Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.

The embedded Apache Felix OSGi framework and console provide a dynamic runtime environment, where code and content bundles can be loaded, unloaded and reconfigured at runtime.

OSGi has a fantastic feature for immediate components ^[1] and delayed components ^[2]. This allows components to delay their possibly expensive activation until the component is first accessed. At the very least it allows the OSGi platform to consume resources as needed. No sense is sucking up those server resources for something that can wait.