I wonder if we should have a smaller group takes this on and come up with some candiates.
_lucifer
yeah sure ruaok
Freso
xBrainz is generally the "source" projects, and BrainzX is derivatives (e.g., BrainzBot)
ruaok
doing this in a large group is likely going to take foreever and yield poor results.
_lucifer
we can dsicuss it outside the meeting
Freso nods
yvanzo
FWIW, there was a discussion about it a few weeks/months ago with candidates.
shivam-kapila likes BrainzDroid
ruaok
_lucifer: pick 3-5 people as a team and then start there.
_lucifer
đź‘Ť
we can this for the meeting, Freso
*end
Freso
Alright.
Thank you all for your time! Stay safe out there!
</BANG>
rdswift likes BrainzDroid Music (to help future-proof)
Mr_Monkey
Thanks !
Mr_Monkey likes BrainzDroid too
_lucifer
I suggest we come with a list and put it on community forums for voting and finalize it by next week
Mr_Monkey: can you come with an icon ? it need not be immediate whenever you ahve the time
jmp_music
take care everybody!
jmp_music has quit
shivam-kapila
I would like if forums have a poll feature
Mr_Monkey
Perhaps after we have a name chosen might be better
shivam-kapila
Lol I have an idea just now
For brainzdroid
_lucifer
Yeah, sure only makes sense after that :)
rdswift
So is BrainzDroid Books in the plans eventually? ;-)
_lucifer
rdswift: once BrainzDroid Music is stable and has a sufficient feature set, I'd say why not?
rdswift
đź‘Ť
SomalRudra
_lucifer: agreed ! apart from a name to the app, the webservices in the app are not android device portable. The websites open in the browser in a desktop view
few changes in the meta tags,if can be done would be really supportive to the current responsive design
_lucifer
yeah sure. we can work on that.
CatQuest
you know my vote is for "Data" something becasue it's android
_lucifer
CritiqueBrainz integration in the app shall also arrive but I don not have a timeline on that
I see in the previous discussion as well BrainzDroid was proposed :)
reosarevok
bitmap, yvanzo, CatQuest: for Add Instrument edits, should we use l_instrument_descriptions (so, should the description be shown translated if we have a translation), or for edit display is it better to show the English original instead even if using an MB translation?
(was going to change it to use the translated version, but then wondered since it might be weird for ones that, for example, got changed since and are no longer translated in that original version)
CatQuest
uh I'd say use the translation if there is one?
yvanzo
reosarevok: why would you not localize it? How would you know it was not translated at the time of the edit?
reosarevok
yvanzo: because this is Add Instrument, so the description didn't exist when the edit gets entered
CatQuest
oh
that's adifferent indeed
reosarevok
So there's no translation at first for sure
CatQuest
I'd say don't mess with "add instrument"
reosarevok
Everywhere else I'd show translations (and we already do), but not sure about edit history since it kinda makes it look like the instrument edit added it in French or whatever
CatQuest
infact it shoudl show the description that was given it (in english) always for those (I sometimes even look at these to compare with what I wrote later)
reosarevok
(would be weird to get a note like "this is wrong in French")
CatQuest
yea
bitmap
reosarevok: I'd show it as entered by the edit in english
reosarevok
Ok
CatQuest
for add and edit instrument there shoudl not be the tranlsated descriptions i'd say
Sorry, I missed the meeting. Nothing much to report, usual sysadmin stuff (trying to prevent kids to put the house on fire mainly), plus working on Picard next release (another beta soon), plus summer.