1 Departamento de Informatica, UTFSM. Agosto 2006 ACS Working Style Mauricio Araya: Team Leader ACS – UTFSM Team

1 Departamento de Informatica, UTFSM. Agosto 2006 Organization Hierarchy

1 Departamento de Informatica, UTFSM. Agosto 2006 Communication Methods Mailing Lists  General non ACS-specific Discussion  Official ACS-UTFSM list. English please!  Private ACS list for coordination purposes

1 Departamento de Informatica, UTFSM. Agosto 2006 Communication Methods General Meeting  Open to everyone  Its a duty only for: CSRG Team Leader ACS Team Leader OLPC Team Leader Sysadmin Project Responsibles Project Meeting  Defined by each Project Responsible

1 Departamento de Informatica, UTFSM. Agosto 2006 Communication Methods Twiki Page  General Discussion of the Group  News  ACS-UTFSM team news Discussion  Any topic about ACS or the working process Projects  Requirements, planning and results of each project

1 Departamento de Informatica, UTFSM. Agosto 2006 Twiki Specifics The Common Calendar (Important!) More collaboration => less documentation ACS twiki must be full written in English Its very easy to use, please do not be shine. Remember twiki includes a versioning sytem The authentication (user & pass) is with the Department Account

1 Departamento de Informatica, UTFSM. Agosto 2006 Account Each member has an “unlimited” home directory, for personal and working purposes The authentication (user & pass) is with the Department Account You have a personal page  Only if you need the root password, ask for it.

1 Departamento de Informatica, UTFSM. Agosto 2006 Documentation The official documentation guidelines are in:  This is only for deliverables; random documentation take place at the twiki The documentation must be revised by the Project Responsible, and released by the ACS Team Leader

1 Departamento de Informatica, UTFSM. Agosto 2006 Versioning System SVN is the main versioning system  GIT: Available for OLPC, can be used  CVS: Legacy support for CVS ACS software still use CVS The SVN repository is divided in:  Documentation Modules  Software Modules More information: 

1 Departamento de Informatica, UTFSM. Agosto 2006 Worklogs If the working time exceeds 30 minutes, a working log must be uploaded to the twiki. No formal or extensive documentation, just a simple log about your activities. If you are working in group, 1 worklog is enough Link the worklog to the project twiki page where you are working

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style Distribution: RedHat based distros  RedHat 9.0  RHEL  Fedora Core  CentOS  Scientific Linux

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style Languages  ACS is CORBA-based, so only O.O. Languages are supported C++ : Controlling, harware access, etc Java: GUI's and Web Python: Prototypes and Glue-Apps  IDL: Interface Data Language Common interfaces between languages  XML: eXtensible Markup Language Configuration Language (easy to parse)

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style ACS Installation  Main ACS directory: /alma/  Its almost a stand-alone framework Includes: gcc, tcltk, emacs, fileutils, binutils, python, etc Java: License problems, separate installation The CommonSoftware directory is where the real framework is  Its ment to run as a local user called: almamgr : Alma Manager Files belongs to this user, not root.

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style Environment  The environment variables are very important in ACS (old school style)  A simple script that setup all environmental stuff is located at $ACSROOT/config/.acs/.bash_profile.acs Where ACSROOT is a variable that contains the location of the current installation  Is highly recommended to put this script in your own.bashrc or.bash_profile

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style Directory Structures  MODROOT: standard directory structure to develop ACS software, includes Makefiles  INTROOT: Integration area, where the software can run without installing the components on /alma/ directory  AcsMakefile: a standard (and generic) Makefile, for all ACS purposes  This two directory structure and Makefile can be generated by the program getTemplate

1 Departamento de Informatica, UTFSM. Agosto 2006 MODROOT src is the directory where you will be putting the sources include is the directory where you will be putting the “.h” files lib is where the libraries get installed bin is where the binaries get installed idl is for the Interface Definition language files man is for the man pages object is where the dependencies files get installed doc is for the documentation generated with doxygen test is where the test source code has to be put

1 Departamento de Informatica, UTFSM. Agosto 2006 ACS working Style TATs  Every code must have a test sequence to be included on the ACS distribution  TAT means: Tools for Automated Testing  All projects on this Team should use this philosophy  The test-driven paradigm is optional

1 Departamento de Informatica, UTFSM. Agosto 2006 More information maray, nbarriga, ntroncos, raraya, msalgado, mmora, rtobar, HvB.