August 2026 - Advisors - list.chattanooga.digital

FOSS Evaluation and IAM/IdP
by Greg Laudeman Sept. 3, 2026

Sept. 3, 2026

Who would be willing help evaluate software for members and/or use for internal purposes? We also need some standard practices, procedures, and tools for this purpose. There are lots of informative resources for using FOSS as components in other projects, which is not exactly right for Chattanooga.Digital since we primarily deploy off-the-shelf FOSS (although one aspect of this is how to evaluate custom or special purpose apps for members, which would be a fee-based service). The "grand-daddy" seems to be https://dwheeler.com/oss_fs_eval.html from 2011. The author includes lots of good resources although a few seem to be outdated. The Concise Guide for Evaluating Open Source Software <https://best.openssf.org/Concise-Guide-for-Evaluating-Open-Source-Software.…> by the Open Source Security Foundation is really good. Another one I like is https://leaddev.com/software-quality/12-things-consider-when-assessing-open… because it seems practical and thorough. Let's combine key elements from these to create a review protocol and scoresheet. At the same time, we need to look at identify and access management (IAM) software. I suggest we use this to hammer out the process, etc. The key missing element with the frameworks is "why." What is the purpose for and requirements of the software? A related element is the user, specifically the "sponsor" that requires the software. For IAM, the sponsor is us, the cooperative, including all members. The basic purpose, as the term implies, is to manage members' access to resources, including and via a digital identity. Our digital identities are a collection of attributes, credentials, data, and devices that represent us. As mentioned in a prior email, the fundamental purpose of Chattanooga.Digital is to give members complete control and full ownership of our digital assets, including our digital identities. More practically, we need: * Authentication via passkeys, passwords, and other factors for single sign-on to as many of our apps/systems as possible. * Authorization for access to apps, data, files, etc., with permissions in various roles. * Automation of user account management as needs for authentication and authorization change. * Governance and monitoring of access, including all of the above, for accounting, compliance, planning, and security purposes. * Via standard methods and protocols: OAuth, OIDC, SAML, etc. Beyond that, we need to position Chattanooga.Digital as a digital identity provider (IdP) for members to access other systems and own data about that access. The main things about this is (a) complementing/replacing centralized digital IDs (b) with a trusted source and (c) supporting decentralized self-sovereign IDs. See https://www.cloudflare.com/learning/access-management/what-is-an-identity-p…, https://www.corbado.com/blog/digital-identity-guide, and https://www.imperva.com/learn/data-security/identity-providers-idps/ for background on this. Please chime in with your thoughts about evaluation approach, methods, process, etc., and how to apply all of that to IAM. Thanks! -- GL

3 7

Chattanooga.Digital's first app: Nextcloud!
by Greg Laudeman Aug. 28, 2026

Aug. 28, 2026

We are ready to start providing Nextcloud accounts to pilot members! Nextcloud <https://nextcloud.com/> is a great general purpose "cloud" app that makes it easy to access files from multiple devices and share them with others. It also has numerous other apps available, such as Talk online conversing/meeting app. All of it is free, open-source software. We will discuss all of this at our next monthly call via Talk. Your account will give you access to our "corporate" Nextcloud instance with 1 GB of storage. We'll inform you about usage and related costs — we need to do that for business purposes — but leave it up to you whether you want to help cover the costs. The purposes of these pilot accounts is to work out management practices and procedures, identify and address issues, and create an online space for members. The pilot phase will be to figure out how/whether to integrate Nextcloud with our accounting and CRM apps. It will also help us determine our basic business model, whether its usage based, flat rate, or some combination/variation. The general plan is to establish "home" and "work" Nextcloud instances for individuals & families and businesses & groups, respectively. When we do that, you'll have the option to move to a paid plan, migrate to a different Nextcloud, or just have the pilot account terminated. Chattanooga.Digital will offer fully separate Nextcloud instances, including instances on private servers, for those who need additional capacity or security, along with other apps separate from Nextcloud. Any feedback, suggestions, or thoughts about this would be welcomed! -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

Our first app: Nextcloud!
by Greg Laudeman Aug. 27, 2026

Aug. 27, 2026

