[mb-devel] Dev chat reminder, issue 8d9fe689-b6ab-4483-8987-8d1bc0e238cf

[Statler & Waldorf]

We've got our weekly dev chat on 2015-05-04 on IRC in #musicbrainz-devel on irc.freenode.net. We're going to meet at Regular Meeting Time [1] (19:00 UTC) [2].

If there is any topic you would like to discuss during the meeting, please add it to the agenda in the channel topic.

[1] http://musicbrainz.org/doc/Development_Chat
[2] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150504T19

[Shadab Zafar]

Hello everyone,

The work that I'd decided for the community bonding period was
understanding of python-musicbrainzngs so that I can add Events later on.

My plan was to wrap up this PR [1] but I haven't been able to do anything
yet due to my ongoing end-semester examinations.

I have 3 (or 4) exams every week, so things are pretty tight.

I'll be free by 21st May from all my college related stuff and will then
begin working full-time on the project.

Regards,

Shadab

[1] : https://github.com/alastair/python-musicbrainzngs/pull/123

Post by Statler & Waldorf
We've got our weekly dev chat on 2015-05-04 on IRC in #musicbrainz-devel
on irc.freenode.net. We're going to meet at Regular Meeting Time [1]
(19:00 UTC) [2].
If there is any topic you would like to discuss during the meeting, please
add it to the agenda in the channel topic.
[1] http://musicbrainz.org/doc/Development_Chat
[2] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150504T19
--
This message brought to you by https://github.com/mayhem/statler-waldorf
Don't even think of responding to this email. We won't answer!
http://goo.gl/FSZdF
_______________________________________________
MusicBrainz-devel mailing list
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel

[Alastair Porter]

Maybe a better place to start with pymb would be adding some new features
in the existing framework - e.g.
https://github.com/alastair/python-musicbrainzngs/issues/142 or
https://github.com/alastair/python-musicbrainzngs/issues/154 (we're quite
behind on schema changes....)
I think that these would be immediately more useful to more people and will
give you an overview of the code, rather than the requests patch, which is
likely to cause lots of back-and-forth for a long time before it is
resolved, and includes a /lot/ of changes.
Feel free to ask any questions in IRC or on github about the tasks, we'd
love to have someone else working on development.

Alastair

Post by Shadab Zafar
Hello everyone,
The work that I'd decided for the community bonding period was
understanding of python-musicbrainzngs so that I can add Events later on.
My plan was to wrap up this PR [1] but I haven't been able to do anything
yet due to my ongoing end-semester examinations.
I have 3 (or 4) exams every week, so things are pretty tight.
I'll be free by 21st May from all my college related stuff and will then
begin working full-time on the project.
Regards,
Shadab
[1] : https://github.com/alastair/python-musicbrainzngs/pull/123

Post by Statler & Waldorf
We've got our weekly dev chat on 2015-05-04 on IRC in #musicbrainz-devel
on irc.freenode.net. We're going to meet at Regular Meeting Time [1]
(19:00 UTC) [2].
If there is any topic you would like to discuss during the meeting,
please add it to the agenda in the channel topic.
[1] http://musicbrainz.org/doc/Development_Chat
[2] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150504T19
--
This message brought to you by https://github.com/mayhem/statler-waldorf
Don't even think of responding to this email. We won't answer! http://goo.gl/FSZdF
_______________________________________________
MusicBrainz-devel mailing list
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel

_______________________________________________
MusicBrainz-devel mailing list
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel