Difference between revisions of "Planned Features"

From Mumble Wiki
Jump to: navigation, search
Line 3: Line 3:
 
If you want to help out with any of the below, '''great!''' Be aware that during the alpha/beta stage the code will change quite a lot, and public CVS lags quite a few hours behind developer CVS, so you might want to drop us a line first to let us know you're working on something. That way we can leave those files alone while you work.  
 
If you want to help out with any of the below, '''great!''' Be aware that during the alpha/beta stage the code will change quite a lot, and public CVS lags quite a few hours behind developer CVS, so you might want to drop us a line first to let us know you're working on something. That way we can leave those files alone while you work.  
  
== Channel linking ==
+
== Release 1.0 ==
  
Multiple channels should be linkable, to allow hierarchic talk structures. The difficulty is finding a way to do this so that it feels natural for all users, and you have no cases where player A and B cause problems for player C because they are both talking to player C but can't hear each other.
+
We need some more field testing, but we are really feature-complete for what should be in the 1.0 release. So the "To-Do" is actually just to be sufficiently sure 0.9.2 (current CVS) is stable enough, release it and if no bugs are reported make that the 1.0 version.
 
 
== Ban and banlists ==
 
 
 
There should be a variable-width ban of IP ranges. Question is; who should be allowed to add a ban? .. and who should be able to see the IP?
 
 
 
I'm somewhat inclined to let anyone with move/kick privileges in the root channel also be allowed to ban a user without showing the IP, and let people with write privileges in the root channel see the IP of all users as well as see/ban IP ranges.
 

Revision as of 04:56, 13 December 2005

These are things that are planned added 'some time in the future'. Please try Mumble out before you comment on any of the ideas below.

If you want to help out with any of the below, great! Be aware that during the alpha/beta stage the code will change quite a lot, and public CVS lags quite a few hours behind developer CVS, so you might want to drop us a line first to let us know you're working on something. That way we can leave those files alone while you work.

Release 1.0

We need some more field testing, but we are really feature-complete for what should be in the 1.0 release. So the "To-Do" is actually just to be sufficiently sure 0.9.2 (current CVS) is stable enough, release it and if no bugs are reported make that the 1.0 version.