# JSON API Weekly Meeting - July 24th, 2015

**URL:** <https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63>\
**Category:** Meeting Minutes\
**Created:** [July 24, 2015, 2:04pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63 "2015-07-24T14:04:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tkellen](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/tkellen/32/1_2.png) [@tkellen](https://discuss.jsonapi.org/u/tkellen)\
**Post date:** [July 24, 2015, 2:04pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63/1 "2015-07-24T14:04:42Z")

</div>

### Determine how we want to handle alpha/beta/release versioning for the website

- Website will always show current stable version by default.
- Version number on header will become a dropdown showing all stable versions as well as the current alpha/beta. The dropdown will allow for toggling between versions.

### Determine what’s needed to get the discussion around embedding and side-posting started

- Source issue: [#795](https://github.com/json-api/json-api/issues/795)
- @dgeb will kick off the discussion in the aforementioned issue with the list of requirements we’ve drawn up.

### Add optional support for top level `version` key in resource objects to indicate versioning.

- Source issue: [#600](https://github.com/json-api/json-api/issues/600)
- @dgeb and @tkellen are +1 to adding this.
- Unless @ethanresnick or @steveklabnik object, we will add normative support for this in 1.1 alpha.
- We can’t add this “officially” until the website supports versioning.

---

<div class="post-metadata">

**Author:** ![steveklabnik](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/steveklabnik/32/2_2.png) [@steveklabnik](https://discuss.jsonapi.org/u/steveklabnik)\
**Post date:** [July 24, 2015, 3:54pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63/2 "2015-07-24T15:54:18Z")

</div>

I really need to set my alarm to wake up early enough ☹

What specifically would this version key be indicating? EDIT: I guess I can read the linked issue, whoops

---

<div class="post-metadata">

**Author:** ![dgeb](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/dgeb/32/17_2.png) [@dgeb](https://discuss.jsonapi.org/u/dgeb)\
**Post date:** [July 27, 2015, 8:59pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63/3 "2015-07-27T20:59:50Z")

</div>

> [@steveklabnik](#):
>
> I really need to set my alarm to wake up early enough

I’d be glad to move this to a later time if it would work better for folks. The current time is especially unfriendly to west coasters.

---

<div class="post-metadata">

**Author:** ![tkellen](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/tkellen/32/1_2.png) [@tkellen](https://discuss.jsonapi.org/u/tkellen)\
**Post date:** [July 27, 2015, 9:46pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63/4 "2015-07-27T21:46:04Z")

</div>

Same! What time works for you @steveklabnik?

---

<div class="post-metadata">

**Author:** ![steveklabnik](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/steveklabnik/32/2_2.png) [@steveklabnik](https://discuss.jsonapi.org/u/steveklabnik)\
**Post date:** [July 27, 2015, 10:31pm UTC](https://discuss.jsonapi.org/t/json-api-weekly-meeting-july-24th-2015/63/5 "2015-07-27T22:31:00Z")

</div>

One problem is that I travel a lot too, so every once in a while, I just can’t because I’m on a plane or something.

Something more like 10 or 11am EST would be much better, if we’re still shooting for morning.