Comments (5)
Hi and thanks for opening an RFC. Due to the holidays it will take a bit longer than usual to evaluate the RFC, apologies! I expect this will be picked in the new year.
from sofie-core.
Hi @ianshade and thanks for waiting while we have been on break and evaluating this.
Let me start by stating that we absolutely support the use case of creating adlib actions for a rundown/playlist through an HTTP API such as the one contributed in #1070, however.
Currently there is a limitation that we would like to lift: Buckets and their AdLibs are global to a Studio, which makes all Adlibs within a Bucket visible next to any Rundown Playlist in that Studio
NRK has decided against lifting this limitation right now. This limitation is a core part of the design of the buckets as their intention is a storage place across rundowns for adlibs that a user wants to reuse. Whilst lifting that limitation is fairly trivial from a code viewpoint, we do not have the infrastructure in place to support such conceptual changes long-term and as such it is extremely likely we will break it in the future. Past experiences have taught us that, while it seems like a small detail, it can easily cause rifts across team members and contributors.
Internally in NRK I will propose evaluating how we can start to accept contributions on conceptual matters, as I believe that with a growing number of contributors we will have to be able to do this at some point. So please be assured that this is something we want to be better at.
In the meanwhile, we would love to help you find an alternative way to support your use-case for this change. Some things come to mind such as implementing an (http) API to create rundown ad-libs. Or if you are using a custom ui, perhaps some metadata can be stored on the bucket ad-lib and you can filter for that instead. If you are interested we can set up a time to workshop some of these ideas and I can involve some of the experts from the NRK team on this. Just contact me at [email protected]
from sofie-core.
@mint-dewit thank you for the answer. Could you please share some insight into what might change about the Buckets in the foreseeable future that would make the proposed addition prone to breaking or hard to maintain in subsequent releases of Sofie?
from sofie-core.
Ah, the issue isn't so much what we are planning to do about the Buckets in the foreseeable future, I apologise if that wasn't clear from my initial explanation. What we need to take into consideration when evaluating the RFCs is more so about the entire system of Sofie and how the different features interact and are separated on a conceptual level. We understand that this stuff is poorly documented and we do apologise for that. We will look into improving this documentation.
As we really want to see you succeed, we would love to invite you for a workshop to talk about these larger designs and also about how to implement this use-case. Would Tuesday 2pm CEST work for you? Feel free to reach me on any platform to discuss a date and time.
from sofie-core.
Thanks @mint-dewit, this won't be necessary. I'm closing this RFC as the proposed change is no longer needed.
from sofie-core.
Related Issues (20)
- RFC: This is a test
- RFC: This is a test
- RFC: Changes and addition to (meta)data properties (SOFIE-2797) HOT 5
- RFC: Updating the Looping Feature with Per-Part Looping HOT 9
- RFC: Removing potentially unused feature: 'Preserve contents of playing segment when unsynced' HOT 5
- Bug Report: Runaway playhead (SOFIE-2899) HOT 3
- RFC: Override NRCS Data in the Sofie GUI HOT 7
- Bug Report: AutoNexting missed Parts after Playout Gateway downtime HOT 1
- RFC: Improve GUI Accessibility HOT 1
- RFC: iNews compatiblity with segments HOT 5
- Bug Report: "debug_playlistRunBlueprints" breaks 'Reload NRCS Data' HOT 2
- Bug Report: Pieces reported as stopped when they're not
- Bug Report: Package statuses incorrectly get changed when set as next HOT 4
- Bug Report: Diff Different between (SOFIE-3004) HOT 1
- Bug Report: Inital Sofie Core Setup : Issue with Persistant Storage HOT 6
- RFC: Picking future technologies HOT 4
- RFC: Segment budget timing as primary timing in Sofie HOT 1
- RFC: Server-side notifications HOT 2
- Bug Report: Device Triggers temporarily go blank HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sofie-core.