Since I received some complaints about the current state of wxCode I
started to inspect the components hosted by wxCode.

All in all there are 91 components listed in the wxCode database.

I detected 6 *empty* components for which never code was being uploaded:

wxCoolBar           (4 years)
wxMemoryMappedFile  (4 years)
wxUML               (8 months)
wxAudio             (5 years)
wxBetterDialog      (6 years)
wxDom               (5 years)

If noone objects I'm going to delete those "components".

Then there are currently 22 officially unmaintained components. Several
of them are in fact outdated, i.e. last supported wxWidgets version 2.4.
IMHO several of them clutter wxCode without being of pratical use anymore.

At last there are quite a few (about 40 to be precise) components which
don't seem to be actively maintained anymore as the highest supported
wxWidgets version stated in their description is 2.4 or 2.6. From my
point of view it's understandable that several visitors of wxCode feel
disappointed.

What should we do with these components? I'm open to suggestions.

CVS update: In the meantime I set the wxCode CVS to read-only access. 5
of 20 maintainers of prior CVS hosted components gave mainly positive
feedback.

Additonally I restricted shell and website access to those maintainers
which actively upload for example the documentation of their components.
Feel free to contact me in case website access needs to be restored.

Regards,

Ulrich


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
wxCode-users mailing list
wxCode-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxcode-users

Reply via email to