2023-03-18 | Open5e_MeetingNotes

[Schofje]

2023-03-18 | Open5e_MeetingNotes

Practical Info

This is a meeting where we discuss the implementation and interaction regarding Open5e.
Any contributor (UI/UX, designer, writer, programmer..) is welcome to attend!
For users and other parties, we recommend to read the notes and comment down below so that the meeting stays focused.

Date/Time: 2023-03-18, Saturday, 19:00 UTC
Meeting location: Discord

Links

• API
• UI

attendees:

• Ean Moody (EapMoody)
• Hannah Ümit (ProtofrogUH)
• Greg (Gredelston)
• August
• Christian (Grin)
• Rhonin_Wanderer
• Thel
• Mike (Slyflourish)
• Sturlen
• David (dpro)

Topics

Summary and Welcome

• Welcoming all the folks from Slyflourish!
• What is Open5e? and what it isn't.

The current state of the project

• Addressing the architecture.
• The cleanup required to progress further.

Potential New Site Projects.

• Improved creature, item, and spell searches.
• Global source selection.
• New projects as modules.

New API projects

• Images for Monsters & Items.
• Adding supporting info for existing items.

Meeting Notes

The team's specialties

• August developed the deployement and other tools in the past few years.
• Hannah is a filmproducer, worked at a few art conventions before. Still a student.
• David is a software engineer fluent in React, Typescript, Terraform, Docker, Python, Django and AWS.
• Christian is a frontend developer. more familiar with React than Vue.
• Greg is a developer at google working on the deployment of ChromeOS, has experience in python.

What is open5e and is not

• Ean introduces open5e as a learning project and removing loophopes and workaround for accessing. It is to give good reliable data so people can make content in the open5e ecosystem.
• Not an ironclad principle: It is focused on supporting the official stuff, not a social media tool. Not providing user generated content due to moderation. It is a community project, not a business.
• Husky, github actions are an options to think of to standard.
• The content is under CC-BY-4.0 and OGL.

Technical side of Open5e

• the API is meant to stay clean.
• Once things are online, they are staying online. No removals that break things on the website.
• Clean, simple fast and keeping it open source so that is accesible.
• Currently on Vue2, it is a hurdle to update to 3 currently.
• Currently deploys to heroku, github pages probably better solution on the long run. Plan is to stop using Heroku, due to being pushed to Enterprise tier. CI/CD will be changing.
• Developing the loading in the data for the searches is the biggest one to work on.
• Eslint is according to David, Christian and Ean the right tool for frontend analysis.
• Dependencies are quite old.
• Need help on updating python (currently 3.8, on August's machine it works on 3.11)
• Front end could be dockerized.
• How do we want to improve custom info we want to add to it, there is no way to tackle it as of currently. Any suggestions are open.

Artwork and images

• AI is currently controversial, there is still discussion about copyright and ethics. Takes long enough to discuss it.
• Major publishers are the bar for developing content. (Kobold Press, WotC)
• Mike knows the person behind inkwell ideas. He wants to approach him to see if it's all good to use it, the art is inconsistent but it is already is done.
• An editorial role to set the barrier of entry to develop extra content, give feedback to them and moderate content. Mike is cool with checking it occasionally but does not have much time. Once we have a workflow established, he is cool with advertising checking data quality.
• A line shader is possible to be used with 3D models contributed by Miguel. With this kind of line shaders. Simplicity is the more effective way. https://kdedene.gumroad.com/l/tcKOI
• Greg asks Tension in art: do we really need it? Since open5e is not supposed to be opinionated, artwork will be serving us and the consumers better. August explains that it is better and has more impact with images. Greg wants to imply the exception as much as possible.

Current tasks

• Greg finds style in code very important due to the amount of contributors, wants to build the styleguide.
• David is interested in working with the infra.
• Toggling settings on the site level is a current goal.
• An easy and non-programmer way to extract data from sources or contribute their own idea.
• Character creation is not out of the line.
• Discord is a place to talk about design, discuss, go fast through it. Once things settle thing down, we'll moving it to Github.
• Styleguide (webdesign) isn't developed for the website.

Next meeting: 202#-##-##, Weekday | Online

Topics