Meetings 2017 03 16

March 16, 2017

Attendees

• brendensoares
• shawncatz

Agenda

• www
• bug train
• next feature train
• flow for api web services in Revel
• test module-based flow

Notes

• discussing revel.github.io
  • want to avoid 404s and typos
  • need to have a formal review process to catch and fix mistakes
  • need to enhance inline godoc comments along side the manual guides
  • need to keep main nav items simple and minimal
• wiki
  • roadmap
    • use the page to communicate high level feature trains and timelines to give a general idea of when we should have certain features in Revel
    • possibly rename to release schedule
  • home
    • draw more attention to core team page
  • revel workflow
    • possibly merge in roles content into this page
    • rename to just workflow?
• RFCs
  • especially for core framework changes and additions, we want to have a clear explanation of the changes, side effects, reasons, etc. This will allow us to update docs when merged and discuss code interface changes.
• using automated tools to create labels and milestones from revel/revel to revel/*
• other items were discussed from Shawn's recent notes and ad hoc action items below

Action Items

• combine issue and PR workflows to avoid redundancy
• assignments should be a pull model, not top down
• refine conductor workflow redundant content
• change “community worker” to “community manager”
• pull in v0.15 train features from backlog based on recent discussions and needs
  • define high level release trains ending in v1.0
• separate release content from workflow wiki
• define specific label changes (removal, addition, etc) and review with team re:roles/workflow
• refine contributing to be more focused
• add contact wiki page and remove all other places where IRC, SO, etc are listed to have just one central place for contact info
• write scripts to monitor web presence for Revel (SO posts, reddit posts, twitter, etc)
• build issue templates
• audit wiki and website docs for accuracy
  • can we improve the formatting of the godocs?
• review notes from above for additional actions items in wiki
• lock down PR flow for revel.github.io to avoid 404s, typos, etc
• figure out when the whole core team can talk