Today we had our first scheduled meeting.
Consensus was, for a first pass:
- Display a simple lock/padlock icon next to locked posts within the post list screen, leaving the “Request Lock” button for the post edit screens.
- When a post is locked, hide the Quick Edit link, and disable batch edit for the post
- To unlock a post, the user will enter the post edit screen, then click a button to request a lock. Â This will trigger a request to appear for the user with the current lock, where they can decide whether or not to allow the new lock.
As far as development tasks go, @azaozz is planning on finishing a first run at the “Heartbeat” API to be committed before the end of the week. I’ll begin working on the list table changes for post listings. We’re currently looking for volunteers to aid, as there’s plenty of room for help! Additional tasks will include the UI for handling post lock requests and auto-save to local storage.
We’ll certainly chat more about this tomorrow in dev chat, and are planning another meeting this Friday (2013–01–25), at 21:00 UTC (the same time as dev chat), unless this doesn’t work for many of you looking to help. Please post here, or come to the chats if you’re interested in helping with this project, and we’ll get in touch with you for further details!