The latest version is in the nyrkio repo. Henrik should be able to grant access to that.
Joe Drumgoole +087 2995547 https://bsky.app/profile/joedrumgoole.com On Wed 27 May 2026, 20:08 Alexander Sorokoumov, < [email protected]> wrote: > The latest comment in the ticket > > https://issues.apache.org/jira/browse/INFRA-27966?focusedCommentId=18083921&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18083921 > : > > > if you'd like, please add my GitHub user (dfoulks1) admin access to the > jdrumgoole org and I'd be happy to get that taken care of for you. > > Joe, can you please do that? > > Thanks, > Alex > > On Tue, May 26, 2026 at 8:40 PM Alexander Sorokoumov < > [email protected]> wrote: > > > Oops, I did drop the ball on this thread, apologies for that. I have > > finally created a ticket to move otava-test-data to > apache/otava-playground > > - https://issues.apache.org/jira/browse/INFRA-27966. > > > > Best, > > Alex > > > > On Mon, Mar 30, 2026 at 2:33 AM Henrik Ingo <[email protected]> wrote: > > > >> +1 > >> > >> On Mon, Mar 30, 2026 at 1:15 AM Alexander Sorokoumov < > >> [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. > >> > > >> > Before filing INFRA ticket, are we in agreement about a separate > >> > `otava-playground` repo? > >> > > >> > Best, > >> > Alex > >> > > >> > On Wed, Mar 18, 2026 at 1:22 AM Joe Drumgoole <[email protected]> > >> > wrote: > >> > > >> > > That name is good. Setup the repo and I will move the code over. > >> > > > >> > > > >> > > Joe Drumgoole > >> > > > >> > > +087 2995547 > >> > > https://bsky.app/profile/joedrumgoole.com > >> > > > >> > > > >> > > > >> > > On Tue 17 Mar 2026, 20:02 Alexander Sorokoumov, < > >> > > [email protected]> wrote: > >> > > > >> > > > After thinking about it for a bit, I do believe that a separate > >> repo is > >> > > the > >> > > > best way forward. > >> > > > > >> > > > A considered alternative was to go full monorepo, where both the > >> > > > demonstrator and the website are pulled into the main repo. This > >> option > >> > > may > >> > > > become interesting after version 1.0.0, but would be IMO premature > >> at > >> > the > >> > > > moment. I'd rather invest our limited resources into other > >> initiatives > >> > > > (architecture discussion, documentation, releases, etc). > >> > > > > >> > > > As a bike-shading suggestion, wdyt about otava-playground as a > name? > >> > > > > >> > > > Best, > >> > > > Alex > >> > > > > >> > > > On Thu, Mar 5, 2026 at 10:18 AM Henrik Ingo <[email protected]> > >> wrote: > >> > > > > >> > > > > On Thu, Mar 5, 2026 at 8:13 PM Alexander Sorokoumov < > >> > > > > [email protected]> wrote: > >> > > > > > >> > > > > > One thing to consider is do we ever want to release/publish > >> > > > > otava-test-data > >> > > > > > to PyPi? If the answer is yes, then a separate repo is the > best > >> > > choice > >> > > > > IMO. > >> > > > > > If the answer is no (e.g., we don't release the website), then > >> the > >> > > > > location > >> > > > > > matters less as per Dave's comment. > >> > > > > > > >> > > > > > My proposal is not to release it. Not that it couldn't be > >> released, > >> > > but > >> > > > > at > >> > > > > least for the foreseeable future, it's not worth the overhead > >> > involved. > >> > > > So > >> > > > > yes, this is why it aligns with otava-website repo and not > otava. > >> > > > > > >> > > > > > If in the same repo, would they then be subject to > consideration > >> > and > >> > > > > voting > >> > > > > > for release? And, how would that work, wrt release artifacts? > >> > > > > > > >> > > > > > Highlighting a potential painpoint. Doesn't matter much to > me. > >> > > > > > > >> > > > > > >> > > > > Exactly. We would have to make sure the demonstrator doesn't get > >> into > >> > > the > >> > > > > release tarball, or if we do include it, we actually have to > test > >> it > >> > > each > >> > > > > time. > >> > > > > > >> > > > > henrik > >> > > > > > >> > > > > -- > >> > > > > *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 > >> > > > > > >> > > > > >> > > > >> > > >> > >> > >> -- > >> *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 > >> > > >
