llnl / llnl/spotbe

Move spotdb into own project?

Open
#18 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3
Forks
3
PR merge metrics
No merged PRs in 30d

Description

The "spotdb" (which is actually a caliper database) could be useful for other projects - could we move it into it's own module proper, and perhaps branded with caliper so it's clear that's what it's serving? Let me know what you think!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the spotdb implementation and its current callers in the repository; the issue does not name files, tests, or entry points. Determine how the caliper database is coupled to SPOT and what moving it into a standalone, caliper-branded module would require. Done means the scope and module boundary are agreed, with any affected integration points identified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.