Rufus NTS for leads meeting

Specific actions

• move discussion to github discussions either on product or portals-monorepo so that …
  • discuss asynchronously
  • involve team

Thread

• Focus on one thing: 🌀 Portals
  • Why? Already main work area
  • Ignore DataHub totally for now
    • Rufus has this for now
    • Less important medium term even if good long-term potential
    • We can discuss later if needed
  • Leave Data Services for now
    • we've already made some good progress with our offer online, plus upwork
• Immediate actions
  • what: have offers well defined for ourselves and others
  • who: who are the users, what are their needs
  • where (aka channels):
  • measurement:
  • team:

Misc

• Should we merge product into portals-monorepo
• How we can coordinate better (and involve team)
  • Why is this even important?
• Can we reduce meetings and do more online so that we coordinate better, spend less time in meetings
  • 🚩 Chat is ok for chat, not good for conversations etc and not good for knowledgement management
    • Why? …
  • ⟹ use discussion threads and/or issues complemented with a wiki/docs
    • Issues are tasks
    • Discussions are discussions. If in doubt start with a discussion

What's tough about organizing the document

• Multiple ways we can slice stuff
  • Overall picture on e.g. branding, bizdev etc
    • this is important because do need things to cohere

Still open questions

• Toolkit or PortalJS for naming / branding.
  • DataHub Toolkit or Portals Toolkit or …
  • Do we need a common brand name? e.g. DataHub X
    • NB: Vercel seem happy to have tools not branded with their name
    • At least for our purposes key thing is to have standard names and not change