> But we already have the website in a separate repo: > https://github.com/apache/otava-website
> So can we move over Joe's repo and call it apache/otava-demonstrator? 2c: I plan to open a proposal to move the website to the main repo. It hasn't been fun to maintain it in a separate repo, especially copying docs updates. It is also harder to discover for new contributors. Finally, it may be tiring to keep docs in otava and website docs in sync if someone steps up to improve the overall state of documentation. Just a heads-up, that we may want to take the current state of otava-website as an example to follow. Best, Alex On Wed, Mar 4, 2026 at 2:02 PM Dave Fisher <[email protected]> wrote: > > > > On Mar 4, 2026, at 1:57 PM, Henrik Ingo <[email protected]> wrote: > > > > On Tue, Mar 3, 2026 at 7:28 PM Dave Fisher <[email protected]> wrote: > > > >> > >> > >>> 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. > >> > >> > > But we already have the website in a separate repo: > > https://github.com/apache/otava-website > > > > So can we move over Joe's repo and call it apache/otava-demonstrator? > > Sure. Do you need guidance? > > Best, > Dave > > > > > 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 > >