We are ready to start providing Nextcloud accounts to members. Of course, we're still a ways from formal launch and just have pilot members. We still have a lot to figure out. This is a major step in that direction. For pilot purposes we will provide accounts on our "corporate" Nextcloud. We'll inform you about usage and related costs — we need to do that for business purposes — but leave it up to you whether you want to help cover the costs. We need to figure out how/whether to integrate it with our accounting and CRM apps. And, we need to figure out our basic business model, whether its usage based, flat rate, or some combination/variation. The general plan is to establish "home" and "work" instances for individuals & families and businesses & groups, respectively. When we do that, you'll have the option to move to a paid plan, migrate to a different Nextcloud, or just have the pilot account terminated. Any feedback, suggestions, or thoughts about this would be welcomed! -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

Choosing software
by Greg Laudeman Aug. 19, 2026

Aug. 19, 2026

Adam asked a really important, even foundational question: How does Chattanooga.Digital decide what software to deploy, particularly as part of our portfolio. Generally, that's up to members, and we need a process for that. Here are just a few more specific thoughts: 1. In concept we can deploy any apps for a member as long as it doesn't negatively impact other members. * Members must bear the cost of deploying apps. So, basically, if you want an app that's not in our portfolio, you have bear the direct costs to deploy, which may include a code review, particularly to assess dependencies, containerization, etc. Exactly how and how much we charge for this is TBD. * All new apps should be treated as projects, especially any that are being considered for the coop's portfolio. Each project must have a sponsor who is responsible for defining requirements, getting other members with similar needs to join the project, and, ultimately, covering the costs. This exactly what Open Source Program Offices do. 2. We should probably have a "portfolio working group" to identify, prioritize, and research apps. * Within or parallel to that, we may need app-specific task force; an accounting task force, for example. * All of that depends on having members who are willing to either (a) volunteer to serve and/or (b) pay others to do this work. 3. I think it will be critical to have a pretty solid portfolio at launch because access to apps is what's going to drive interest. Yes, some folks may join because the believe in what we're doing. Most people will join because they want to do something or use some particular app. * Personal/family apps will likely drive most of our membership, apps like Actual Budget, Firefly III (accounting), Grocy (or Mealie), Home Assistant, Immich, PaperlessNGX, etc. * Business apps... accounting, CRM, digital marketing, HR/payroll, process automation, etc., etc. * Community app: audio streaming, event management/registration, mapping/geodata, social media, video sharing, etc. It will be important to get stakeholder input on these things. Of course, we have to assume our stakeholders are totally clueless and unable to provide meaningful input. That is one a primary reasons for doing Hack Sessions, to hear from [prospective] members about their issues and give them an opportunity to test-drive some options. Our business plan and bylaws/charter should clearly address these issues... I'm working on that. Any thoughts, suggestion, or feedback would be greatly appreciated! -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

All-call and online space
by Greg Laudeman Aug. 19, 2026

Aug. 19, 2026

Just a reminder that our first monthly all-call is this evening at 6:30. You can attend in-person at Society of Work, 110 Somerville Ave, Ste 266, or online at https://go.eduity.net/call/r7vypa3x. Calendar item attached. I'm resending invitations to hub.chattanooga.digital, a preliminary version of an online space for members. It's probably not what we'll use in the long-term but is an interesting example. -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

Chattanooga.Digital All-call, August 19, 6:30 PM
by Greg Laudeman Aug. 18, 2026

Aug. 18, 2026

Our first monthly all-call will be next Wednesday, 6:30 PM * In-person during Hack Night at Society of Work, 110 Somerville Ave Suite 266, Chattanooga, TN 37405 * Online at https://go.eduity.net/call/r7vypa3x. Let me know if there are any specific issues or topics you want me to cover. -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

2 1

Chattanooga.Digital events this week and next
by Greg Laudeman Aug. 12, 2026

Aug. 12, 2026

