Sorry for the long post (I've been away, ...

At the moment I think that the 'New development announcements' is absolutely vital as it takes information from the many places that developers put it.
I second the scrapping of the Web-links
Regarding 'ContribsForSME6' this wouldn't scale to the number of contribs that we have - there needs to be some kind of structure as there is on the main 'How-to%20Classification' page.
I agree that the Announcement process is too much, but in practice various parts of that are done. But how should things be announced - often they only go to Devinfo or either Experienced or General fourums - I don't think that this will change. (I have a change proposal lower down)
My comment to this thread is that we need a fundamental review of how contribs are handled.
0) How to store RPM contribs. Often a topic on Devinfo and relevant here.
1) Find a lite way to annouce contribs - and get it agreed on Devinfo or at least some of the prolific developers.
2) Work out how the information can be maintained easily - ideally seperate the data from the presentation. Can Monkey help here?
3) Work out how to allow comments on the contribs and have this fed back to the developer.
If we had the data stored in a database rather than the wikipage the list of contribs for version X or popularity could be easily generated rather than having more hand-crafted pages such as 'ContribsForSME6' (which serves a useful purpose, but I don't think is sustainable)
I will have a lot of time in December - but it would be nice if the effort was useful.
As a short term change should we modify 'ContribsPage' so that it goes
* intro (but only the first two lines)
* How To Classification
* Contribs
* Web-links
As another short term change as the announcement process -
step 1) make clear this is optional
step 2) Post to Devinfo or Experienced forum
Then we accept that it needs some 'Doc' work.
(I can change this if you agree)
Finally does the doc email list work? Or is it just a case of needing to re-register (again)?