2010 Q1 Dev Meeting: Difference between revisions

From Armagetron Advanced
Luke-Jr (talk | contribs)
too much detail :P
Epsy (talk | contribs)
→Agenda: Added a bunch of stuff
Line 41: Line 41:
**Python scripting fork (removes Ruby "support")
**Python scripting fork (removes Ruby "support")
*Feature requests via bug tracker?
*Feature requests via bug tracker?
*CMake and other stagnant branches
=== User Experience ===
*Menus
**Item Reorganisation
***Implementation Details, better kept for future dev-only discussion
****Use hooks to generate menus on the fly
*****eEvent branch uses boost::signals, finalise and use that?
****Add menu entries statically, but better
**Better Look
***Use cockpit code?

Revision as of 18:32, 8 January 2010

http://forums3.armagetronad.net/viewtopic.php?f=4&t=19861

Date and Time

On Sunday 10th, January 2010, a bit before the ladle, around 18 GMT

Where

IRC Channel #armagetron on irc.freenode.net

http://webchat.freenode.net/?channels=#Armagetron

Agenda

Edit as desired...

Community

  • Forum moderation

Resource Repository

  • Splintered community repositories popping up
  • Restoring the central community repository
    • Hosting
      • Is Dreamhost usable?
    • Accounts
      • Username or global-ID?
    • Management
      • Non-developers?
      • Third party dtd's?

Merging Sty/CT

  • If the 0.2.8 branches are wanted, maybe they should be merged and become 0.2.9?
  • Merging trunk development
    • Per-feature branch theory
  • Trigger protocol
    • Need a way to let servers define new controls

Future Direction

  • Console/phone platform support
    • OpenGL ES
    • GPL exceptions?
  • Scripting
    • Python scripting fork (removes Ruby "support")
  • Feature requests via bug tracker?
  • CMake and other stagnant branches

User Experience

  • Menus
    • Item Reorganisation
      • Implementation Details, better kept for future dev-only discussion
        • Use hooks to generate menus on the fly
          • eEvent branch uses boost::signals, finalise and use that?
        • Add menu entries statically, but better
    • Better Look
      • Use cockpit code?