Talk with the HyperThought team about using our template file format.

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by clarifying the proposed .ez template file format with the HyperThought team, as requested in the issue title. Then identify the server-side entry point and existing file-upload or metadata-tagging flow in MetaForge. Done should include an agreed parser scope and demonstrated handling of the format.

Written by the indexing model from the issue text.

Description

Maybe we can write a server-side .ez parser.

Dominant language
Python
Stars
2
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlueQuartzSoftware/MetaForge

All issues in BlueQuartzSoftware/MetaForge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.