---
# System prepended metadata

title: Ahau team hui | 2021-02-22

---

# Ahau team hui | 2021-02-22

opening karakia : https://gitlab.com/ahau/process/-/blob/master/karakia.md

last weeks notes: https://hackmd.io/q2sBhmsmTXWHQfxQeJHuVg?view

## Milestones

- V1 Milestones (from 11 Dec)
	- [x] i edit any record that I have access too
	- [ ] i can decline an application
	- [ ] i can provide whakapapa information to a group application
	- [x] i can add collections to an archive
	- [ ] i can add an exisiting profile to a community

# Agenda

- [x] Karakia
- [x] Check-ins
- [ ] Last week
  - [ ] Actions from last week | Asana
  - [ ] Blocks
  - [ ] Updates
  - [ ] Reflections
- [ ] Milestone Revisit
- [ ] This week
  - [ ] Action for this week | Asana
- [ ] Closing karakia

## Last Week
- looking in asana Sprint 4 https://app.asana.com/0/1199666386930030/board

Rahera:
- the facilitation pack template (for facilitators to use)
  - KM is looking at that
- Finished colaborated whakapapa process
- set up E panui template
- put all text in google sheet for translator



Cherese
- Application UI
  - updated notifications panel
  - updated registration form
  - updating review form
  - updated packages
- merged PRS
  - ssb-graphql-tribes
  - whakapapa-ora custom community forms
  - .... 

Mix:
- did a little conversation with apple pataka thing
- cherese pointed out a failing test and i ended up going down a whole testing thing and turned up a couple bug
  - one was really important
  - sent a bunch of time to make sure tests pass on windows linux and mac
  - confident they are all passing
  - important for security
- code review
- worked on partners (specify a partner in the backend)
  - opening ssb-whakapapa
    - upgrade that to use ssb-crut (maintenance)
    - easier to write ssb-crut makes maintenance easier
- crut now has the tombstone method by default
  - requires checking anything using a tombstone
  - major release wont be a problem
- had a call with coblox
  - asked them for an update
  - they've got some code for me to test (smoke test)
- Lined up a call to catch up with Eurobutts
  - hopefully this week

Blake
- finished profile form changes + merged it in
- fixed whakapapa table bugs
- went into a vacuum on thurs and fri with whakapapa table menu
- did a bit of work yesterday on small bugs and small changes on ui

Ben
- Did some work on the budget work
- 12 hours on Collections UI
  - Started with collections title card and went onto fixing some other bugs
- pairing with mix
  - milestones
  - next features
- whakapapa process
  - diagrams
- spend reviewing 
  - 2 hours on pataka testing
- forgot to toggle some things at end of week

### Blocks

Mix
- large files need testing (from Cobox)
  - i should do it or someone else?
  - i can continue with partners work or work on that
  - magma have till the end of this month, needs doing today or tomorrow
  - 

- partner records?
  - link/profile-profile/child
    - parent
    - child
  - link/profile-profile/partner
    - parent/ child?
    - source/ target

Rahera
- having issues with the servers
  - when im smoke testing, maybe im not doing it properly
  - what are those bugs?
    - i think its how im starting things up
  - npm ci
  - cherese: reocmmend against use `npm run cleanup`
    - it deletes all the node_modules in desktop + ui
    - if the package.json has changed, then that's when you need to re-install

  Recommended (if npm ci doesnt work):
    1. Check package.json on PR to see if they change (sometimes i just skip and reset them anyway)
    3. If it has: delete `node_modules` folder in the same folder as that package.json
    4. run `npm i` in that folder
    5. should be good to go!
    Note: this is mainly used in the desktop folder if the back-end modules have changes
    Note: May be suitable to run every time if youve downloaded modules previously and then the one you want to look at has no changes
    Extra: you can check if you already have the package installed with `npm ls <the package name>`
  

Cherese N/A

Blake
- table filter menu
  - UI changes

Ben N/A


### Updates

Mix
  - Large files...

Ben
  - trying not to work too much for couple days as gonna be away for full weekend
    - 3 days taitokorau
    - 2 kaimai forest
    - 1 auckland
    - 1 tauranga
    - 1 wellington
  - call my phone directly

Blake
  - did couple hours yesterday
  - half day today

### Reflections




Blake
- Sprint board has been helpful but need to get into the habit of checking my tasks more frequently
- Have found the team toggl useful as well
- Feel a bit frustrated that I wasn't active in the chat/jitsi on Thur/Fri last week, but happy that working in a vacuum helped me make some progress on table filter menu

Rāhera
- Feeling like I need to form better processes for testing 
- Asana and toggl good for managing productivity

  - Cherese: I can help by writing some better commands for you to use :smile: Thanks!


Cherese
- cool to see our list of things completed each week on asana (its been getting bigger each week!! ) :smile: and its nice to look back!
- I set up a pataka with mix, then last week i connected my computers to it! So awesome to use! Especially for testing (wrote a little hack to connect it and not sure how long it will work)
- Its cool to see all the new changes the team has been making

Mix
- CI testing is annoying AND awesome
    - find bugs like a boss (slow VMs, different OS)
- github has better CI tools (but is leaning evil)
- want to book 2 weeks of to do Rust learning
    - personal learning
    - relevant to Ahau
      - accessing some of the Sunrise Choir ssb work
      - can write things in rust then compile to WASM (web assembly, which Node can run)
- love doing maintenance work
    - ssb-crut
    - ssb-tribes
    - (itching to do ssb-ahoy to upgrade electron)
- stoked with ssb-crut (+1 Cherese)
    - adding new things is easy
    - Luandro is using it with Community Currency project
- where are we with end of Feb goals
- Toggl <> Asana integrations

Ben
- mixins feel like a bit of a regression proping and emiting functions and data. Am stuggling a little to get my head around how best to use them
- I have a live pataka permantely running at home
    - i was wondering if I could have a permanent dev pataka running at th last time e same time 
        - could i just change some code locally to do this without getting the errors
- feeling like i made a bunch of promises about changes in the app that we havent managed to get to 
- the app is slow
  - could be old data hanging around?
  - rahera: its pretty slow, even with the archives page loading
    - ben: im getting about the same
    - cherese: same for me
    - mix: is it just stories
    - ben: it takes a while to add/remove/edit anything
      - its a little scary
      - may be a big issue but not a big fix
      - needs to be investigated before publishing
    - mix: no pagination put in on stories/archives 
    - rahera: slow not even loading any stories
    - mix: may have an idea
    - ben: can we make this a priority

## Milestone Revisit

- V1 Milestones (from 11 Dec)
	- [x] i edit any record that I have access too
	- [ ] i can decline an application
	  - [ ] graphql declining
	  - [ ] ui
	- [ ] i can provide whakapapa information to a group application
	  - [ ] allowing your data to be sent to the community kaitiaki
	- [x] i can add collections to an archive
	- [ ] i can add an exisiting profile to a community
	  - [ ] later!

## This week



