language for the tags and search capacity on those tags
enticing/rewarding people to tag (“Bootstrapping”?)
Solution? Seed tags with automated material, make it easy to see
change logs
document contexts
Solution? Wizard as a tree-selection (“is this a horse?” “how is it NOT a horse?”)
Solution? Wizard asking direct, thought-provoking questions
Solution? reward by searched tag success (best searched tags are worth more to the author of that tag)
tagging old source
Write sentences and extract terms from those instead tags directly.
attach tags tightly to some specific source (source, blog, doc)
automation of tag extraction
automatable
scalable
many languages
fingerprint used APIs
“gaming” the tagging system, evil taggers, etc
DOAP adoption is slow (Debian rule? like manpages?)
Is there a license for APIs? (Use, but not take advantage of.)
Gather comments about functional relationships between two areas of code.
Getting to block and line addressability for commenting.
What makes sense for filtering or guiding relevance?
Copyright on the tags themselves, or the data exchange?
Possible new Aspect tags
Automatic tag similarity discovery, tag context clustering
Best-Practice for manual tagging
Wizard for just describing a project's capabilities.
Find short piece of code, see what could say about it
Documenting software patterns/ideas
Time-stamping is a well-solved process. Could use more date-associations being made. (ha ha:
http://nethash.org/)