From: Ulrich T. <ulr...@gm...> - 2011-02-16 18:15:49
|
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 |