2) Was always on my radar. Try to make it a little easier on Mark when he does stats from the tracker post release (number of items tested, who tested, etc.). Was more focused on com_tracker and getting that finished before starting a com_reports.

1) Could easily be built on top of that reporting data. Just a matter of doing it in all honesty.

I'd like to at least have badges for various leadership roles, i.e. Mark as the JBS Coordinator, JM as Language Coordinator, etc. to kind of distinguish those folks from other users (not saying everyone isn't important, but to the untrained person, they might mistake something as sounding official from someone who isn't in a spot to make such a statement, for example). I think this is something we could manage in com_users by building a user plugin.

The point system, we might need to bug the (rest of the) PLT and other teams about to see if this is something the project as a whole would like to support. I do think it'd be pretty cool though. Maybe I could finally afford my Joomla PLT polo shirt

There's a PLT polo shirt? :D

2) Nice! Yeah, this stuff is just icing on the cake.

1) Cool

3) That's a good idea about the badges. I was thinking in the sense that a person might get a badge when they 100 contributions, for example. There could be different earned for different completed tasks, e.g. at http://www.codecademy.com/ you can earn badges for completing classes. Sounds kind of kid-ish, but if we do it in a professional way, people can use it as an accomplishment board within their profile area and can use that on job résumés or simply to show off, lol.

4) Agreed. I just wanted to put the idea out there so that we can start thinking about how to engage people via gamification and social coding once all the basic requirements of the project are completed.

Cool ideas.

1) and 2) shoudn't be too hard - I love stats. Let's pick a nice graph thingy (maybe Raphaël)

3) Yes badges are cool, maybe based on the user group ? I hope they don't get too fancy.. maybe we can just use the bootstrap labels and badges ?

4) That sounds like real Fun :) I remember someone in the JBS chat brought up the idea to "gamify" the PBF events.

Are there JBS coffee cups ? I would like one of those :D

I'll make you a deal. If you code gamification / social coding aspects into the tracker, I'll get you a JBS coffee cup :D

I talked about this with Javier Gómez three weeks ago as a funny way to increase the number of contributors.

My idea was creating squads/teams and change our working git workflow to a lieutnant based:

http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows

Each team has a leader/lieutnant that filters team contributions and finally decides what is ok to get into the core.

We can have teams by countries. This will increase non-english speaking contributors. Teams decide their country and there is also a mixed type for teams whose members are from various countries.

This way at the end of the year we can award:

• Best country team
• Best continent team
• Best world team
• Promote team members to new lieutnants/recruiters/formers
• Promote lieutnants to ....

Awards would be JAB / JWC free travel for the team to share their experience/thougts. Strong country communities can award his best team of the year.

I'm sure that all this ideas will increase the number of countributors but before all of this we have to follow our roadmap: First make a working tracker. Later improve it with new features.

That does indeed sound like a fun way to do it :)

Any good examples of leader boards or stats pages to look at as examples?

Free Gamification Module:
http://itprism.com/free-joomla-extensions/ecommerce-gamification/game-mechanics-platform

Digging up old history (and needed an issue as a test dummy for my last commit)

Since this was opened up, we added the charts to the developer site. Should those stay there when we migrate over to this app or do we want to integrate those into the app natively? Also, does that change any ideas with what types of features we add with this?

I think this should be changed. I would like to see better integration with actual github issues and comments etc… The current system does not appropriately reflect all aspects of issue maintenance. 

Additionally, I'd like to see it integrated with the new tracker :) I've got several report ideas - so I'll write them up and see what everyone else thinks.

Thanks,
David Hurley
webspark

david@websparkinc.com
336.525.9282 (mobile)
336.525.6131 (office)

On August 21, 2013 at 10:56:49 AM, Michael Babker (notifications@github.com) wrote:

Digging up old history (and needed an issue as a test dummy for my last commit)

Since this was opened up, we added the charts to the developer site. Should those stay there when we migrate over to this app or do we want to integrate those into the app natively? Also, does that change any ideas with what types of features we add with this?

—
Reply to this email directly or view it on GitHub.