[Broken Ohloh code location]

https://www.openhub.net/p/TrinityCore/enlistments

 

Ohloh is still pointing to master branch, please correct it to point to 6.x. Current status is "Analyzed 4 months ago based on code collected 4 months ago." , after 4 months it's about time to fix it

[Dbc, Maps, mmaps, Vmaps problems]

Does the 3.3.5 branch now need the version 5 mmaps generator?

 

https://github.com/TrinityCore/TrinityCore/commit/f7bc86a17cc0dd1c59c338539c1a7f1d7d6e5f64#diff-0ce9ee26a4f08071044530f2558b2f97R39 since 21 Feb 2014

[Open Source related videos and articles]

http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/

 

"14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star"

 

for all the community members who are not top skilled developers and still want to help the project but don't know where to start

[Bountysource - get paid for fixes]

2 weeks later BountySource emailed me a congratulations letter and a nice sticker

[Open Source related videos and articles]

http://blog.codinghorror.com/what-if-we-could-weaponize-empathy/

 

Another interesting article on the topic of online communities

[Bountysource - get paid for fixes]

Sharing my personal experience fixing https://www.bountysource.com/issues/1412712-chat-channel-messages-lost-while-loading

 

I noticed there was a bounty an a quite interesting issue "Chat Channel messages lost while loading"

 

I started working on it, adding my findings to the github issue and pushed to my fork the initial work

 

To notify the backers I went to bountysource and clicked on "Get started" in the developers tab

 

Once I finished my fix I was able to push the fix directly and close the issue, otherwise contributors should open a PR and wait for it to be merged

 

Once the issue gets closed on github, you can claim the bounty on bountysource

 

The bounty will be paid if all backers accept or if they don't reject it between 2 weeks

 

While writing this post the backer accepted the fix as valid and bountysource awarded the bounty

 

Now all I have to do is find an issue I want to get fixed and put the money I earnt on it

[Bountysource - get paid for fixes]

well it's up to you to see the glass half full/half empty.

 

You could ask those questions to Bountysource directly and post their reply here

[Bountysource - get paid for fixes]

Some questions are related to how Bountysource works, you can check https://www.bountysource.com/faq for answers. GitHub integration is supported but currently not working due to Bountysource issues.

 

Blizzard reaction has nothing to do with how much money TC contributors make but how much money Blizzard loses monthly due to people playing their game without paying them. Adding Bountysource doesn't affect Blizzard's income/losses.

[Bountysource - get paid for fixes]

Fixing and reclaiming the bounty is not restricted to TC's official developers: anyone can propose a fix (usually by doing a pull request) and, if it is accepted, get the money reward.

 

I'd like to stress out the fact that anyone can get the money reward, from the guy who just joined 5 minutes before to long-standing developers. What's more in the Open Source spirit than this ?

[Open Source related videos and articles]

Very interesting video I've been looking at for the last 10 minutes, still a lot more to watch. Thx dfighter for sharing it

 

"How to Protect Your Open Source Project From Poisonous People"