May 14 2019
Nov 21 2018
Nov 15 2018
@Jdlrobson actually @Jhernandez were just hypothetically discussing using MCR to hold a summary data that is editable by editors. So it is possible to have the summary actually be in the page, but we need product buy in on adding this user facing feature first.
Nov 11 2018
Oct 8 2018
Sep 25 2018
Sep 12 2018
Aug 24 2018
Jul 27 2018
From what is being said, it sounds like the main question that needs to be answered is:
Jul 23 2018
Created to track @Anomie's work… removing the parent task as it is not needed for SDC
Jul 17 2018
Adding Operations, but not sure where this task should actually go
Jul 12 2018
Jul 10 2018
@AndyRussG working on getting you some help here from one of the MCR engineers
@hashar thanks, so basically what we need to do is modify the config file to remove the jobs we no longer need, correct?
Jul 5 2018
Jun 26 2018
Jun 21 2018
Jun 19 2018
Just tagging Reader's Web for them to track
Jun 9 2018
Can you explain the use case for generator usage?
@Jdlrobson we should talk about your workflow so we can understand it.
Jun 7 2018
@WMDE-leszek no problem, thanks for looking into it!
Jun 6 2018
@WMDE-leszek can you say why this is blocked now? Just saw… thanks!
May 15 2018
@Dbrant is going to write a script to see if he can break the service by adding pages from every project that the app supports.
May 14 2018
@Pchelolo do you have any other objections or were you just looking to reuse schemas for consistency?
May 11 2018
May 8 2018
May 7 2018
May 1 2018
thanks all… we will keep this open and look into it again after we get the code base split up as @bearND suggests
Just a thought on the overloaded field...
Apr 30 2018
Adding @Lydia_Pintscher for visibility
Apr 27 2018
Apr 18 2018
@bearND are we good to close this?
FYI I moved this to the kanban board to do column, but you don't have to do this before other work, just wanted to resolve the open question
All of these solutions are fine with me…
As far as suggestions, either per project or an aggregate end point both work for me.
Apr 17 2018
@Mholloway The part I'm not sure about is that this seems to be implicit. -1 and -2 does not clearly mean "non-editible" without knowledge of Parsoid's/MCS's business logic
Apr 9 2018
Bikesheding… I'll be more disciplined about opening tickets
@Mholloway has this been addressed in your Media API work
Just handling this in the thumb API
Very open ended and not actionable. If we want to reopen, lets make a specific ticket to implement.
@bearND is this still an issue?
Also do we maintain it?
@bearND is this within the MCS codebase or separate?
Apr 4 2018
@Mhurd yes, prioritize this over the references!
Apr 3 2018
Apr 2 2018
I get that it’s in a different hierarchy but it’s odd to have the only api that delivers media not under the media hierarchy.
How about just site/css?
Sorry for coming in late here. But I do have an objection with using media. We have another api named media so that’s kind of confusing
Mar 28 2018
Mar 26 2018
I'm going to do research on this in the near term to figure out what the path forward is
So is this something we should address in the PCS @bearND
Is this in references to the Summary service? Or mobile sections?
Mar 23 2018
For context: We have lots of client code with work arounds for getting the right sizes of images. So much duplication and bugs. We want to get rid of this code in the client and instead use this much more flexible proposed API.