Scripto, itself, is based on etherpad-lite, with a ton of other code added to support various other features necessary to support the shows and was written by some contract employees.
Depending on what is in your git repo, please don’t be the next Uber - if you had any secrets in your repository (even historical), definitely roll all your API keys and check secrets/credentials etc.
Thankfully that was just our marketing site! Our team has fixed it (and re-issued any api key that could have been potentially compromised).
Our product isn't a monorepo (and has a much more rigorous release process than this site), so even if the main repo that does the build is ever exposed, the secrets aren't in there :)
The new version we are working on (and briefly mentioned) is based on choo[0] with the editor provided code-mirror[1] and ot-delta[2] from quill with some custom (and soon to be open sourced) glue code to make them work together.
When I was in news television in ~2005, we dabbled with replacing iNEWS with something Web-friendly and nice, but the Web landscape just wasn't there. It seems like a million years ago, in terms of the Web. Our frustrations were the same, since iNEWS and ENPS are just slightly different flavors of shit sandwich, and while a typical ENG rundown can plod along with one-active-writer-per-slug the editing locks were starting to really get in the way of some other things we wanted to do. Reading this was just like being back in those meetings.
Nice to see someone have the exact same idea and execute well. If you wanted to take on Avid, I bet you could firm up some ENG-type integrations (wire integration would be a showstopper) and get some traction in newsrooms, all of whom are having their thin budgets bled by AP and Avid. MediaCentral is a hot pile of garbage, I hear, so Avid might be handing you the opportunity as we speak.
Showrunner has a big challenge in front of it taking on the Final Draft religion, but man, if you guys crack that nut...