Skip to content

Meeting Notes

Jump to bottom
Kimi edited this page Aug 22, 2016 · 11 revisions

22 August 2016

Attendees: Paul, Kimi, Ben, Erika, Victoria

  • Main functionality completed
  • Frontend/styling development to begin this week to the visual guidelines here: https://invis.io/XM897JRCA
  • Brainstorming on new brand name needed
  • Ben to supply credentials for a super user to Devs
  • Erika/Paul to update readme for 0Auth process
  • Erika/Paul to share a standardised format with Ben for data to seed test db
  • Ben, Devs and Kimi to schedule upcoming time to confirm database structure
  • Teardown to happen wk of 29th to go through all functionality and edge cases in person
    • drinks.

11 August 2016

Attendees: Paul, Kimi, Ben, Natsuki

  • No backend hackathon held this week.
  • Wireframe by Kimi coming in: https://invis.io/XM897JRCA
  • Need timeline doc --> Natsuki to work on
  • Sprint Day: Sunday, 21st August Time and Place TBD (Shoreditch?)

04 August 2016

Attendees: Paul, Rhiannon, Natsuki Some more questions re: specification

  • Report an issue - should there be categories like spam / duplicate / inaccurate? Logged in users only?
  • Managing reported issue - what does it look like? who manage?
  • One definition vs. Multiple definition (e.g. Urban Dictionary, Stack Exchange...); maybe as a part of report an issue flow, users can suggest alternative (e.g. Google Translate) -- Action point: Natsuki to put them in specification discussion doc. Follow up with Ben / Kimi

Wireframe -- Victoria is working on it this weekend

Demo site: https://vocabulary-app.herokuapp.com/

28 July 2016

Attendees: Kevin, Victoria, Natsuki

Wireframe (@Victoria)

  • Could have more hands - will discuss with Natsuki / Kimi to divide tasks

Backend (@Kevin)

  • Hackathon outcome: basic table, handling one word with multiple template, basic search (no elastic search for prototype), oAuth with FB...
  • Next hackathon - next week ? Need help with clarifying some requirements - Natsuki will lead discussion
  • Are we showing definition both in EN / AR? Are they translation of the other?
  • How to add new terms - Actual use cases will be helpful
  • Up - down voting ? (confirm if it's nice-to-have / must-have)

To-do for next hackathon;

  • search - academic field filter (if no terminology is typed but filter is applied, then show all terms in the field)
  • no result found page

24 July 2016

Attendees: Kim, Victoria, Natsuki

###Action Items

  • Victoria - provide the first version of wireframe by the end of July
  • Natsuki - Coordinate weekly call
  • Natsuki - Document user story / requirements so far in wiki (Draft)
  • Kim - Share sketch of wireframe / meeting notes with Natsuki and Victoria

Meeting Note:

Wireframe needs

Must for prototype launch:

  • search (terminology + field of study (optional))
  • search result page (need to be able to see which fields of study the terminology belongs to)
  • detailed result page (show details of the single terminology)
  • add new term page

Other pages:

  • editing - inline (so may not necessarily need specific wireframe)
  • admin monitoring page (managing reported contents)
  • sign-in (Facebook)

Note:

  • Main wireframe in Desktop, but also show mobile screen, too.
  • Arabic is right-to-left language. (Eddie speaks Arabic, so he could help with language)
  • no in-product feedback loop

General Timeline

Wireframe (desktop and mobile) (End of July?) > Dev work > Ben and his team to put sample contents > Test / QA > Launch (target: Friday, 2 September 2016) Then Ben's team will run test sessions with refugees to gather feedback.

Clone this wiki locally