• tc-squared - A Linux-based open source "web-top" or "web thin client" that we use to create simple client devices to connect to web applications being developed in other projects.
• tagEventor - This is software that enables radically simple and intuitive "object based user interfaces" by enabling RFID tags to produce actions on a PC with an attached reader.
• Contributors: Mikael Örtenheim from Norway
• Contributors: Scott Greenlay from Canada
  
• autelicdemo - this is a Google App Engine application to demonstrate some of the photo aggregation & messaging and RFID-tag and touch-screen UI concepts proposed in our "aperture" project.
• double-clicker - this is a simple utility (for Windows at the moment) to help people who have difficulty with the double-click mouse action, by enabling combined mouse (for pointing) and keyboard (for clicking or selecting) use.
• Contributors: Josep-Maria Asensio from Spain
  

If after reading about them, and checking out each project´s Volunteer page you are ready to start contributing then contact us by e-mail at info@autelic.org.

To protect you and the Autelic Association we will ask you to submit either the Autelic Individual Contributor License Agreement, or if you are contributing on behalf of your company or contributing some existing software to submit the Autelic Software Grant and Corporate Contributor License Agreement. Both of these are modelled on the Apache2.0 contributor licenses.

Which license have we chosen and why?

The association is non-profit and our goal is not to make money out of community developed software. We want the solutions or services based on these developments to be deployed to end users by anyone offering a valuable service, for profit or not. So the software will be given freely, and available for commercial use.

If a company takes what´s developed here and offers a service that helps end users - great!  If the company provides enough value to charge end users for it, then fine.

We´d like companies to improve on what we provide, so we allow derived works. Ideally, we´d like to see back any additions and improvements made to the code by them, or for them to collaborate here on it´s development and maintenance. But we don´t want to oblige companies to share their own source code or otherwise scare them off from using these projects by forcing GPL licensing terms on them.

If a company makes money from these developments and wants to donate money or developer resources back to the projects that enabled that income, we´ll consider accepting that (within our stated goal, policies, bylaws, etc)

The most used open source license that meets our goals is the Apache license, so whenever possible we will license these projects under the Apache 2.0 License found on the Apache Foundation´s license page.