Confirmed users
1,209
edits
User:Wenzel/Bouncer:MirrorBrain: Difference between revisions
Jump to navigation
Jump to search
→MB's Alignment with Bouncer Goals
(initial observations) |
|||
| Line 21: | Line 21: | ||
Note: This list is by all means not complete. I gathered a number of requirements from the [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bouncer&resolution=--- current Bouncer bug list], and determined if MB claims to handle that problem or not. | Note: This list is by all means not complete. I gathered a number of requirements from the [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bouncer&resolution=--- current Bouncer bug list], and determined if MB claims to handle that problem or not. | ||
* ... | === Present in MB === | ||
* GeoIP / peer network ({{bug|353237}}) handling: MB claims sophisticated mirror selections based on both of these criteria -- and more. | |||
* Automated mirror monitoring, and spot-checking file integrity (Bouncer's Sentry functionality): MB supports this, along with real-time server health checking. | |||
=== Not handled yet === | |||
* MB does not have a Web Frontend yet, though it is [http://mirrorbrain.org/development-status planned]. | |||
=== Unsure === | |||
* Due to the lack of a web frontend, it's unsure if administrative data can be saved and easily be retrieved (mirror contact data, for example: {{bug|408677}}) | |||
* The command-line interface will likely make Build happy, if it supports adding releases on the fly ({{bug|408674}}) | |||