Committees are voluntary groups, formed by members in order to achieve certain goals.
To join this committee, contact the committee chairperson. See Rules and Policies#Committees for more information.
- 1 Charter
- 2 Policies
- 3 Jump Server
- 4 Telephone System
- 5 BoD Annual Election Procedures
- 6 Infrastructure
- 7 Governance Model
- 8 Contact
- 9 Members
- 10 Moderators
- 11 Meeting Minutes
- 12 How To Join
- 13 Service Level Agreement - Contents
Charter approved by BoD 2019-09-08
The Infrastructure Group performs operations and maintenance of Dallas Makerspace mechanical/electrical/plumbing (MEP), communications, online presence, and physical security.
Infrastructure Officer General Charter
The Infrastructure Officer shall be bound by the General Officer Charter.
The Infrastructure Group is headed by the Technology Officer, who may appoint or dismiss members without cause. The Technology Officer shall record and publically post the names of all members of the Infrastructure Group, noting changes in a timely fashion. The Infrastructure Group shall meet on an as-needed basis and report to the Board when requested by the Board.
The Technology Officer may delegate functions of the Office of the Technology Officer to member(s) of the Infrastructure Group as they deem necessary.
Responsibilities of the Office of the Technology Officer
- Facility MEP (Mechanical, Electrical, Plumbing)
- Compressed air
- Onsite Electronic Communications / information assets
- Onsite servers
- DMS-owned computers
- Online presence
- Website (infrastructure)
- Cloud infrastructure
- Internet access
- Physical security
- Access control
- Contracts related to Infrastructure
The Infrastructure Group shall have a monthly allocation specified by the Board of Directors. This shall be charged against the general fund; Infrastructure Group will retain no balance.
The Jump server hosts several virtual machines; including a Windows Server that hosts our VCarve, FeatureCAM, and AutoDesk Inventor software.
- This link provides information about storing and accessing computer files at DMS.
- Jump Server login (and creating AD account)
- Jump Server FAQ.
The phone system is a Voice over IP PBX, which consists of a virtual machine running Asterisk 11 with IncredibleGUI 12 on Ubuntu 14.04LTS. We use Google Voice for trunks, providing free calls to anywhere in the US or Canada. Our main number is 214-699-6537.
BoD Annual Election Procedures
Our Bylaws require an annual election of our BoD, the page in the link below details the procedures that were used in the most recent election. These procedures should be updated whenever a change is made.
- Freddy Calvert - Chief Technology Officer (@yashsedai)
- Stan Simmons
- Dwight Spencer (DevOps, IT, PM)
- Lisa Selk
- Andrew LeCody
- Alex Rhodes
- Bill Gee (@Bill)
- Robert Davidson
- Frank Lima
- Erik Smith
- Joe Helmstetter
- Mark Havens (Grand Master Computer Janitor)
- Jason Ottwell
- Mike Kelp (Code Wizard)
- john a. gorman (Senior IT Specialist)
- Stephenie Webb
- James Blocker
- Justin Edwards
- James Braye
- Woody (@woody)
- Jim Hartnett (@hon1nbo ; cybersecurity stickler)
- Kyle Crothers
The Infrastructure Committee sponsors a team (Moderator Team) to moderate the Talk Forum with a published set of moderator guidelines. The Moderator Team desires and promotes an open, transparent environment on Talk that promotes inclusion, diversity of opinions, knowledge sharing, fairness and respect while respecting privacy of all individuals.
The committee routinely meets on the second Wednesday of every month. Meetings will be posted on the calendar.
How To Join
- Send an email to [email protected] and request to join the Infrastructure committee.
- Add your name to the list of members on this page.
All pages related to the Infrastructure Committee.
Service Level Agreement - Contents
A Service Level Agreement typically contains the following information (actual contents may vary depending on the type of service):
The Service Level Agreement contains the contractually relevant data for an IT Service:
- Name of the IT Service
- Clearance information (with location and date)
- Service Level Manager
- Client representative
- Contact persons
- Name of the Service Provider
- Name of the Service recipient
- Contact partners/ persons in charge (on client-side as well as on the side of the IT Organization) for
- Contractual changes
- Complaints and suggestions
- Escalations in the case of contractual infringements
- Service reviews
- Contract duration
- Contract start
- Contract end
- Rules for changes to the SLA
- How are requests for change submitted (deletions, additions or changes to components of the SLA)?
- How are the requests for change and their implementation controlled?
- Who is responsible for the clearance of the changes?
- Rules for termination of the SLA
- Service description
- Short description of Service
- Users of the IT Service on the client-side
- Breakdown of the offered Service into Service groups, e.g. along infrastructure components or IT applications
- For each Service group:
- Which Services are offered, e.g.
- Handling of Service interruptions (by telephone, by remote access, on site?)
- User Services (user administration, installation, …)
- What quality is required of the offered Services, e.g.
- Service times
- Availability requirements
- Number of interruptions allowed
- Availability thresholds (xx,xx %)
- Downtimes for maintenance (number of allowed downtimes, pre-notification periods)
- Procedure for announcing interruptions to the Service (planned/ unplanned)
- Performance requirements
- Required capacity (lower/upper limit) for the Service
- Allowed workload/ usage of the Service
- Response times from applications
- Reaction and resolution times (according to priorities, definition of priorities e.g. for the classification of Incidents)
- Requirements for the maintenance of the Service in the event of a disaster
- Which Services are offered, e.g.
- Relations to other IT Services
- Procedures for requesting the IT Service
- Requests possible by telephone/fax/mail, ... (addresses, telephone numbers, etc.)
- Of the client (also within the field of IT Security)
- Responsibilities and liability of the IT Organization
- Quality assurance and Service Level Reporting
- Measurement procedures
- Which indicators
- With which measurement procedures
- At which intervals
- Collated into which reports
- SLA Reviews
- Intervals at which SLA reviews are to be held
- Measurement procedures
- Service accounting
- Costs for the provision of the Service
- Accounting method for the Service
- Intervals for invoicing