#metabrainz

Freso: you're welcome :)

[musicbrainz-server] y-van-z opened pull request #481: MBS-8748: Wrap medium name in release tracklist (master...mbs-8748-wrap-medium-header) https://git.io/vyG4D

Freso: thanks. Was nice. :-)

Surprised by my friend being on the same flight as I.

Freso: https://joeyh.name/blog/entry/removing_everythi...

Freso: https://news.ycombinator.com/item?id=13766933

Freso: my understanding is that both software freedom conservancy and the free software foundation are still talking to GitHub to get things fixed, but currently it's a bad situation.

(probably the analysis on mirbsd is slightly alarmist, and it isn't _that_ bad,... but it's still bad)

kuno: Reading now. Thanks for the heads up.

ruaok / Freso: do I even bother to answer the latest gsoc email at support, given they didn't bother to look it up themselves?

Be nice. Send them to the ideas page.

btw, just pinned https://twitter.com/MusicBrainz

ruaok: the LB one specifically? (since that's the most relevant one I guess)

That's part of the guide too, if they can't read that...

@ruaok

alastairp I'm interested in contributing to the Machine Learning Project, "New Machine Learning Infrastructure", I'd really appreciate it if you could tell me what are the skills I would require, and how I could start working on my GSoC 2017 proposal. Thanks in advance!

Forgive me for sending the same message twice.

grassknoted: do not send private messages to people in IRC

it has a habit of annoying them and they feel less inclined to helping you

Also, sending private messages show that you failed to read, or at least failed to comprehend, the "how to get started with GSoC" notes.

Freso : I apologise, it's not that I failed to comprehend the notes, it's actually my first time using freenode. I'm more comfortable with the slack or gitter clients. I'm sorry, I will not happen again.

grassknoted: Ah. You're right. Seems CallerNo6 removed the old heavily worded warnings against doing just that. Sorry about that. My bad. 🙏🏼 :)

zas np! I hope the places I picked were enjoyable for all! :)

Hm. Or maybe it was on another page that I'm mixing up now.

Freso: it's mentioned twice on https://wiki.musicbrainz.org/Development/Summer...

Quesito: The food was amazing!

alastairp: Ah. Right. :)

not on GettingStarted, though

Freso: glad you liked it!!!

Yeah. That was the one I was looking over. :)

alastairp: I'm extremely sorry, I didn't intend to private message you.

how do you mention someone in a jira comment?

alastairp: Something like [~JiraUsername] I think.

right

Hey! I'm new here, and I'm unable to sign up at: https://wiki.musicbrainz.org

The site prompts me for a Username and Password, even when I'm trying to sign up

try

NOTSPAM/NOTSPAM

Thank you so much! It worked! I think the Sign up process should be made a little easier, keeping a naive user in mind, maybe?

there used to have a popup but with Opera browser I don't see it

OTHER-286: Wiki anti-spam authentication broken in Chrome/Chromium

you can upvote the ticket ;)

akashn97: the problem is with Chrome, unfortunately

alastairp: I'm pretty good when it comes to front end webdev, can I try to solve the issue?

we should try and improve this somehow. Maybe on the signup/login screen?

it would involve editing our mediawiki source. Perhaps you could talk with legoktm, our wiki maintainer

Since the problem lies only with Chrome/Chromium browsers, I suggest we prompt the user to enter NOTSPAM/NOTSPAM

or make a comment on the ticket that Lotheric mentioned

a captcha should be implemented rather than a http auth popup

I just commented on it myself

right. We do in fact make a comment about this, but chrome has decided to not show it for security reasons

samj1912: does mediawiki have captcha built in?

that would be ideal

theres an extension https://www.mediawiki.org/wiki/Extension:Confir...

A simple recaptcha could be implemented. It could be done at the User data-entry page rather than a prompt.

I don't think that will be an issue.

That wouldn't take too long to get

