KendraBaseWhy

KendraBase, first mentioned in [this email] on [kDev], is the name we're giving to our information cloud or object store.

• Why KendraBase? { [Ref] [Ref] [Ref] }
  • In order to create KendraSystem we need to gather requirements from many, many different individuals and organisations in the content value chain. We need tools to assist with this information gathering process. Which must have features:
    • Not reliant on people gathering at the same place and/or time.
    • Enable people to talk in their own language and use their own terminology.
    • Enter and query structured information.
  • It could, in fact, be the basis for KendraSystem.

• Why not use currently available tools (Wikis, Blogs, Forums, Polls and Email Lists)? { [Ref] }
  • Because they don't fulfill the requirements of the KendraBaseProjectPlan.
  • Because you are at the mercy of the packages you use it terms of what features are in or out and what direction the package development takes.
  • Because the time taken trying to hack the software to get it do what you want could be better spent on developing exactly what you want.
    • This process could fail. It could be a blind alley. Perhaps the package's object model is just not fine-grained enough for our purposes.
  • Current collaborative software:
    • Doesn't interoperate smoothly.
    • Are hostile environments - prone to flaming and ramblings. Doesn't shield users from this.
      • Why not turn on moderation on all posts?
        • The work load would be immense. Would rather use a non-hierarchical rating system like [Slashdot].
    • Make it difficult to track the thread of ideas.

• What are the benefits of having a homegrown system?
  • Autonomy - we get to control the direction and features.
  • We will have a product that will hopefully attract developers.
  • Gives something tangible for people to relate to.
  • Better for funding/sponsorship purposes.