The Systems & Infrastructure Group is a subcommittee of Lamba Labs responsible for the management, implementation and support of the infrastructural operational systems at LLBH. The division was created on Thursday April 11th 2013. Although partially labeled IT Division the work of this group will branch more towards Software Development, Engineering and Research in all the major computation disciplines.
Currently LLBH necessitates 3 team members for this division's operation.
Members Holding The Positions:
The current strategy for the division is managing and overseeing the implementation of the plan detailed in the diagram (mind-map) below:
This process was initiated by determining the minimum specifications of a server depending on the needs of LLBH's online presence. After doing a brief market study and analysis of VPS providers we were able to specify the important criteria to look and direct our choice.
The data collected and choice of proper provider can be found in the following downloadable excel sheet. (Note: this brief study might become obsolete in the duration of months as the packages provided by the vendors vary frequently depending on the market demand).
The criteria that played the essential role in the decision making process were (by order of importance):
For months and since the inception of LLBH we have relied on Google Groups as the main system of communication. However after a while, this mailing list was heavily consumed by its members and the number of received emails per day was staggering. For this reason we decided as part of the new infrastructure to create Distribution Lists for specific Teams, Subcommittees and Project Leaders at LLBH.
The current mailserver in use is Postfix.
Here are the current Distribution Lists:
All hackerspaces need a realtime communication platform with minimal delay and lag. What's better than Internet Relay Chat ( IRC) to provide that?
We are currently present on the Freenode servers. Freenode is running by volunteers from the FOSS community and the server's philosophy meets our internal mission statement.
For total beginners you can use our WebClient (It's super easy).
Note: Virgil is currently the bot responsible for automating the maintenance of the channel.
Part of our mission is to contribute to the open source community. Keep an eye on our Github repository for the updated releases of our internal tools and public projects.
Like all hackerspaces the need to know if the space is open or closed is essential to members who don't have keys to access the space. So we created our own version of a space notification system that will indicate the status of the space.
More information can be found here: Space Status Tool