Meetings 2015 04 16
NotZippy edited this page Mar 5, 2017
·
1 revision
- anonx
- brendensoares
- thetawaves (observer)
- Decide roadmap for
revel/cmd
See Comment - Discuss release candidate workflow to release more often
- Decide on repo workflow e.g. branches, releases/tags, milestones
- Decide on open RFCs
- Decide on roadmap priority and effort for all outstanding features/issues/PRs and adjust roadmap as needed
- Enhance GH labels
pending-todos
-
pending-reply
instead ofwaiting for reply
- Get new website working
- Get micro refactoring initiative under way
Decide roadmap for revel/cmd See Comment
DECISION: hold off on cmd changes for now as they are related to major architectural changes.
Internal Revel Core Priority List (important)
- Composable Controllers to replace filters and interceptors
- Reorganize code files in subpackages https://github.com/revel/revel/issues/614
- Asset pre-processing revel/revel#901 vs general script runner https://github.com/revel/revel/issues/889#issuecomment-89614910
Pubic Revel Priority List (Important and urgent)
- flexible templating (configurable for pongo, jinja, go, etc) a. revel.View model similar to revel.Controller
- asset pre-processing (coffeescript, haml, etc)
- user authentication and authorization functionality (e.g. ACL and/or RBAC)
- CSRF https://github.com/revel/revel/issues/788
- get RevelFramework.com online with latest docs
- official preferred ORM, but allow for user’s choice of ORM a. perhaps just standardize where model code files are stored b. models folder/package just like controllers
Post Meeting Action Items
- label all open issues/PRs with priority and effort labels to identify the most important and/or urgent items
Development
Resources
Community