Freso: what's our mid-term plan with google cookies?

and does recaptcha use any?

(I think we're also already using recaptcha for MB.org. And we actually do get a bunch of spammers signing up there. The wiki seems happily void of spammers though, so the HTTP Auth at least seems to be working. :/)

Is it alright if I assign myself to the bug, or do we adhere to a decorum here at MusicBrainz?

akashn97: WP:BB! :) (That is, go ahead and assign it if you're going to work on it. ;))

akashn97: you can take up any issue if its unassigned :)

alastairp: I don't think we've gotten any further in that discussion.

akashn97: I recommend that you start a discussion on the ticket as well

Freso: right. and since we already have recaptcha, not much of an issue for now

We were going to look into it because the EU cookie law...

But that cookie law might be going away soon.

(Finally!)

Well, "soon".

akashn97: it's good to take the initiative, however most of the implementation of this task will have to be done by metabrainz employees, because it involves configuration, not coding

however, if you can provide a push to make someone enable this plugin, then that's great too!

Alright, I'm sorry I got a little carried away, my main intention here was to just introduce myself. I heard about MetaBrainz because of GSoC, and I'm really fascinated by it now that's I've started reading about it and getting to know it better.

Hope to work with you all this summer! :D

akashn97: Getting carried away is a good indicator for a prospective student. :)

samj1912 tends to get a bit carried away! :D ❤️

akashn97: amazing introduction! :)

I'm sorry if this is a bad question, but does MetaBrainz use Git?

akashn97: Heavily :)

did you read https://wiki.musicbrainz.org/Development/Summer... ?

Freso: :P

I didn't mean to manage the code, I'm sorry I should have been more specific.

akashn97: you should pick a project from https://wiki.musicbrainz.org/Development/Summer...

What I meant was, why doesn't MetaBrainz just rely on the Issue Tracker Git provides?

ah, we use Jira for changelogs and other things :)

its more flexible and a dedicated issue tracker rather than the one github provides

and theres a difference between git and github :P

I really appreciate all the help and everything. Thanks for getting me started guys :D I'll give it my best!

akashn97: we have used jira for longer than github has existed

so there is a lot of historical reasons for staying with jira

(perhaps that's a small lie, we've definitely been using jira since before the gh issue tracker got good)

When did we start using git?

true, we also used subversion and bitbucket before github

(I'm genuinely curious.)

look at git log for the first git-svn tag?

oli mentioned git-svn in d8758a1281abc6173ac5cbaaf21acd80ce4254ab in November 2008

Haha. That was the commit I just found too. :)

samj1912: me too! :)

iliekcomputers: in an IIT?

ocharles made a Git mirror in 2008: http://musicbrainz.1054305.n4.nabble.com/Git-mi...

nah, an NIT

ah :)

And 2010 seems to be when the official move actually happened: http://musicbrainz.1054305.n4.nabble.com/mb-ser...

Ha ha, I love the community already! Everyone is so friendly and interactive! :D

akashn97: wait for the first code review ;)

So GCI '15 winners and GCI '16 winners made a mega group chat and..ohmy..

iliekcomputers: never take code reviews personally

And 2012 is when GitHub became the official git repository for mb_server: http://musicbrainz.1054305.n4.nabble.com/Making... (though code reviews still happened off-GitHub for a while)

[musicbrainz-server] y-van-z opened pull request #482: MBS-9266: Fix subheader of area pages (master...mbs-9266-area-subheader) https://git.io/vyGbb

Gentlecat: haha, I know, I was just making a joke :)

I actually like code reviews :P, my coding has improved tons in quality since I first started in december

akashn97: from our side it's nice that you came in with a problem, discussion, and willingness to work with us, instead of asking us to tell you how to start contributing :)

^

samj1912: Well, that's the hope. It'd be tedious having to tell someone the same thing over and over again. :)

samj1912: 🙌

wow. so many people working on AB tickets. this is great