Tim and TJ make decisions on fundamental concepts of Paranext:

• Repo structure
• How will PT9 and Paranext interoperate?
• How will we leverage existing PT9 code?
• C# Extensions?
• New API endpoints vs extend existing API endpoints
• Node vs Deno
• How much core Paranext will be made of extensions?
• RTE - starting point and data format
• How to deal with project-scoped extensions?
• Extension ecosystem - how are extensions found without curation?
• gRPC vs REST/Web sockets vs Web sockets
• How to keep UI consistent?
• What extension DX features are we aiming for?
• C# or Node as primary webserver?
• Web server or Electron-Edge?

As an architect I want to know if there is an easier path to defining an extension framework.

Investigate the possibility of finding and using an extension framework for Paranext.
Time boxed to 3 days.

As an architect, I want to know how well Node would suit us as a web server technology as opposed to C# to determine if we should use a C# web server or Node web server (assuming we do not go with Electron-Edge as referenced in #9).

• Are we limiting ourselves using Node websocket as opposed to a C# websocket?
• How do startup and resource use look between C# and Node?

Under what organization is our shared drive? SIL? Other? Who has to take the expense of hosting files? Will SIL always be willing to pay? Does that create any weirdness ownership-wise? Who has access if SIL creates it?

Create shared drive.

As an architect I need to have a working example of a cross platform build.

Develop an application UI shell (an empty application frame) that can be built and deployed to Windows, Linux and Mac.
All necessary code should be checked into this repository.
Include a build on demand system for all three platforms.

• Add electron-react-boilerplate
• check x-platform builds through GHA
  Move to a new card for a future sprint
• Add .NET Core
• check x-platform builds through GHA

The team would really like a long term name for this product. It seems like their is an organizational level decision on whether this will keep the name Paratext or assume a new name.

• If we would use a new name we could open up polls to organizations on coming up with a name.
• If we keep the name Paratext, we need some sort of way to distinguish this application from Paratext 9.

As an architect, I want to know if forking Node processes to call C# asynchronous code is a viable solution to determine if we should try Electron-Edge as our base architecture.

• How costly is forking Node processes? Startup time, memory cost
• Can we reuse Node processes and call different asynchronous C# methods?
• Can we create an interface that hides implementation details of "asynchronous" forking and calling C#?
• Can we start threads that continue to execute in C# after returning to edge? Can we subsequently check those threads for completion or errors?

As an architect, I need to know the license we are putting on our new code in order to start working on open source repositories.

We need to set the license file on each repository appropriately.

Integrate the Proskomma library to parse USFM data into JSON.
Chris Hubbard can be a resource for learning more,