Office hour notes: 2020.02.18

Attendees

What is everyone working on?

Lyre
- OpenCollective folks joining us for March 3rd meeting.
Ian
- working on http bridge
  - https://github.com/sandstorm-io/sandstorm/pull/3221
  - https://github.com/sandstorm-io/sandstorm/pull/3222
Dan
- Working on OpenStreetMap thing. Near done getting tile server going?
- Successfully starts up postgres, initializes.
- Worked around /dev/shm unavailability for now
- not using apache's mod_tiles, other option less recommended but fits daemon constraints better
- Question asked: what's wrong with apache that makes it hard to package? Might be valuable for community to know how or what's hard
  - Not sure offhand, can look into later
Adam Bliss
- Taking care of baby
- Looking at porting matrix.im & riot (frontend) and they recommend not hosting riot on the same domain as your matrix install.
  - Ran afoul of CORS issues
  - When you set up an API endpoint, replies to requests with Access-Control-Allow-Origin: *
  - but that's not enough for HTTP basic auth to work, for some reason?

some discussion of reusing systemd configs to figure out what you're launching? probably not worth trying to use systemd itself to launch units

Kenton
- Spent a day trying to catch up on Sandstorm stuff, did not fully succeed
- Pushed a release, turned off the tests that were holding us back from Meteor 1.8.2
  - Need a new, supported plan for how to run JS unit tests
  - Rest of test suite is selenium, which (somehow) people keep supporting
- Plan to make Meteor 1.9 work between now
  - blocked on node-capnp working with Node 12, since Meteor 1.9 switched to node 12
- Reviewed some open pull requests; did not get to all
  - Expect to get to Ian's other PRs this weekend
Drew
- https://github.com/sandstorm-io/sandstorm/pull/3231
- Looking at what is needed to get us using modern js conventions and tools on the front end. Imports, modules, Typescript, etc.
- Simplifying package management by moving away from meteor's fancyness would be a good thing.
- Proposal writeup incoming.
What's the status of Mongo in Sandstorm?
- We're still using 2.6
- No longer supported upstream
- Meteor may no longer support mongo 2.6 at some point
- Upgrading self-hosted servers complicated. What if people run out of space in the middle of data export from old version of database?
- https://github.com/sandstorm-io/sandstorm/issues/3235

Add to next agenda:

Can we establish some clear short-term goals/milestones?
- I set a ~6mo. goal for vagrant-spk: https://github.com/sandstorm-io/vagrant-spk/milestone/4 but Sandstorm, as a larger more complex project should have multiple milestones.
- Not set in stone, milestones for Sandstorm should highlight achievable short-term (6-12mo.) goals backed by a list of relevant issues/action items.
- An example might be "Improve self-hosting experience" (containing #3186 #3204 #3211). A lot of Ian's issues on the Powerbox would likely be another milestone.
- Only Jake can update GitHub milestones, but this could be modeled in the Wekan by using cards with a checklist. (Lyre has a great example one already.)

Code Contribution

Giving Talks