DG: release it!

DiaGrammar (App)

App sales flow

End responsible: Gregg (aka "The Manager")

Code

• Toomas, with support from Qingtian for Red fixes.
• ?? Backup dev - let's park this until after release until we know better what's next.

Licensing Code

• Done.
• Uses https://orders.redlake-tech.com/validate.rsp

Who: Will (server), Toomas client?

Build

• TBD Define what goes into a release (examples, metagrammars, other files) (Toomas & Gregg)
• TBD Lock down format (Single EXE, self-extracting zip, zip) (Toomas & Gregg)
• We can do the first release manually, but then should write a script to automate it. (Toomas & Gregg)

Code Signing

Ready.

• Gregg, backup person will need a hardware key. See code-signing repo for details.
• https://github.com/Redlake-Tech/code-signing
• who: Toomas, backup Maarten, Gregg Action: hardware keys + instruction to backups

Deployment

• Releases get uploaded to Paddle and get a product ID. The product and vendor id are used in the webshop pages to get to the right product: Gregg, backup Maarten

• ?? We should maintain an historical archive. Where? Same goes for videos, and whole website. We need a file storage service for that, I think. Dropbox/OneDrive like service?

• ?? Who does the archiving? And WHEN do we do this. I'd say, the who is less important. When: every dot release for exe, website we'll need to determine, videos - Maarten

• What is the flow: -- Call for freeze, test (Gregg) -- Sign off on a build of the EXE (Gregg, Toomas) -- Gregg signs the EXE (Gregg) -- Build a deployment package (Gregg or Toomas) -- Test package/installer outside web flow (All) -- Upload package/installer - redlake account owner == Greg, backup Maarten -- Write release announcement for web site. ??Who??

Server/API/Shop

• https://github.com/red/web-redlake-shop
• APIs are served by Cheyenne
• @Warp handles it all right now - BACKUP needed.
• ?? where are the Dockers deployed
• ?? who handles the email addresses in GSuite, like sales@
• ?? are the emails complete (we have sales and noreply)

Showstoppers

• Static website: video in place of image
• Static website, link to order page in stead of red-lang.org
• the final order page hangs on the "spinner" (Adam, Will)
• redlake-tech.com paddle.io account (Gregg)
• ??we have not given any ideas about the showstopper account - (what does this mean?)
• who watches these inboxes?

Web Site (Redlake DiaGrammar pages)

• https://github.com/red/web-redlake
• Link to order page instead of red-lang (Bolek?)
• intro video instead static image on top of page (Bolek?)

TBD

• Look at the above, make sure there are secondaries
• "keys" should always be accessible to a backup person
• static/order-website integration

Design

• Done.
• We lack Hugo expertise. Changes will be hard until someone gets trained or hired.

Static Content

• TBD Gregg to complete. Who does proofreading?
• make sure video is there and link all go to the right destination

Dynamic Content

• Blog entries, tutorial videos, examples (Maarten): 5 blog entries and 15 videos ready, but need second iteration to support multiple grammars
• Videos to go on a YouTube Channel, not in the site repo. Private for now. Do we have a Redlake video channel? He he, see below
• !! Gregg to set up Redlake YouTube channel

Shopping Cart Integration

• !! Gregg to get Redlake account set up with Paddle (needs site to be ready)
• shopping cart is non-sense, best we can do is more than one copy with these one-off products. Needs research.

Deployment

• TBD change to deploy from Master, not Shop branch.

Hosting and Admin

• G Suite
• Email addresses: [email protected], [email protected], [email protected], [email protected] (Maarten or Will, are these all correct, and where do we manage creds?): Maarten says: we miss support, we all have access, but who actually watches which address?
• Docker (where does it run, who has keys?)

Shopping Cart

External Services

• Paddle.io, G Suite, mailgun
• shopping cart: iteration II

Showstoppers

• After order, we do not go to a landing page, but see the spinner indefinitely (Will, Adam)
• Minimal docs on how to deploy the dockers (Will)
• static website in place as described above (??)
• localhost (dev) shop workflow gives errors/blank pages. Needs fixing, as we can't develop/bug fix this way (Will?)
• acquire Redlake Paddle account (Gregg)

TBD

• turn this list upside down, so we can lookup who is responsible for what and if the load is fairly balanced.

External Services

• G Suite
• Paddle
• Github
• Notes
• the docker container run
• mailgun

Server Side license validation

• https://orders.redlake-tech.com/validate.rsp- Will (Maarten backup)

Client Side

• DG hits https://orders.redlake-tech.com/validate.rsp
• Key stored locally (cached). Who: Toomas client

Team

• Gregg (PM)
• Toomas (App Lead)
• Maarten (Glue, Marketing)
• Will (Server, Admin)
• Adam (Web)
• Bolek (Web, test)
• Endo (Test)
• Qingtian (Red)