Agenda
----------
- Location: #wikimedia-office IRC channel
- Time: Weekly, Wednesday 22:00 UTC (2pm [PST- [Meeting type](https://en.wikipediawww.mediawiki.org/wiki/America/Los_Angeles))Good_meetings#Taxonomy): TBD
- [Meeting type](https://www.mediawiki.org/wiki/Good_meetings#Taxonomy): Field narrowingTime: Weekly, Wednesday 21:00 UTC (2pm [PDT](https://en.wikipedia.org/wiki/America/Los_Angeles), 23:00 [CEST](https://en.wikipedia.org/wiki/Central_European_Summer_Time))
- Agenda:
- {T124752}This time is the standard as of this writing (in March 2016), but may change as we make adjustments to accommodate daylight savings/summer time adjustments for the participants. By default, we intend for this meeting to be held Wednesday 2pm [San Francisco time](https://en.wikipedia.org/wiki/America/Los_Angeles).
- Topic:
- Key Questions
- Should the expiry date be its own field or should a properties field be introduced?
- Is a more automatic way of keeping the watchlist table clean needed or will a maintenance script do?TBD (for discussion in comments)
Other meetings
- Will indexes be needed on the expiry column in order for this to scale?------------------
| **[Architecture meetings](https://www.mediawiki.org/wiki/Architecture_meetings) ** |
- Should the refactoring talked about actually happen and if so should it happen before or after the changes?|-----------------|
- Should custom expiry date be considered in the import/export process using Special:EditWatchlist/raw), or should all imported and exported watchlist entries always have unlimited watching duration?
//See the [Architecture meetings](https://www.mediawiki.org/wiki/Architecture_meetings) page for more general information about this meeting (also: [Phab query: list of upcoming RFC meetings| **14:00 PT ArchCom-RFC Meetings** | **[upcoming](https://phabricator.wikimedia.org/calendar/query/ShzbHT6BPGCE/), [Phab query: list of all RFC meetings** | **[all since 2015-09-09](https://phabricator.wikimedia.org/calendar/query/XJjy54s3PEFf/)).//**