> On Mar 3, 2026, at 4:55 AM, Henrik Ingo <[email protected]> wrote:
>
> I believe the process is actually to move the current repo so that history
> is preserved. And once approved in this thread (or a separate vote), this
> can be accomplished with an INFRA ticket in Jira.
>
> Another process question: Can we have this code in the project without
> incurring the overhead of release bureaucracy?
Everything in a release should be in the repository, but not everything in the
repository must be in the release.
> Essentially we should think
> of this as an interactive part of our website, not an app that produces
> pypi modules.
Cool.
Best,
Dav e
>
> henrik
>
> On Tue, Mar 3, 2026 at 12:58 PM Joe Drumgoole <[email protected]> wrote:
>
>> Hi,
>>
>> Can we create a new repo for the otava-test-data repo under the Otava
>> project and I will submit a PR to check in the demo code.
>>
>> I propose that we actually call the repo "otava-demonstrator".
>>
>> I will update the package names and other identifiers to align with this if
>> people are in agreement.
>>
>> regards,
>>
>> Joe.
>>
>>
>> --
>>
>> Joe Drumgoole
>>
>> +087 2995547
>> https://bsky.app/profile/joedrumgoole.com
>>
>
>
> --
> *nyrkio.com <http://nyrkio.com/>* ~ *Continuous Benchmarking as a Service*
>
> Henrik Ingo, CEO
> [email protected] LinkedIn:
> www.linkedin.com/in/heingo
> +358 40 569 7354 Twitter: twitter.com/h_ingo
