Difference between revisions of "Open Source Task List"
(Actualize.)
Line 1: Line 1:
−
=Software=
+
This is a general task list for the various open-source projects currently underway at the GoW.
−
==Client==
+
−
* Branan's PlasmaClient is very WIP.
+
−
** Currently supports linking though StartUp to Relto.
+
−
** Has basic rendering and physics interactions.
+
−
==Server==
+
−
* Zrax has DirtSand, which is functioning at a basic (but very impressive) level at this point.
+
−
* Dustin has one, which I haven't tested and can't comment on yet.
+
  
−
==PyPRP2==
+
== Software ==
−
* Theoretically supports MOUL format. Should be verified and expanded on.
+
These are the plans for the various software aspects of Uru (client, server, etc.).
−
** What about the PhysX binary blob? Ignore because Branan's client won't read it anyway?
+
−
*** That depends entirely on whether supporting Cyan's MOUL client is a design goal... which will probably depend on how communicative cyan becomes in the future.
+
−
* What else does this need on top of current PyPRP to be a solid tool?
+
−
** GUI access to all, or at last the most often used, features? Seems to be the PyPRP2 path anyway
+
  
−
==File Server==
+
=== Client ===
−
* Where will we store age files? How will the server distribute them?
+
* The [[Development:CyanWorlds.com Engine|H'uru fork]] of the [[CyanWorlds.com Engine]] is currently undergoing major development. Big projects include:
−
=Assets=
+
** Enabling cross-platform compatibility. This entails, among other things:
−
It should be possible to create enough fan content to not have to include many Cyan assets. The big issue will be the global data. See below.
+
*** Replacing DirectX with OpenGL support,
 +
*** Replacing PhysX with Bullet physics,
 +
*** And rewriting great parts of the networking code.
 +
** Replacing the Game Manager.
 +
** Implementing new features (such as KI copy-pasting).
  
−
* The KI is special. It's deeply integrated into the game, so we have to do *something* with it. Re-implementing the old Choru ki has been floated.
+
=== Server ===
−
==Global Data==
+
* [[DIRTSAND]] is the server currently used by the GoW for deploying open-source Shards by the GoW (an alternative is MOSS by OpenUru).
−
* CustomAvatars wouldn't be necessary on an all-fan-asset shard (except for any of our own, of course)
+
* [[Wondruss]] is a work-in-progress server with additional functionality, set to replace DIRTSAND at some point.
−
* GlobalAnimations has some things referenced in source code, much of it is only in assets (but those anims are useful for common things)
+
 
−
* GlobalAvatars we're probably stuck with, unless we want to re-do all the necessary global anims in addition to creating new avatars
+
=== PyPRP2 ===
 +
* Basic geometry available.
 +
* Support for MO:UL format.
 +
* Very incomplete compared to PyPRP1.
 +
** Help wanted!
 +
 
 +
== Assets ==
 +
* It should be possible to create enough fan content to not have to include many Cyan assets. The big issue will be the global data. See below.
 +
* A letter has been sent to Cyan requesting a more permissive license for Cyan content. See the [http://forums.openuru.org/viewtopic.php?f=91&t=635 associated thread] on OpenUru.
 +
* A new concept for the GUI of the Nexus interface has been [http://www.guildofwriters.org/tweek/uru-concepts-nexus-gui/ proposed by Tweek].
 +
 
 +
=== Global Data ===
 +
* CustomAvatars wouldn't be necessary on an all-fan-asset shard (except for any of our own, of course).
 +
* GlobalAnimations has some things referenced in source code, much of it is only in assets (but those anims are useful for common things).
 +
* GlobalAvatars we're probably stuck with, unless we want to re-do all the necessary global anims in addition to creating new avatars.
 
* GlobalClothing the only thing that should be required here is the default items. Everything else could likely be replaced.
 
* GlobalClothing the only thing that should be required here is the default items. Everything else could likely be replaced.
 
* GlobalMarkers is used for marker hunts. We could change the sounds and pictures stored here to customize markers. It's a small thing, though.
 
* GlobalMarkers is used for marker hunts. We could change the sounds and pictures stored here to customize markers. It's a small thing, though.
−
==Special Ages==
 
−
===Startup===
 
−
Tweek once designed a new Startup GUI. Perhaps it should be implemented for this?
 
−
===AvatarCustomization===
 
−
This is absolutely necessary, but I'm not sure whether we should just use Cyan's or write a new one
 
−
===Personal===
 
−
there are references in the actual code to 'Personal', so we have to have *something*. Whether its Relto or a fan creation? who knows.
 
  
−
=Documentation=
+
=== Special Ages ===
−
==Python Files==
+
'''<code>Startup</code>''': Tweek once designed a [http://www.guildofwriters.org/tweek/uru-concepts-login-gui/ new Startup GUI]. Perhaps it should be implemented for this?
 +
 
 +
'''<code>AvatarCustomization</code>''': This is absolutely necessary, but I'm not sure whether we should just use Cyan's or write a new one.
 +
 
 +
== Documentation ==
 +
This is the work that needs to be done on the documentation of software features.
 +
 
 +
=== Python Files ===
 
* There are lots of x*.py files to implement common features. They should be doc'd with the correct parameters in a way artists can easily understand.
 
* There are lots of x*.py files to implement common features. They should be doc'd with the correct parameters in a way artists can easily understand.
−
* On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver)
+
* On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver).
−
==PyPRP2==
+
 
−
=Community and Sustainability=
+
=== Wiki ===
−
==Donations==
+
* All the tools need to be documented as new features are introduced. Work is currently underway to actualize the wiki.
−
* Might be warranted/needed at some point
+
 
−
==Information Sharing==
+
== Community and Sustainability ==
−
* Should be much more open than Cyan. This seems to be our general nature anyway, so shouldn't be hard ;)
+
This is what needs to be done for the community and for the Guild.
 +
 
 +
=== Donations ===
 +
* Might be warranted/needed at some point.
 +
 
 +
=== Information Sharing ===
 +
* Should be much more open than Cyan. This seems to be our general nature anyway, so shouldn't be hard.
 +
 
 +
[[Category:Development]]

Revision as of 21:18, 15 May 2012

This is a general task list for the various open-source projects currently underway at the GoW.

Software

These are the plans for the various software aspects of Uru (client, server, etc.).

Client

  • The H'uru fork of the CyanWorlds.com Engine is currently undergoing major development. Big projects include:
    • Enabling cross-platform compatibility. This entails, among other things:
      • Replacing DirectX with OpenGL support,
      • Replacing PhysX with Bullet physics,
      • And rewriting great parts of the networking code.
    • Replacing the Game Manager.
    • Implementing new features (such as KI copy-pasting).

Server

  • DIRTSAND is the server currently used by the GoW for deploying open-source Shards by the GoW (an alternative is MOSS by OpenUru).
  • Wondruss is a work-in-progress server with additional functionality, set to replace DIRTSAND at some point.

PyPRP2

  • Basic geometry available.
  • Support for MO:UL format.
  • Very incomplete compared to PyPRP1.
    • Help wanted!

Assets

  • It should be possible to create enough fan content to not have to include many Cyan assets. The big issue will be the global data. See below.
  • A letter has been sent to Cyan requesting a more permissive license for Cyan content. See the associated thread on OpenUru.
  • A new concept for the GUI of the Nexus interface has been proposed by Tweek.

Global Data

  • CustomAvatars wouldn't be necessary on an all-fan-asset shard (except for any of our own, of course).
  • GlobalAnimations has some things referenced in source code, much of it is only in assets (but those anims are useful for common things).
  • GlobalAvatars we're probably stuck with, unless we want to re-do all the necessary global anims in addition to creating new avatars.
  • GlobalClothing the only thing that should be required here is the default items. Everything else could likely be replaced.
  • GlobalMarkers is used for marker hunts. We could change the sounds and pictures stored here to customize markers. It's a small thing, though.

Special Ages

Startup: Tweek once designed a new Startup GUI. Perhaps it should be implemented for this?

AvatarCustomization: This is absolutely necessary, but I'm not sure whether we should just use Cyan's or write a new one.

Documentation

This is the work that needs to be done on the documentation of software features.

Python Files

  • There are lots of x*.py files to implement common features. They should be doc'd with the correct parameters in a way artists can easily understand.
  • On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver).

Wiki

  • All the tools need to be documented as new features are introduced. Work is currently underway to actualize the wiki.

Community and Sustainability

This is what needs to be done for the community and for the Guild.

Donations

  • Might be warranted/needed at some point.

Information Sharing

  • Should be much more open than Cyan. This seems to be our general nature anyway, so shouldn't be hard.