Hi pbryan, not at the moment, but that will happen this quarter
2023-02-03 03459, 2023
monkey
About the style repo, definitely a good idea to have it deployed for review!
2023-02-03 03432, 2023
monkey
If you're comfortable with all this you can clone the repo and use readthedocs to deploy you cloned copy
2023-02-03 03457, 2023
monkey
Happy to help with the process nex5
2023-02-03 03404, 2023
monkey
Next week
2023-02-03 03428, 2023
Shelly joined the channel
2023-02-03 03455, 2023
Shelly
I think this issue https://tickets.metabrainz.org/browse/BB-530 could be a beginner project since the implementation require knowledge wikimedia API and various other language handler functions.
2023-02-03 03456, 2023
BrainzBot
BB-530: Wikidata Blurbs
2023-02-03 03422, 2023
Shelly has quit
2023-02-03 03425, 2023
pbryan
OK, thanks monkey.
2023-02-03 03453, 2023
ArjunM joined the channel
2023-02-03 03410, 2023
ArjunM
hi, i was trying to setup the dev environment for bookbrainz and this issue propped up. it says there's a syntax error in json file. https://pastebin.com/zrWW03T7. The clientID is my musicbrainz id and i've set it to NULL in the original config/config.json file and rerun, the issue still persists. redis, elastic search and node are installed
2023-02-03 03411, 2023
ArjunM
successfully.
2023-02-03 03406, 2023
ArjunM
when rerun with default values it says Error setting up OAuth strategy MusicBrainzOAuth2Strategy requires a clientID option. You will not be able to log in.
2023-02-03 03421, 2023
pbryan
@ArjunM: A JSON string value must be contained in quotation marks. So, "clientid": "value" not "clientid": value.
2023-02-03 03445, 2023
ArjunM
thanks a lot @pbryan. made the change and executed it. the issue is resolved now.
2023-02-03 03422, 2023
Aqib joined the channel
2023-02-03 03443, 2023
ArjunM
Oops, I forgot to introduce myself here. Hi team. I'm Arjun, a CS undergrad with some experience in Java, CPP and SQL. I'm new to this community and I look forward to contribute to this project as part of GSoC'23 and otherwise.
That issue is labeled “Decision Required”. It would probably be best to discuss what the proposed solution should look like and get consensus on that beforehand.
2023-02-03 03403, 2023
pinkman7009
Ah sure. I understand
2023-02-03 03432, 2023
pinkman7009
Whom should I discuss the solution with?
2023-02-03 03401, 2023
pbryan
I would just start writing comments in the issue about how it would work.
2023-02-03 03419, 2023
pinkman7009
Sure. Thanks!
2023-02-03 03422, 2023
pbryan
CatQuest points out that annotations are doing this right now.
2023-02-03 03458, 2023
pbryan
So, I think the question will be whether having a separate field will prove useful enough.
2023-02-03 03417, 2023
pbryan
And, if we do add the field, what the guidelines will be around its use.
2023-02-03 03447, 2023
pinkman7009
From what I understand, aren't annotations supposed to be certain specific comments about the work? Maybe a description is a more descriptive input, explaining more details about the work.
2023-02-03 03401, 2023
pinkman7009
And kind of like a generalized summary sort of
2023-02-03 03427, 2023
pinkman7009
Also can you explain to me what exactly you mean by guidelines around its use?
2023-02-03 03432, 2023
pbryan
If we add a field, we should document what it should contain, and how it should be used.
2023-02-03 03447, 2023
pinkman7009
Oh, yeah I get it
2023-02-03 03404, 2023
pbryan
So, for example, the guideline would likely suggest it be written in English, have a certain length, contain or not contain certain information.
2023-02-03 03416, 2023
pinkman7009
Yes
2023-02-03 03421, 2023
pbryan
Annotations are pretty much free-form, without any guidelines.
2023-02-03 03425, 2023
pinkman7009
Okay
2023-02-03 03426, 2023
pbryan
So, description would be better because its semantics would be more defined.
