User Tools

Site Tools


emerson:stone-soup:digital-infra-overhaul

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
emerson:stone-soup:digital-infra-overhaul [2025/04/01 16:10] – created naptasticemerson:stone-soup:digital-infra-overhaul [2025/04/29 15:05] (current) naptastic
Line 1: Line 1:
-====Facilities Makeover==== +====Digital Infrastructure Overhaul==== 
-Honestly I'm surprised more people aren't jumping on these ideas. I suspect the issue is fatigue. That'finethat's why I'm here.+    * Involving the current stakeholders sounds hard but it's completely doable. 
 +      * Need a list of who owns what 
 +      * **ASYNC** Brainstorming session on how to provide all the church'digital needs 
 +    * We need a task management systemHilary suggests Asana
  
-===Building Security Review=== +    * Aim for Discord until we find something better**It'going to take long time for communications to converge and I'm sorry.** I'm doing my best. Some people are going to be stuck on Zoom, Signal, and Facebook until we have something that actually ticks all the boxes. 
-Information about a security review does not go on an insecure page like thisThe point is, we know where Emerson'weaknesses are from security perspective, and we know how easy they are to get around. We need to improve our policies and procedures, and to some extent upgrade our facilities, to reach a level of physical security appropriate to the level of activism we expect to engage in, and the possible hostilities we should be prepared for.+    * User accounts 
 +    * No AI content policy (I'll explain later) 
 +    * I have another computer for the work room 
 +    * Network upgrades
  
-**Additionally**, there are some security needs we don't have yet, but we will, and we need to prepare for them. I'll get into that later.+====Worship Workflow App==== 
 +Ed's template-based system is genius. The weak points are the result of how it's implemented. To fix the pain points and get the flexibility and usability we need, it really needs to be an app.
  
-===Sanctuary makeover=== +This is something I have to manage myself. I have zero faith that another project manager could get it done without hiring an entire team and **we don'need that**The way to get the app developed and delivered successfully is to get the smallest team possible of the right peopleWe don't have those people yet, and the theorycrafting piece explaining how this is all going to work (and how we're going to avoid all the traps that app development usually falls into) isn't written yet. I'll have it before we need it.
-  * Lights: Replace the neons with LEDs and tie them into the main lighting system +
-  Replace the fluorescent lights in the organ chamber with LEDs +
-  Clean the high surfaces +
-  * Resurface the chancel +
-    * 3D print some feet for the choir risers so they don'scratch a new floor +
-  Hanging choir mics* +
-  * Acoustic treatment on the back side walls, which are currently very naked +
-  * Get the organ fixed +
-    * The console needs to be taken apart, cleaned, and put back togetherIt's a few days' work with some kind of nasty chemicals, or we can ask an organ builder to fix it. +
-    * The physical pipes do not currently sound. Having those stops missing is annoying when playing. +
-    * We do not currently have a working relationship with **any** organ builder. +
-  * Replace the little stick for opening the piano +
-  * The pull handles to get into the sanctuary need to be polished (I think?) +
-    * I'm sure there's a lot of other "elbow grease" stuff don't know about or haven't noticed.+
  
-We need more data before we can intelligently choose hanging mics. Gathering that data is a non-trivial project; I will need some A/and choir and musician hours allocated to get that all squared awayDetails on [[emerson:stone-soup:mic-party]]+====The Book On The Church==== 
 +===Org Chart=== 
 +  * needs to have links to personal directory 
 +     * Executive C-positions 
 +     * List of committees, members, and responsibilities 
 +     * connections with other orgs, churches, etc., as part of our organizational chart. Liaisons and their relationships need to be listed.
  
-===Use Westwood Better=== +(Change language of "committee", "team", "ministry", and perhaps a few other terms. There are times and reasons for each word. We need to change a few around in order to get the results we want. More later.) 
-  * One or two A/V control rooms in the upstairs + 
-  * Off-site storage for stage stuff+  * Maps 
 +  * Directory 
 +  * Calendar 
 +  * Playbooks (specifically, the instruction manual for Westwood Hall needs... yeah) 
 +    * The checklists from which we operate need to come from a single place. The workflow for "being in charge of a service" needs to start with making a copy of the appropriate checklist. 
 +  * Archives and links 
 +    * There's a book of old member sermons in the Ready Room that ought to be digitized 
 +  * History 
 +    * Somebody wrote a history that's complete up to ??? years ago. It should be digitized, and I should read it.
  
emerson/stone-soup/digital-infra-overhaul.1743523851.txt.gz · Last modified: 2025/04/01 16:10 by naptastic