The majority of
ARES is implemented. This is what remains to be done. Items are removed as they are finished, mostly from the top. Nothing on this list is set in stone or final. Names in square brackets are what system components are involved.
Input and Vox:
_input must fully implement mind restrictions
recvchat restrictions must be disentangled from vox-input pipe
Package Manager:
Split into two modules, pkg (package driver) and ax (server browser)
Nice display of package lists [ax]
Add tracking of which packages are installed [.pkg scripts]
Add full set of commands for install/remove/upgrade [pkg]
@beacon July 8 2023 (release Alpha 1 and CX/Supervisor controller)
db backup, db load support for character streams (web sources) [db]
forget deleted script [kernel]; daemon info [proc]
standard external menu HUD (AMenu)
replacement for remote console HUD (ARemote)
ARES-to-ARES menu access [variatype + menu]
policies pt 2: curfew [security]; apparel policy [security]; distress beacon [power], IM policies [security], owner radio policies and exceptions [security]
deal with impending tide of bug reports
start of Mainframe shopping event July 20, 2023
@beacon July 22, 2023 (release Alpha 1.1)
finish core personas
consent request bundling; updatable alerts [security, variatype]
animation hoverheight
defensive low-power-masking
prevent unsit while charging
lock & autolock [security + menu + baseband]
command for drainprotect [power]
Cleanup:
shakedown of interference and security rules
shakedown of documentation completeness
shakedown of guest access
shakedown of announcer rules; second set of announcers
@beacon August 5, 2023 (release Alpha 2)
finish nav; new nav server
RLV relay [restraint]
begin updating old devices for ARES compatibility
extra time for bug fixes, polish
sexuality (TESI for ARES); estimated 5 working days
@beacon August 19, 2023 (release Alpha 3 and sexuality (TESI for ARES))
Plans after the third ARES Alpha are less definite in terms of the amount of time required and the order of expected developments. Once ARES hits Beta, we will retire the Supervisor controller, and ARES will start to become available on standard hardware.
implement stream-oriented API, command-line pipes
Spring Utilities replacement with new rental, proximity, and cron facilities
database overlays [db]; Hierarchy/XNMS compatibility [domain, db]—no server code changes anticipated
ARES WARRIOR add-on with malfunctions (estimated 4 working days)
Beginning of converting Companion controllers to new ARES versions, deliver ARES to people who bought those systems; end of availability for exclusive ARES supporter controller
undefined amounts of time for copious bug fixes and polish; update remaining devices (those that previously depended upon the Companion "internal" message); update remaining controllers
dive (3 workdays)—ability to move units with direct key input with camera etc.
@beacon September 2, 2023 (release Beta 1 and WARRIOR)
undefined amounts of time for copious bug fixes and polish
HUDware (??? workdays)
new CSU system (??? workdays)—the CSU is a particularly design-intensive product that requires a complete overhaul as many of its settings are no longer meaningful; we would like to replace it with a "cyberware inventory" experience, where you must go to your local ripperdoc (Arachne X8) to change load-outs
@beacon September 16, 2023 (release Beta 2 and dive)
uplink (??? workdays)—ability to control units from web; will require new payments system and Patreon integration
@beacon September 30, 2023 (release Beta 3?, HUDware?, uplink? HCS?)
This is the page roadmap as it appeared at 2023-07-07 13:45:36.
You can view other old versions at the
history page.
Alternatively, you may want to settle for
the current version.