Skip to content

STARS Announcement 09-05-2026

Posted: September 5, 2026

EnglesBird is down and will be back up tonight.

STARS is looking into Paper-Space and Digital Ocean as hosting platforms. We’re currently mostly using Vercel to host static custom client pages and wikis, since it’s free/cheap and works well for pages with no CPU usage.

As the chapter grows, if our digital asset needs outpace what these platforms can handle, we’ll move to join one of the many cloud co-ops, where member orgs pay annual dues (usually a couple hundred dollars) and jointly own the servers.

Several of our original goals, including a website redesign, access to OpenSlides, access to OpenProject, and a Discord bot for Action Network, have seen partial progress. These are minor successes, but none are fully complete.

Given the clear need for infrastructure and mesh organizing within STARS, along with growing member interest in the tech space, we’re formally shifting to ground setting.

The tasks above are not complete. We’ll deprioritize them in favor of the work outlined below.

This project has three primary goals.

  • Create wikis for different processes
  • Thoroughly document technical processes in a private wiki
  • Thoroughly document organizing processes in a private wiki
  • Thoroughly document resources and onboarding materials in a public wiki (non-sensitive info only)
  • We’ve been pushing national for a pilot license for OpenProject, since their hosted version is still in beta and limited to chapters with cadre formally within the NTC.
  • We’ll give this until the end of September. After that, we’ll shift to self-hosting an open source project management tool, which should take about a week of setup by someone familiar with web hosting. This will likely mean bumping up our resources on whatever platform we’re using to host custom web services should we adopt one, which could increase our monthly hosting cost by roughly $5 to $10.

Goal 3: Clean Technical Request and Delivery Systems

Section titled “Goal 3: Clean Technical Request and Delivery Systems”
  • Build a “Rank-Validator” tool to confirm whether an email belongs to a member in good standing
  • Automatically serve low risk requests such as:
    • Discord access
    • Google Workspace access
    • OpenSlides access
    • Access to project management software or other core systems expected for members in good standing
  • Develop a Help Desk system for requests that need manual review
  • Build out infrastructure to support more complex requests and needs, which may include:
    • Buying or renting server space
    • Hosting APIs for special operations or requests
    • Hosting documentation via wikis, shared drives, or cloud notes
    • Standardizing and ranking system access based on knowledge ownership and trust in deployment pipelines

We’ll deliver a 3 month project timeline with milestones and deadlines, using intermediary tracking tools until formal project management software is in place. This project document will be presented at the next Comms Committee meeting or General Meeting for feedback and discussion.