-
Notifications
You must be signed in to change notification settings - Fork 5
Bounty currency symbol? #67
Comments
I like this! |
However, isn't that symbol often (erroneously) used to represent BitCoin? In that case, we could consider using another one to not cause any confusion. |
Yeah, it happens. I think the confusion will quickly subside once they want to know more about what those message on Slack mean. I just discussed this with Myrjam and she raises the relevant question whether newbies will actually click on these mentions or just ignore them. The reason for ignoring might be that they don't know what bounties are (at least nog in this context), what GitHub is, what GitHub issues are and what gamification in general does (at least nog from that sole message on Slack). Posting "฿50" instead of "bounty points" makes it perhaps even more obscure. |
When you'd be willing to work on Zeus projects, I guess you will easily find out. This would be an issue when our users existed in a vacuum, but fortunately we see them every few days, and even engage in conversation with them. |
We're at the point of trying to encourage them of doing so. |
@Procrat but bounty points are only shown in the #zeus-dev channel, so these notifications would only be for people who already joined the #zeus-dev channel. And these people would have already some experience with Zeus projects. |
@Procrat I doubt anyone would start contributing because of gamification. I expect it to encourage more contributions, but there has to be some engagement to start with. |
I guess you're right. It somehow feels a bit like a failure though. |
That is, some engagement with Zeus, not neccisarily with our projects. In that case, you'd still know what Gamification is. |
Bumping this in relation to #87. |
How about:
|
Or a combination? ฿₱ for ฿ounty₱oints? |
We could use the Thai Baht symbol instead of "bounty points", for both brevity and elimination of any confusion with bounty score.
Example usage:
Any thoughts?
The text was updated successfully, but these errors were encountered: