June 2021 Priorities, Part 1

[jefftangx]

June 2021 Priorities, Part 2 Here

Notes: https://roamresearch.com/#/app/athensresearch/page/wzoTtozBy

Backend

P1: Self-Hosted Collaboration Using Single-Writer Approach | Status: In Progress | @neotyk

• Why: our top customer needs this and no one else has real-time collaboration yet (except for Roam which has really bad collaboration UX and still has data loss).
• Main PR outlining approach feat(rtc): v1 self-hosted real-time collaboration #1170
• Getting support from Flexiana and Datahike

Frontend

P2: Text Editor | Status: Help Wanted | @shanberg

• Why: lots of bugs occur from our text editor implementation which has two views: render (when not focused) and raw (when focused)
• See New Editor to Replace Raw Textareas #1091, Cursor is not placed at the location of the click in a block #566

P2: DB Switching | Status: In Progress | @shanberg @sid597

• Why: improves UX for when we have collaborative knowledge graphs -- will want to be able to switch between local and remote graphs easily.
• Database Management #882

P2: Presence | Status: scoping | @shanberg @neotyk

• Why: collaboration UX is very important for collaborative graphs
• See "Presence" search query
• Notes on discussion between @shanberg and @neotyk

P2: Utilize a dropdown/popover library | Status: Ready to start | @shanberg @juniusfree

• Why: TODO Invest in Material-UI React Component Library #1316
• Popper #869

Community

P1: Head of Community | Status: Done | @joelhans

• Why: community is a core function/domain of Athens and we need a rock solid pillar that can build out this function and team.
• Continue to refine job description
• Learn from Heads of Community in other OSS and Crypto Startups/Projects
• @joelhans starting full-time June 18th

P1: Finish the Handbook | Status: In Progress | @joelhans

• Why: we need to document our guidelines for both contributors and employees in order to effectively and efficiently collaborate at scale
• @joelhans taking over

P2: Scaling GitHub | Status: Help Wanted | @tangjeff0

• Why: we need to master GitHub features to build Athens at scale
• Research, notes, links on Roam
• The current problem, Roam notes

P1: Launch Website | Status: so close | @tangjeff0 @shanberg @mateicanavra

• Why: we need a 1) a central entrypoint to Athens that is not GitHub/Twitter/Discord/Handbook, 2) we need to begin marketing Athens to our ideal customer to gain adoption and monetization

Meta

P1: Onboard Core Team | Status: In Progress | @tangjeff0 @shanberg @mateicanavra @joelhans @neotyk

• Why: we are bringing on people to build out entire departments of an open-source startup. We are going 1->5 core leaders, which requires evolution in terms of communication and knowledge and task management infrastructure.
• create and document systems, processes, guidelines for work, meetings, etc.

Retrospective on May

[juniusfree]

P2: Utilize a dropdown/popover library | Status: Needs Research

@tangjeff0 Can I try to do this again?

[jefftangx]

@juniusfree requires research on which libraries we want to use. @shanberg is unsure about Material UI Dropdown component, I am okay with it. Can you evaluate the current options available to and share a doc?

[shanberg]

The Material UI dropdown works fine, and nothing's stopping us from using it for our context menus, dropdowns, tooltips, and dialogs.

I just want to evaluate it more carefully before we get so deep into it by accident that we can't afford to eject.

[juniusfree]

@shanberg What are the considerations before we choose a library?

[shanberg]

@juniusfree I just wanted to make sure I understood what we were getting with Material-UI, and what potential drawbacks might be over time because it felt like we'd just stumbled into the library without examining the options. But I'm happy with what I've seen, so I have no reservations.

[juniusfree]

@shanberg Alright. I can start with the conversion of the pop-ups if that's okay.