The using the money for this stuff like that is the part I understand. I guess the only part I dont understand is how "This $100 is not real money."
Have you played the board game Monopoly before? You are given fake money to play with. You use that money to buy fake properties to place on the board. The other players must pay you (again with fake money) if they land on your property after rolling the dice.
That's what I'm talking about. It wouldn't be real money. We'd have 100 units of voting power per month to put toward whatever enhancements are on the list of requested enhancements. For instance, let's say we have 10 enhancements on the list:
A, B, C, D, E, F, G, H, I, J
Now I have 100 units of voting power in March. I decide to put 90 votes towards D and 5 votes towards H. I was stupid and let March go by without using my final 5 votes. If 2 other people voted the same way as I did and nobody else voted, then we would have the following prioritization at the end of March (assuming we started this whole idea at the beginning of March and there was no voting in February):
D = 270
H = 15
A = 0
B = 0
C = 0
E = 0
F = 0
G = 0
I = 0
J = 0
Now, the developers would have a pretty good idea that the most important piece to work on is D, because it got the most votes. After that, comes H. After that, it is a toss up, because nobody voted for the other items. I'm sure in reality, there would be some votes cast for nearly all options, since everyone has their own likes/dislikes about the site.
Now, I'm not suggesting that the developers should *only* be allowed to work on those items at the top of the list. I'm just saying it gives them an idea of what most peope want to see implemented. D may be extremely hard to implement and a given developer may not feel they are qualified. But maybe G is right up their alley, so they would work on that instead and leave D to some other developer.
The other thing that needs to be worked out is how to keep more than one developer from working on the same item. In some cases, the item may be big enough that it can be split out, but I'm speaking of two people not knowing the other person is working on it and each person spends the time to fix the same issue. That's inefficient. On the other hand, we don't want a developer to take an item off the list to work on and then not work on it for months either. There may need to be a time limit for one person to work on something before turning it over to someone else, hopefully giving the second person all the work that has been done by the first person, if they have managed to put in some time toward it.
I'm unclear about the "disabled" comment. Does that mean someone is thinking of shutting off private message functionality on the boards?
I guess I didnt word that right. What I meant is, "Its a very important tool, and I hate to think it may continue to be hard to use for people with large amounts of incoming pm's."
Ah, yes. I agree. It doesn't have nearly the feature set as most email programs do. I wonder what the benefits are of using it vs a real email system? I mean we can all create gmail accounts and use those instead. Of course, then it isn't integrated in with the system (like being able to click on a person's name and send them a message).
One option would be an enhancement for adding an email "gateway" to the boards. What I mean by this is that a user could pick whether they want to use the IPB email or they want to use their own email account on another system (gmail, hotmail, etc.). Let's say I decide to use my gmail account. I would enter that email address into the system and enable the gateway option for my account. Now, when another user sends me a private message on here, the system would send the message to my gmail account. It would come from a system generated email account on our system (we'd have to work this out with our hosting company). When I reply to the message, it would be sent to that system generated email account and then the board would read the message and put it into their private messages as coming from my board ID.
There are some downsides to this approach (no standard mechanism for quoting...you'd have to manually put the quote tags in the gmail message, etc.). SPAM is another consideration, but there are ways around that (the system can use throwaway email accounts for the system generated ones and periodically change them). We'd want the user ID to be part of the email address though, so you would know who the email is from. Of course, it would be up to the person whether they like that option vs the regular option. They could stick with the current PM functionality if that is better for them.
Another option is to plug in a completely different messaging product with more robust functionality and allow that option for online (non-email) messaging.
David