BMO/Meetings/2014-07-08: Difference between revisions
Jump to navigation
Jump to search
(Created page with "* When do we shut off BzAPI?") |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
* When do we shut off BzAPI? | * When do we shut off BzAPI? | ||
** When enough high-profile/heavy-use sites switch to the compat layer, we'll be redirecting all traffic to the compatibility layer. See tools.bmo posts. | |||
* Make reusing users easier? | |||
** Not worth it to add a new column; we only reuse users because there are some to be reused. | |||
* Switch to memcache-fast | |||
** At some point, if memcache becomes more of a bottleneck. | |||
* Express form fields, dependencies, etc., in a data file? | |||
** Would like to know what percentage of existing forms (or at least of a good sample) could be switched to this format with little or no change. | |||
** Dylan to file a bug and investigate. | |||
* Brainstorm features that can alleviate the pain caused by limited header filtering in GMail at BMO meet-up later this month. | |||
Latest revision as of 16:09, 8 July 2014
- When do we shut off BzAPI?
- When enough high-profile/heavy-use sites switch to the compat layer, we'll be redirecting all traffic to the compatibility layer. See tools.bmo posts.
- Make reusing users easier?
- Not worth it to add a new column; we only reuse users because there are some to be reused.
- Switch to memcache-fast
- At some point, if memcache becomes more of a bottleneck.
- Express form fields, dependencies, etc., in a data file?
- Would like to know what percentage of existing forms (or at least of a good sample) could be switched to this format with little or no change.
- Dylan to file a bug and investigate.
- Brainstorm features that can alleviate the pain caused by limited header filtering in GMail at BMO meet-up later this month.