rdswift: I do remember it being a rocky road re. moving the docs… but I thought we wanted to start moving some this year, at least. In any case, mayhem and I are very keen to have it happen! ping me if there’s anything I can do to help
2024-05-06 12704, 2024
aerozol[m]
I’m going to update MBS-13395 with what was last discussed - in the Dec 2023 meeting topic - it looks like we were able to agree on some things that could be moved when/if you’re ready and keen (fingers crossed)
ansh: monkey: listened to an album and a weekly exploration today, using BrainzPlayer w. YouTube! SMOOTH!! 🥳
2024-05-06 12722, 2024
glguy has left the channel
2024-05-06 12726, 2024
minimal has quit
2024-05-06 12741, 2024
rdswift
aerozol, here is what I had started. https://musicbrainz.readthedocs.io/en/latest/ I tried to start with the new user stuff, style guides, database and server stuff. Still lots to do, but there is a good chunk already there.
2024-05-06 12727, 2024
rdswift
If you think it would be better splitting up the user documentation from the technical things (database details, server setup, etc.) that can be fairly easily done (but I think it would need to be done in separate repositories). Perhaps a good starting point would be an outline of the desired site (topics, sub-topics and what links to what) so it's clear what to build. I basically just started with the existing stuff in the wiki.
2024-05-06 12706, 2024
aerozol[m]
rdswift: Do you think the sidebar will stay manageable with editor and technical/dev content in the same site? I find it very confusing on the wiki, but it looks okay on the site you’ve already made (I suppose if there’s a lot still to add that could change)
2024-05-06 12702, 2024
rdswift
We could include all the developer stuiff
2024-05-06 12721, 2024
rdswift
Opps, lets try that again... :-)
2024-05-06 12736, 2024
aerozol[m]
For instance, if a editor is looking for style guidance on the wiki, and they type ‘release’ into the Wiki search, they will be directed to: https://wiki.musicbrainz.org/Release (they would have to know to do a deeper search to find the styleguide)
2024-05-06 12701, 2024
aerozol[m]
I might be overcompensating by imagining two ReadTheDocs with slightly different colour schemes to let users know where they are
2024-05-06 12735, 2024
rdswift
That could be done. Have you tried the search on what I have so far on readthedoce? Try entering "release" for example.
2024-05-06 12709, 2024
rdswift
(in the search box at the top of the left sidebar.)
I’m being called away from the keyboard for the next 30min sorry!
2024-05-06 12723, 2024
rdswift
From what I recall, there was a plan / desire to maintain the database technical documentation in the database itself, so that would be removed. The only other thing that we might want to include would be the api documentation, but I suppose that could be in a separate rtd site (although I would be tempted to include it on the main rtd site either as an appendix or separate section near the bottom of the sidebar navigation tree).
2024-05-06 12736, 2024
aerozol[m]
re. splitting the styleguide from docs, I guess we would have prominent links in the menu to go between the two (and on some pages as well)
2024-05-06 12720, 2024
rdswift
Yup. Actually, I have to run now as well. Perhaps we can discuss more tomorrow.
2024-05-06 12709, 2024
aerozol[m]
rdswift: Sounds good - let me know if there’s anything I can do in the meantime. I’m getting a bit focused on details, but if push comes to shove I think we can use what you’ve already done, which looks good to me!
2024-05-06 12711, 2024
aerozol[m]
p.s. I had a little bit of a search for using different themes for sections within the same site, but no luck (thought this might be a good way to differentiate the styleguide pages)
2024-05-06 12737, 2024
Techman has quit
2024-05-06 12747, 2024
Techman joined the channel
2024-05-06 12757, 2024
Techman has quit
2024-05-06 12710, 2024
aerozol[m] has quit
2024-05-06 12709, 2024
yellowhatpro joined the channel
2024-05-06 12751, 2024
Techman joined the channel
2024-05-06 12729, 2024
zerodogg has quit
2024-05-06 12736, 2024
SigHunter has quit
2024-05-06 12745, 2024
SigHunter joined the channel
2024-05-06 12733, 2024
zerodogg joined the channel
2024-05-06 12712, 2024
reosarevok
yvanzo: when around, maybe we can keep trying to figure out that Perl PR :)
This report has been created in 2011, might have some other changes make it irrelevant in the meantime?
2024-05-06 12717, 2024
monkey
ansh: I deployed LB#2858 to test.LB, and I can't reproduce the issue you mentioned where the playing-now listen disappears. Can you try it too and confirm please?
reosarevok: perhaps there was a bug that caused actual gaps in the track positions, and the report was added to fix them? there isn't any information in the commit message to tell, but it doesn't seem useful now
2024-05-06 12730, 2024
reosarevok
I mean, theoretically having a report that looks for missing *numbers* could make sense
2024-05-06 12751, 2024
reosarevok
But that would need to I guess at least support a letter + number, and A / AA / B
reosarevok: you don't have write access to mb-solr?
2024-05-06 12743, 2024
reosarevok
Apparently not
2024-05-06 12719, 2024
reosarevok
So ENV MB_SOLR_TAG dbd709a in docker/templates/Dockerfile.tests.m4
2024-05-06 12721, 2024
reosarevok
Right?
2024-05-06 12715, 2024
bitmap
actually that doesn't work, we do need a tag or branch name
2024-05-06 12750, 2024
bitmap
master should be fine for now then
2024-05-06 12750, 2024
reosarevok
Hmm, ok
2024-05-06 12753, 2024
KassOtsimine has quit
2024-05-06 12753, 2024
KassOtsimine joined the channel
2024-05-06 12753, 2024
MonkeyPython joined the channel
2024-05-06 12736, 2024
zerodogg has quit
2024-05-06 12721, 2024
reosarevok
Ok, and then rebuilding the image
2024-05-06 12754, 2024
bitmap
yep
2024-05-06 12704, 2024
bitmap
I added coreteam to the mb-solr repo, so you should have access now
2024-05-06 12730, 2024
reosarevok
Thanks
2024-05-06 12719, 2024
reosarevok
Remind me, where are the docs for test images, which I know exist because I have followed some time?
2024-05-06 12745, 2024
bitmap
in HACKING-PROD
2024-05-06 12745, 2024
reosarevok
Oh
2024-05-06 12750, 2024
reosarevok
Yeah, just found them
2024-05-06 12734, 2024
bitmap
you can clobber the existing tag since this change shouldn't break other branches using the tag
2024-05-06 12701, 2024
reosarevok
So just recreate v-2024-04.pg16-perl5.38 ?
2024-05-06 12737, 2024
bitmap
yep
2024-05-06 12733, 2024
reosarevok
bitmap: "the --mount option requires BuildKit. Refer to https://docs.docker.com/go/buildkit/ to learn how to build images with BuildKit enabled" oh ffs. cannot generate the cpanfile snapshot - guess it might not actually be needed for this though? Or is it?
2024-05-06 12755, 2024
bitmap
you don’t need to regenerate the cpanfile snapshot
2024-05-06 12731, 2024
reosarevok
Still, good to know that it will be a mess eventually
2024-05-06 12733, 2024
bitmap
but you should install the BuildKit plugin anyway if you don’t have it
