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. On Thu, Mar 5, 2026 at 2:58 AM Henrik Ingo <[email protected]> wrote: > On Thu, Mar 5, 2026 at 12:26 AM Alexander Sorokoumov < > [email protected]> wrote: > > > > 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. > > > > > > Thanks, and that is a timely comment. > > IMO the docs section of the website should be somehow automatically be > extracted from the markdown in the main repo. For example the main repo > could be a git module for the website. > > So I wouldn't necessarily want to merge the otava-website into otava. But > if we don't want to have lots of separate repositories, then I would rather > park the otava-demonstrator inside otava-website, but not the main repo. > > 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 >
