Techlahoma Software Lifecycle and Governance

Software Developed and Maintained by Techlahoma

The board may vote to officially support the development and maintenance of various software projects. For each project maintained by Techlahoma, the board will recognize a project lead from among the volunteers for the project, and optionally additional developers who will be responsible for development and maintenance of the software. These individuals will also be responsible for addressing / managing reported issues for their sponsored project.

If at any time the board cannot find volunteers to maintain a project, they should take steps to recruit a maintainer, allocate funds to hire a contractor to maintain the project, or they may vote to close the project.

Software Deployed and Supported by Techlahoma

For all software projects deployed and maintained by Techlahoma, the board will vote annually to continue investing in them, or expire the project. The purpose of this review is to ensure that neglected and unused projects do not continue running, costing money, and possibly exposing vulnerabilities.

For projects deployed and maintained by Techlahoma, the board will recognize a deployment lead from among the volunteers for the project, and optionally additional developers who will be responsible for maintenance, security, appropriate content, and error awareness of the deployment.

If at any time the board cannot find volunteers to maintain a deployment, they should take steps to recruit a maintainer, allocate funds to hire a contractor to maintain the project, or they may vote to close the project and/or find a 3rd party service as a replacement.

When considering projects for deployment and support by Techlahoma volunteers, the board should take into consideration the criticality of that piece of infrastructure and how that relates to the nature of volunteer work. By relying on volunteers to maintain and support live software deployments, the board acknowledges that the volunteers will often have other responsibilities that may preclude them from responding to incidents as quickly as might be expected from a 3rd party vendor. The more contributors per project the better.

Hosting and Vendors

To address the security and accessibility of Techlahoma projects, each project should default to being deployed to heroku, github pages, or S3. The board should vote when a project needs to go to a vps/server or other deployment service and make sure a plan is in place with regards to the monitoring, security, key management, and accessibility of that infrastructure.

Existing Software Projects:

• techlahoma.org
• us.techlahoma.org (blog roll, etc)
• donate.techlahoma.org
• php job board ???

Individual user group sites/projects are not automatically considered as officially supported by Techlahoma itself. The board may vote to assume responsibility for any such projects at their discretion.

Will the 2023/2024 notes be added here or are they hosted somewhere else?

https://zapier.com/engine/hydrate/1571375/.eJxVj09rg0AUxL9K2ENPEmNTaxRC8ZBSmpZWaA71IsvuUxf3j919iykh372rOfX0YObNj5kLYUYjaGzwdwRSkJJERGiHVDNoBCfFdpNnebpLIsK8Q6O8A7sYSZol2yyNCGXM-ED4J7YCJG80VTO0FRICd5io7RwpLsRbGeQecXRFHHPD3LozppOwZkbFLQB3QZ20NJTPtlehoovhPBqL8WE5T4LvEzEcZVkffx7Z5r4_fZ4O35OrhrTsyrp-qPqX6c2y1_Qjq_Ld3S39bKyiuA_Qc6iEAuUyuwPN6YpqvnoX2iO41ReoUVKci7dLJrwtqev1D7L5aQY:1n5DJb:d5IU3TeOj56hrflrISo5FDpMI0s/

Acquire Directors and Officers insurance and Employment Practices Liability insurance. This issue is to approve purchase of a policy that is nearly identical to the attached quote, Option 2, with 1 change: The maximum benefit is $2M, with a maximum benefit of $1M per claim.

Is this from the future/potential Innovation District meeting or did Tommy say that he found a new place? Also, what about adding on RaiseMore's new location?

Hey y'all, it's tax time again 💸 That means we need an average of how many hours you spent each week doing work for your position in Techlahoma throughout 2017. Reminder: this only applies to folks who officially served on the board or as officers in 2017.

Please estimate the amount of time you devoted to your position each week and post it in here by Monday, March 19, 2018. If you have questions hmu here/slack or ask Vance.

CC: @vlucas @DevinClark @jagthedrummer @groovecoder @Blazedd @the-simian @seejessicacode @amandaharlin @robolucas @tk2u @TRozzell @dustincurzon @aestus @matthewreily

Acquire Directors and Officers insurance and Employment Practices Liability insurance. This issue is to approve purchase according to the attached quote, Option 1

Sliding Scale:

• Growing (2-15 members) $4/person

  • OKC PHP
  • TULSA GAME DEVS
  • Code for Muskogee

• Established (15-50 members) $4.50/person

• Flourishing (50+ members) $6/person

  • OKCFP
  • OKCJS
  • TULSA web devs
  • TULSA UX

• UG you buy the food

• sends us a receipt, or email github it.

• post picture on meetup

• read the script

• post an accurate description and encourage attendance on meetup

• treasurer uses bank rule to associate name with account.

Can we invite another Tulsa tech community leader to the January meeting? I added a bunch of 200 OK organizers to the Slack team, but I'd like to get more Tulsa perspective into the meetings - I don't feel like I can adequately represent everything that's going on in Tulsa tech community.

This can be subject to amendment based on board majority, if we learn new ways to properly run the slack channels

1. Members violating the CoC are subject to being banned. All activity in Slack channels must conform to the agreed upon CoC that all usergroups and events follow. This includes non harassment policy.
2. No Solicitation Policy.
   The Slack forums are a way to conduct usergroup and developer activity in Oklahoma. It is not a place to post jobs, sell goods or otherwise conduct for-profit business in the virtual space. Infraction results in a warning first, and then a ban. This extends to public channels, private channels and private messages.

I purchased a really nice indesign template and i've been working on a trifold brochure for thunder plains - so we can promote techlahoma and share the good stuff that we do for the community. if anyone wants to give some feedback on data used in the brochure (like "yes, include 2014 data" or "no, use 2015 data only", etc) - that'd be very much appreciated too.

I didn't finish this for tonight, so there won't be signatures needed. Ryan Hoegg is helping with the bylaws though, and possibly taking over this task, so if you are interested in helping sort through the 23 pages we've got as a template - please let him or myself know

Right now this repo is controlled by the "Core Owners" team of the Techlahoma GitHub org. We should change it to the Board of Directors team?

Acquire Directors and Officers insurance and Employment Practices Liability insurance. This issue is to approve purchase according to the attached quote, Option 2.

1. you get to use, and are expected to use techlahoma branding, in turn we have aresponsibilityt o help promote and mention your group in our own media outlets
   1. there is an understanding that you group is in alignment with our own mission
   2. you are willing to help promote groups other than your own
   3. your group is focused on the betterment of the attendees, the 'users' of your usergroup
   4. You agree to the terms of our CoC
   5. you are willing to allow some time at the beginning of your meeting to allow sponsors to speak (and in turn this is how we can help support you financially)
   6. your status can be revoked by a 75% majority board vote, or on grounds of you violating the Coc or not aligning with the mission. In turn, you reserve the right to walk away any time from the arranagement, if you feel on your end our missions are not in alignment

The below link to the User Group Report, from the October Board minutes, appears to be a dead link.

https://github.com/techlahoma/board_meetings/blob/master/2018/committee_reports/10_ug_comm.md

Reason: Board meetings are currently dual purpose, for community engagement and administration concerns. They are getting longer and harder to weild. Proposal is to separate these into two separate concerns: Town Hall and Board Meetings

1. Close board meetings to special invitation, board members, officers, advisors.
   -Board meetings are monthly
2. Start Town Hall in the style of open spaces.
3. These are quarterly, and follow the style of open spaces
   http://www.amazon.com/Open-Space-Technology-Users-Guide/dp/1576754766

Proposal is to do the first Town Hall in mid April.