Meetings 2017 03 02

March 2, 2017

Attendees

• brendensoares
• shawncatz

In Gitter:

• wariosolis
• pedromorgan

Agenda

• discuss project state and start planning revitalization

Notes

• referenced:
• https://github.com/revel/revel/wiki/Meetings
• https://github.com/revel/revel/wiki/Work-In-Progress
• http://www.timqian.com/star-history/#revel/revel to show Revel's continued popularity and one of our "Why"s for working on Revel
• https://www.techempower.com/benchmarks/ to show how Revel has fallen behind our baseline of pure GO HTTP
• Revel's primary goals: ease of use and performance
• Change "Community" to "Support" in Revel's main README.md
• reference http://gobuffalo.io/ as it is inspired by Rails productivity
• new aggregate: deployment platforms?
• Heroku, GAE, Docker, etc
• https://github.com/revel/heroku-buildpack-go-revel
• referenced:
• https://github.com/revel/revel/wiki/Articles
• we need to update for 2016 articles and remember how others have been affected boy our work on Revel
• https://github.com/revel/revel/wiki/Apps-in-the-Wild again, the affect our work has on the world
• what roles can each core member take on?
• https://github.com/revel/revel/issues/892#issuecomment-81676605
• how can we best deal with new feature PRs?
• https://github.com/revel/rfcs
• RFCs are supposed to reduce issue volume by forcing contributors to organize their thoughts
• for significant changes, we need to have consensus with the core team before merging such PRs
• we need to define a release schedule..."release trains"
• ideally, we release monthly
• https://github.com/revel/revel/wiki/Core-Team
• defined final roles
• added 2 new team members (Shawn, Mario)
• assigned roles to current team
• https://github.com/blog/2111-issue-and-pull-request-templates we need this to encourage following an issue format
• Revel v1.0 need s to have a template engine and officially supported ORM

Action Items

• Triage existing PRs
• Merge bug PRs and release into first train
• Merge feature PRs into revel feature branches for further testing and discussion for following release trains
• Plan trains to arrive at Revel v1.0
• Define the PR/RFC workflow
• make use of GH issue templates
• Coordinate with @revel/core to decide additional planning action itemsChange "Community" to "Support" in Revel's main README.md