wxcode-users

[wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[Ulrich T. <ulr...@gm...>]

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

Re: [wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[PGridDev <pgr...@ya...>]

Hi Ulrich, and thanks again for your recent work for wxCode.

Of course empty components make little sense, but I would not delete outdated ones --always had a hard time throwing old things away! To help users sort obsolete code from maintained one, we could:
   - introduce an option to not display them in the 'component search' of the website
   - use some CSS markup or a special field in the component list to issue a warning
The criteria for obsolescence could be for instance: (wxWidget version < 2.8) || (no maintainer)

I do not understand the reason for the shell/website access restrictions, it makes your job harder, but was there an issue ? At any rate I hope I still have access  :-)

Cheers,
Ronan


On 16/02/2011 00:44, Ulrich Telle wrote:
> 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

Re: [wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[Ulrich T. <ulr...@gm...>]

Hi Ronan,

> Of course empty components make little sense,

Especially if they stayed already empty for 4 or more years. So I'm
going to delete them - with one exception: the maintainer of wxUML
contacted me today to announce that there'll be probably a first release
in spring. The component is part of his diploma thesis he's currently
working on.

> but I would not delete outdated ones --always had a hard time
> throwing old things away!

I'm not going to throw away any component easily, but I feel it's
necessary to present to the wxCode users a tidy website not cluttered
with obsolete and/or outdated and/or unmaintained components.

> To help users sort obsolete code from maintained one, we could: - 
> introduce an option to not display them in the 'component search' of 
> the website - use some CSS markup or a special field in the
> component list to issue a warning The criteria for obsolescence could
> be for instance: (wxWidget version < 2.8) || (no maintainer)

Yes, I think it's a good idea to separate them somehow from the actively
maintained components. I'll check which option might be suited best.

Thank you for your feedback.

> I do not understand the reason for the shell/website access 
> restrictions, it makes your job harder, but was there an issue ?

Well, it's in fact only a precautionary measure due to the problems
SourceForge had recently. Only very few maintainers have published
online documentation for their components on the wxCode website. So I
don't see a general need to grant shell/website access to everyone. Of
course access rights will be granted to every maintainer who needs them.

> At any rate I hope I still have access  :-)

You have. :-)

Regards,

Ulrich

Re: [wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[Ulrich T. <ulr...@gm...>]

Hi Francesco,

>>> Of course empty components make little sense,
>> 
>> Especially if they stayed already empty for 4 or more years. So
>> I'm going to delete them
> 
> I agree...

The mentioned empty components have been removed by now.

> I think that we could just add a new category to wxCode DB "outdated"
> and put there those outdated components?

I added a column "outdated" to the components' table and flagged those
components stating version 2.4 as the highest supported wxWidgets
version as "outdated". Probably all components for version 2.6 and below
could be flagged that way, since I don't think they are usable with
version 2.8 without major adjustments.

The change is not yet reflected on the wxCode website.

> This way they are not displayed in the pages with other components
> but still are available to everyone (without having to search in the
> SVN repository history or things like that!)...

I intend to add a switch to the search/display components page so that
visitors can choose whether they want to see outdated entries or not
(where omitting them will be the default).

Regards,

Ulrich

Re: [wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[Francesco <f18...@ya...>]

Ulrich,
everything sounds good to me. Changing the search and the udpate website
script (for regeneration of the component lists) in order to include/exclude
outdated components should not be difficult... (I hope :)). Let me know if
you need help with the PHP stuff.

Thanks,
Francesco



2011/2/19 Ulrich Telle <ulr...@gm...>

> Hi Francesco,
>
> >>> Of course empty components make little sense,
> >>
> >> Especially if they stayed already empty for 4 or more years. So
> >> I'm going to delete them
> >
> > I agree...
>
> The mentioned empty components have been removed by now.
>
> > I think that we could just add a new category to wxCode DB "outdated"
> > and put there those outdated components?
>
> I added a column "outdated" to the components' table and flagged those
> components stating version 2.4 as the highest supported wxWidgets
> version as "outdated". Probably all components for version 2.6 and below
> could be flagged that way, since I don't think they are usable with
> version 2.8 without major adjustments.
>
> The change is not yet reflected on the wxCode website.
>
> > This way they are not displayed in the pages with other components
> > but still are available to everyone (without having to search in the
> > SVN repository history or things like that!)...
>
> I intend to add a switch to the search/display components page so that
> visitors can choose whether they want to see outdated entries or not
> (where omitting them will be the default).
>
> 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
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Empty components, unmaintained components, CVS info, shell/website access

[Francesco <f18...@ya...>]

Hi Ulrich, Ronan,




2011/2/16 Ulrich Telle <ulr...@gm...>

> Hi Ronan,
>
> > Of course empty components make little sense,
>
> Especially if they stayed already empty for 4 or more years. So I'm
> going to delete them
>
I agree...


> > To help users sort obsolete code from maintained one, we could: -
> > introduce an option to not display them in the 'component search' of
> > the website - use some CSS markup or a special field in the
> > component list to issue a warning The criteria for obsolescence could
> > be for instance: (wxWidget version < 2.8) || (no maintainer)
>
> Yes, I think it's a good idea to separate them somehow from the actively
> maintained components. I'll check which option might be suited best.
>
> Thank you for your feedback.
>
I think that we could just add a new category to wxCode DB "outdated" and
put there those outdated components?
This way they are not displayed in the pages with other components but still
are available to everyone (without having to search in the SVN repository
history or things like that!)...

 Again, keep up the great job Ulrich!

Francesco