Re[2]: [TWiki-Dev] Attic webs

[Rafael A. <sor...@ya...>]

Peter,

This is not a problem of managing "Stale Content". Is more a problem
of the tremendous chaos that is Codev.

I ask "What is the purpose of Codev"? I see it has several uses:
   1. Brainstorm Ideas, that later are made into Features
   2. Report Bugs and Issues
   3. Serve as a place to store... interesting stuff (Howto's, links
   to the competition, etc)
   4. Track & Announce releases

As such, Codev has accumulated too much "cruft" over the years because
it's was overloaded" with too many responsibilities.

Now, we can see that some of the responsibilities of Codev are being
moved to other places:
  2. Report Bugs and issues: This is being done in Support and Bugs
  4. Track & Announce releases: Tracking is being done in the Bugs
  web.

What I think that we should do is:
   * Move all the Bug reports, feature done and release tracking
   topics "out of the way" (Attic?).
   * Either move all the Feature brainstorming discussion to a
   Development web, or all the "interesting stuff" someplace else (I
   vote for the former, as I think it's easier).
   * Use each place for it's function, and only that function alone.

I strongly disagree that tagging content will help. It won't help the
WebChanges being flooded with content I don't care about while moving
out of the page the content I *do* care (no, I *don't* want to use the
RSS feed), nor it will help the severe performance impact in search
while looking through 4000+ topics, and won't help when I look for
information about the META PI and I need to scan 500+ unrelevant
topics. 

Think about this: If you are looking for information that you've never
look at and don't know how to classify, what is your first choice:
Google or del.icio.us?


-- 
Best regards,
 Rafael                            mailto:sor...@ya...