Skip to content

Latest commit

 

History

History
156 lines (102 loc) · 4.49 KB

20190115-telco.md

File metadata and controls

156 lines (102 loc) · 4.49 KB
Raw

SpaceAPI Telco January 2019

Date: 2019-01-15
Location: The Internet
Who: Danilo, Raphi, Timm

Previous meeting: 20181009-telco.md

1. Agenda

  • Status
  • Inclusion of @rorist to Core team
  • Feedback from 35c3
  • Moving SpaceDirectory
  • Website
  • Directory
  • Metrics
  • TLS on reverseproxy
  • Ansible-vault from gopass
  • Logo on black

2. Status

  • Danilo
    • Move spacedirectory.org to spaceapi.io
    • Move validator.spacedirectory.org to validator.spaceapi.io
    • Register Twitter-Handle and put password in gopass
  • Timm
    • Short presentation about the project for lightning talks etc
    • Draft for directory spec (OpenAPI 3.0) in a GitHub branch
    • Create SpaceApi-archive GH organization, give Slopjong access, move old repos there
    • TLS forwarding traefik
    • Put Directory on directory.spaceapi.io
  • Raphi
    • GPG pubkey to Timm for pass repo
    • Responsive design fixed for small devices

3. Inclusion of @rorist in the core team

Does @rorist want to join the core team?

@rorist couldn't attend the telco. Let's talk about it next time or via E-Mail / Chat.

4. Feedback from 35c3

  • List of language bindings / impementations would be nice: SpaceApi/website#23
  • Entirerly not clear that spaceapi.net is dead and we are the active project
  • I had to explain the fork story multiple time
  • Getting started guide missing: SpaceApi/website#25

5. Website

We should do some usability testing. Maybe @timm can find some designer / UX help from CCC people.

It's not clear for people looking at the start page what we are and what we want.

How to describe the SpaceAPI project in one sentence? The My Hackerspace app describes the purpose best currently, when showing it to other people.

Should we add a help needed section?

Getting Started Guide

SpaceApi/website#30

Should we recoomend static hosting on GitHub / GitLab? The problem is they don't allow setting the CORS header.

Decision: We make an example for static hosting on a server (not GitHub/GitLab) which sets the CORS header correctly.

6. Directory

Moving SpaceDirectory

Should we move the SpaceDirectory repository to SpaceAPI GitHub orga?

@rorist must be included in the decision. We'll talk to him about the issue on Mattermost / GitHub.

Directory Schema

SpaceApi/schema#29

It's hard to distinguish between the directory source format and the served directory. We need to document this better, maybe even with a diagram 😉

7. Metrics

SpaceApi/provisioning#35

Setup:

8. TLS on reverseproxy

Should this be reachable from the internet? It's easier to setup with traefic that way.

9. Ansible-vault from gopass

We will configure Ansible to get the vault password directly from gopass.

The gopass mount shall be named: spaceapi

10. Logo on black

@timm pinged blinry to create a logo with a black background.

11. Varia

Promoting SpaceAPI at the CC-Camp

  • Maybe at the CCC-CH assembly?
  • Or at the Chaoswest assembly

Next Meeting

Tuesday 9th April 18:00UTC / 20:00CEST

Contact to Slopjong

We made contact to slopjong via SMS. He responded, that he currently doesn't have any time.

Watchtower

Lots of error / info messegas from the bot. Some get sent on redoploy and the others look like temporary errors.

12. Todo

  • Danilo
    • spaceapi.net warning on website
    • Logo on website
    • Upload Twitter-Password to Gopass
    • Watchtower:
      • Auto-update?
      • Get rid of chatty messages?
  • Timm
    • Find some designer / UX help from CCC people for the website
    • Document differences between "directories"
    • Add basic auth to prometheus
    • Add basic auth to traefik
    • Make provisioning repo use gopass for vault password
  • Raphi
    • Write an initial "Getting Started" guide
    • Think about menu / navigation on website