Greetings! You are receiving this because you are on the Chattanooga.Venturing advisors email list or have registered for our events on Luma. The next "Let's Learn Linux" study group meeting is this Wednesday, August 12, 5:00 PM at Francis B. Wyatt Community Center in North Chattanooga. This month I hope to set up all of our demo/learning laptops and maybe install Linux on my old MacBook Air. This is an informal group that anyone who is interested in Linux with any skill level is welcome to attend. RSVP at https://luma.com/mjs2o0u8 or just show up! Calendar file attached. Next week, I'll attend a few local tech meetups to share info about Chattanooga.Digital. Specifically, we'll use the Carbon 5 Hack Night on Wednesday, August 19, for our first monthly "all call" to discuss C.D's status, plans, and next steps. You can attend in person or online. If you are on the advisors list, please reply to let me know that you will attend. If you wish to attend online but are not on the advisors list, let me know and I'll add you. You can also register directly via Meetup <https://www.meetup.com/carbon-five-chattanooga-hack-nights/events/315911326/> (registration required).https://www.meetup.com/carbon-five-chattanooga-hack-nights/events… -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

2 1

Identity and Access Management Services
by Greg Laudeman Aug. 11, 2026

Aug. 11, 2026

Chattanooga.Digital needs a process for evaluating and selecting software. We also need identity and access management software, which is a key element of our core infrastructure. More fundamentally, we need to decide how/whether to provide digital identity services. Our general, short-term requirements, that I'm aware of, are: 1. Must have single sign-on to all/most apps, with options/practices for dealing with apps that don't support relevant protocols. 2. Must be able to remove or suspend access to some or all apps without deleting a user/account. 3. Should have multi-level or multi-tenant functionality so that a user can control/own their portion of IAM; organization members, in particular, should have full control over the IAM. 4. Should be portable; the more so, the better. Some persons using members' apps — employees or family, for examples — may not be members of the coop. How and whether they might use our IAM services is to be determined. They may have accounts on one or more apps or one or more members but not SSO. Members may need to manage these accounts separately or run their own IAM services (on C.D or otherwise). An underlying issue is how/whether C.D provides digital identity services, particularly decentralized identifiers, self-sovereign identities, and verifiable credentials. I personally think this is critical but a lot of it is (a) evolving and (b) rather complicated so probably isn't practical in the short-term. My thought about the process for evaluating software for core (to run the coop) or standard (for members) purposes is that it should: 1. Require an anchor user/sponsor. 2. Be carried out by an application/purpose-specific task force or a software evaluation working group; regardless, some member(s) need to own the process. 3. Start with analyzing the requirements, including scope of application and use cases. 4. Methodically identify and evaluate options based on consistent criteria & metrics. I'm not sure what these should be, though... functionality, maturity, etc., but more specific. 5. Generate a recommendation and high-level implementation & management plan for staff and board review and approval (depending on specifics of our charter, which is in the works). 6. Include acceptance testing with members, particularly by the sponsor(s). 7. Result in a deployable, replicable, working version (ideally a Docker image) that can be migrated to production upon acceptance. What do y'all think? Let us know! -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

Hub.Chattanooga.Digital
by Greg Laudeman Aug. 5, 2026

Aug. 5, 2026

Our Hubzilla instance is now live and ready for kicking around! It is frankly a bit... different. It has a LOT of features and functionality, some of which can be a bit challenging to find and grok. "Channels", for example, are basically different areas of interest but function like different user persona. I'm still not totally clear on the practical difference between "Home" and "HQ"! It is intended to be an interim/short-term solution, until (and if) we decide on something else. We'll look at several options in the near future. Any suggestions or thoughts about an online space for members would be greatly appreciated! You should get an invitation to join via email in a few minutes. We'll discuss and do a walk-through during our first "all call" meeting, probably at 6:30 on 8/19. BTW, Hub is ActivityPub-based fediverse app that should integrate seamlessly with Mastodon <https://toot.chattanooga.digital/>, et al. -- Greg Laudeman, Ed.D., Instigator Chattanooga.Digital <https://chattanooga.digital/> greg(a)chattanooga.digital <mailto:greg.laudeman@chattanooga.digital> 706-271-5521

1 0

Email services
by Greg Laudeman Aug. 5, 2026

Aug. 5, 2026

I've learned the hard way about how weird email services are. They're also pretty critical for Chattanooga.Digital. We've tried a couple of options that were less than adequate. What we have now should work short-term but we need something more flexible, functional, and robust. Does anyone know email services really well? Would anyone be willing to do some research on options? I can give you a good starting point and reasonably detailed requirements. Would it make sense to organize a task force/working group on this? As I mentioned in a previous email, IAM is one of the next big apps/services to figure. The two definitely need to work together. Thoughts? Suggestions?

1 1