search

realXtend / tundra

realXtend Tundra SDK, a 3D virtual world application platform.
www.realxtend.org
Apache License 2.0
84 stars 70 forks source link

Make a new repository ("TundraApplicationPlugins" or similar) for lesser used plug-ins #650

Closed Stinkfist0 closed 11 years ago

Stinkfist0 commented 11 years ago

The current Tundra repository contains lots of plug-ins that have been maintained (or used) very little or not at all for a long time. These plug-ins should be moved to their own repository. This new repository could also contain more experimental plug-ins that wouldn't need "strict" code review before accepting them.

antont commented 11 years ago

+1 for reorganizing somehow, some food for thoughts about how exactly:

  1. how about the idea of a Tundra SDK repo? was discussed and planned quite a lot earlier. i.e. a minimal Tundra core sdk repo which would be used as an SDK when building applications, or plugins.
  2. in some cases the right granularity for plugins is to have a repo per plugin. for example Yan, visiting Oulu from Hong Kong till September, is currently working on an OpenNI plugin based on what I started earlier. He is not interested in touching other parts of Tundra, just work on that one plugin, so seems that a repo for that plugin would be best fit.

git submodules seem to work nicely to aggregate things to convenient wholes, like Sirikata has one master repo (kind of like current Tundra + deps) where core, modules etc. are as submodules. so it is easy to get and build the whole package, but the parts are still organized sensibly.

anyhow to help with the current situation and to have one place where to dump kind of rex-originated more esoteric plugins the original proposal here may be fine.

cadaver commented 11 years ago

Organization-wise it would be least hassle to decide the application plugins that will be included as part of the official releases, and keep those + the core in the "base" repo. Those are the ones that require going through pull request review.

Then, everything extra could be in extra repos, or several of them, but they would no longer be referenced by the core BuildConfigTemplate / CMakeLists.

Stinkfist0 commented 11 years ago

Canditate plug-ins to be moved to the new repo: -BrowserUiPlugin, -CAVEStereoModule, -EC_LaserPointer, -EC_PlanarMirror -KinectModule, -PythonScriptModule, -VlcPlugin (Admino has stopped maintaining this BTW), -XMPPModule, and -SceneWidgetComponents.

jonnenauha commented 11 years ago

I think that list if fine if core does not want the widget components and vlc functionality. Both are still maintained by us, that has not gone anywhere. We just wont be implementing new functionality to them. They will stick in Meshmoon Rocket distributions still for a long time.

Anyways both of those provide great, working components and are fully integrated to both Mac and Windows build chains for core. But ofc if we want to slim down core functionality that's fine too :)

Stinkfist0 commented 11 years ago

Nothing against having SceneWidgetComponents in "core". VlcPlugin however is not a good core plug-in IMO as it's usable only when doing 32-bit VC9 builds on Windows.

Stinkfist0 commented 11 years ago

https://github.com/realxtend/TundraAddons