Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan Spec-Up-T and Spec-Up integration #68

Open
henkvancann opened this issue Dec 16, 2024 · 2 comments
Open

Plan Spec-Up-T and Spec-Up integration #68

henkvancann opened this issue Dec 16, 2024 · 2 comments
Labels
feature New feature or request maintenance A maintenance issue to be picked up at regular maintenance weeks

Comments

@henkvancann
Copy link
Collaborator

Hi all,

@kordwarshuis and I are honored to be admins of spec-up.

Our approach to integrate Spec-Up-T and Spec-Up:

  1. synchronize / update bundles
  2. NPM install instead of the old way
  3. Make it optional to take the terminology engine
  4. Address the open issues
@henkvancann henkvancann added maintenance A maintenance issue to be picked up at regular maintenance weeks feature New feature or request labels Jan 14, 2025
@henkvancann
Copy link
Collaborator Author

In relation to point 3

What: The regular current def-ref for terminology is the minimal solution. We suggest enjoying the Spec-Up-T Terminology engine.

Why: To offer a choice

|Who: anyone used to DIF Spec-Up

When: Available after the integration

Which way: One-way system, you can upgrade Spec-Up to Spec-Up-T, downgrading (T to old one) will be hand work, content is involved. The directory structure and functionality is different, etc.

@henkvancann
Copy link
Collaborator Author

Topics related to point 1

It is an arbitrary categorization.

  1. Client-side
  2. NodeJS
  3. Specs.json simplification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request maintenance A maintenance issue to be picked up at regular maintenance weeks
Projects
None yet
Development

No branches or pull requests

1 participant