Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Attendees

Gary Oberbrunner, Dennis Adams, Pierre Jasmin, J-P Smith, Paul Miller, Peter Huisma

Minutes

Meeting called to order at 11:07am EDT

ASWF Business

  • Discussed Meeting Management
    • What do people need to do to subscribe to meeting reminders?
    • Need to send proper meeting link to ASWF calendar (requires a LSF account to see the actual link)
    • Action: Gary to discuss with John Mertic, document meeting management process
  • Association wind-down:
    • Peter reports:
      • all outstanding bills are paid
      • accountant is paid
      • waiting for info from UK tax repayments from prev yrs
      • When we have that, we can continue the dissolution (accountant will file wi/ Company House)
      • John preparing closing of bank account - waiting for tax repayment info
      • Final balance is around £1600 (plus tax refund, which may be £1-200)
    • Then donate to ASWF; J-P asked John about how to send £ to $ account. J-P knows of an exchange-efficient method.
    • May take a couple of weeks or months to get the Companies House filing complete, depending on tax office
    • Companies House filing takes two months to finalize and strike off records
  • Charter is approved
  • IP transfer is complete
  • Now we can reassign github and change copyright messages (use script)
    • Action: Gary will do these with John Mertic
  • Mailing lists:
    • move discussion group content
      • 29 subscribers on new list, 89 on old discussion list
      • Action: Gary will follow up w/ John M re: transfer mailing list content
    • We have 48 members on the slack channel
    • 34 members on the discord
    • Agreed to not migrate directors' list, but try to migrate members' list content as well as discussion list
  • John M will "put us on the list" for new website
    • Old minutes need to be transferred
    • Don't want to lose old content
    • John proposed a new wordpress site
    • Domain would still be openeffects.org
    • Various types of content on the old site:
      • docs
      • minutes
      • marketing
      • standard discussions -- can be archived
        • Action: Pierre will review old standard discussions to see if we're missing anything on github
      • remove contact form & sign-in
    • Will establish a subcommittee for this when appropriate

Technical Discussion

  • Getting new TSC members, contributors, and eventually committers:
    • Action: Pierre will reach out to Frederik Devernay, Foundry, Autodesk, also Blackmagic (Rohit)
    • Action: J-P will reach out to Mistika (Roman)
  • J-P asks: should we review open github issues? Only 19, but we should also review all PRs
    • Actions: followup (more info), accept, reject, transfer...
  • Agreed to schedule this discussion for next TSC meeting
  • Also we would like to have detailed tech discussions on particular proposals
  • Dennis notes that OSL is talking about color space too, so this is becoming a bigger topic in the community
  • It was noted that collaborations are important and we can play a role there
  • Action: Pierre will create a list of all topics we've discussed over the years that don't have current issues or PRs
    • Some of these are too amorphous to be issues yet; need more discussion
  • Discussion of next meeting's agenda:
    • 10 min for ASWF admin
    • 30 min for reviewing github issues and PRs
      • don't have detailed discussions
      • for PRs, a decision clearly has to be made -- actionable
    • 20 min to review Pierre's list
  • Following meeting(s): focus on 1 or 2 bigger tech topics, maybe with guests
    • 30+ min for a topic
    • Invite others e.g. OSL, OTIO, host vendors, etc.
  • J-P has an idea: sometimes OpenFX nodes want to do things outside of plugin instance, e.g. manipulate another node in the tree via the host's scripting language:
    • Idea: add a new suite w/ one function, "executeScript" -- host-specific language/format, but generalized execution method
      • Plug-in would have to know details of host to know what script to pass to it for execution
    • Alternative idea: two related nodes could talk to each other, but J-P's idea is different because it's more general – a node can do anything the host supports, but it's host-specific
    • If the goal is to add metadata to other nodes, what about using a structured data format that's host-independent?
      • Code-based model is easier than trying to define a structured data format to talk to other nodes
      • Code-based model would be much easier for hosts to support
    • Alternative: private script suite per host
    • Motivation: Recognizing we can't do everything in OFX, so provide an "escape hatch"
    • When would the script be executed? Probably during interacts, probably not during render
    • Is there bidirectional data transfer? Can scripts return anything to the executing node? Is the script executed synchronously or async? If async, can the node get a callback when complete?
    • Action: J-P will follow up w/ BMD, see if they're interested in investigating further

Meeting adjourned at 12:15am EDT

Video recording: to be provided when ready


  • No labels