Align existing code base with publisher attributes from the MVP
In our MVP call today , we altered the language that describes publisher fields. This task is to align the code to what we discussed.
Check the repositories section of the MVP page for up to date language.
#9 Updated by ttereshc almost 3 years ago
- Status changed from ASSIGNED to CLOSED - COMPLETE
- % Done changed from 0 to 100
Publisher model/serializer is correct and complaint with the discussed Publisher attributes for MVP, no changes needed.
auto_publish exists on the model/serializer.
It was suggested to discuss a need for auto_publish functionality in MVP after alpha release.
#11 Updated by mhrivnak almost 3 years ago
I think we are close to finalizing it and just need to discuss it a touch further. Jeff and I agreed so far that auto-publish makes sense to keep and is trivial to use.
We could try to get it added to the MVP, which would then make it clear. But the MVP is of course a minimum, and nothing stops us from strategically including additional things where they make sense. So we could just leave this in and use it.
Either way, let's keep it for now and discuss as necessary.
Please register to edit this issue