Fri, Jan 10
Waiting for the tests in the sub-task to get reviewed.
So, the endpoint is live; I've validated that it's working correctly. Please close this when the tests are merged.
Wed, Jan 8
Tue, Jan 7
This seems in our wheelhouse.
This proposal ticks a lot of the boxes we use to evaluate projects: there's a clear need, there's current interest from the Product department, and it also seems to be related to our recent work with Kask, MainStash, ....
Thanks for looping us in @Masumrezarock100 . According to the maintainers list the stewards of the upload code are Multimedia, and @kaldari is the maintainer. I've changed the tags and backed us out, but let us know if we can be helpful.
Dec 11 2019
Dec 10 2019
One last thing: it would be really cool if we dogfood the Core REST API for updating pages on the developer portal.
So, this seems like the kind of feature that makes the most sense for Community Tech to review. @Niharika I'm untagging us from this ticket. Can you lead the community discussion necessary to decide whether and how to implement?
Looks like this makes sense for the Translate extension, so I'm untagging CPT. Let us know if there's any issues with API integration.
Dec 9 2019
Dec 5 2019
@Pchelolo but we can rely on a library in core, right? Could we just depend on the Parsoid/PHP library, not the Parsoid/PHP MW extension?
Hey, @Pchelolo . Why does the cache have to be implemented within Parsoid/PHP? Couldn't it be implemented like...
@WDoranWMF I wonder if we could get data from analytics about this?
@BPirkle great point! I updated the schema on the wiki and the read-only endpoints, but I forgot to hit these. I think it's up-to-date now.
Dec 4 2019
@nnikkhoui I changed the "license" and "other_licenses" elements to objects, so we have some more options. Instead of just a SPDX code, we also have an URL and a name.
Dec 3 2019
This makes sense as a feature; using a single log line is probably fine here. We'll track this as it proceeds.
We've discussed this internally in the CPT group, and we don't see a big objection, and it seems like a nice benefit, especially for people who do a lot of page moving. We'd like to see you get some community discussion on this to shake out any possible bad ramifications before there's a patch ready to review.
So, we do have the concept of a wikibreak, which is probably a really healthy thing for a lot of users to plan and take. There are even tools like the Wikibreak Enforcer that help enforce these kinds of breaks.
I'm re-opening so I can go over the endpoint and make sure it meets the acceptance criteria. @nnikkhoui not a problem, but I try to do this for all the user stories.
Dec 2 2019
We discussed this in our kickoff meeting today.
Nov 27 2019
One thing Tim brought up was that we should look to MediaViewer and Parsoid to see what image data was needed for real-world API clients. Bill and I split up that task; I did MediaViewer.