1. Blogware Aggregator (inc. Newshub, Blogware native as well as RSS feeds) The main point of this function will be to allow publishers a quick and easy way to aggregate content, review it, manage it and post the ones that they like directly to their blog in a simple and efficient way. This isn't for readers, that will come next - we need to worry about the post function more than the readers function at this point. ;)
    • medium-high to high.
  2. MakaWiki We could almost turn this into a wait and see while we figurre out what the value proposition is. Its not clear who will be using this or what - but the extra-dimensionality that the feature will add to the typically linear progression of the blog is an interesting development. Let's chat more about this one when we get a chance. Maybe we should install some tools into the sandbox to further explore the what the technology has to offer.
    • low-medium.
  3. POD This is a great idea, but its not clear how web hosting companies will be reacting to the offering. If it turns out that we are evil scum villains, then PODs will need to rise quickly to the top of the list - if no one raises any objections, then we can take it off the list. The trick will be figuring out what to do when the reaction occurs (as it should) somewhere within that continuum. My preference is to wait and see what the market has to say while continuing to think about potential features. Note that this is not a feature that has been designed for "HP" and their internal corporate communcations requirements, but instead is conceived as a solution to the "I want to use my disk and space" issue that we might encounter.
    • wait and see.
  4. Marketplace (automated permissions expiry) I love this feature, I want to do it now. We need to get a better sense of the market before we can increase its priority, but the sheer coolness of the idea will at very least set us apart from the dreary competition. If we can get even five or six publishers using this effectively, they will likely be influential and talk about it. Which, at least, is worth something from a publicity perspective.
    • Medium.
  5. Notify on post (no digest mode, uses templates for emails) Notify readers that is. This should use bots, or a variant, to allow the publisher to script what goes out.
    • High
  6. Community features (top blog, most recent post, newest blogger, most popular, least popular, trackback mesh (like a webring) These are actually ndividual features that will be prioritized on an "ease of development" basis and banged out on a recurring schedule as TVs that we can implement FCFS into www.
    • Ultra-high.
  7. PhotoRSS Self-explanatory. We need to allow for this. Absolute links in the RSS pointing back to the original image. Its simple and doesn't break the spec (AFAIK)
    • Medium.
  8. FTP Upload 'nuff said.
    • High.
  9. templatable RSS We've talked about this quite extensively. If we can knock it out fairly quickly, then we probably should. If not, then we might want to leave it for a rainy day.
    • Low.
  10. URL Templating Same here. I would love to give users the capability to set their own URLs, but the performance tradeoff might not be worth it.
    • Low.
  11. Allow publisher to select sticky defaults that get used to govern XML-RPC posts. 'nuff said.
    • Done.
  12. Auto-gen entry excerpts (using first n words from article body) Should be self-explanatory.
    • Medium.
  13. Allow post article from file manager to photo album or text blog. WE NEED THIS!!
    • High.
  14. Per category RSS Look into this, we might already have it - document or expose better.
    • ??
  15. Allow publisher to specify that basic HTML (bold, ital, ul and link) should be allowed in comments and replies - the default is "escape html"
    • low to medium. (niggly thing that should be fixed)
  16. Manage multiple weblogs (bugfix)
    • Really freakin' High.
  17. Post to multiple blogs.
    • Really low - wait and see.
  18. Fix UI Like, duh!
    • High.
  19. Search my blog We will need some notion of indexes and keywords dropped into play.
    • High.
  20. Kickin Stats! We will need to determine what's important and what isn't. Hitcounter doesn't go far enough, analog goes too far.
    • High.
  21. Post via mail For the moblogging crowd.
    • Medium.
  22. Emailed when someone comments on your blog. Definitely a community promoter. We might want to consider adding this as an additional chargeable feature. (comments?)
    • High.
  23. Comment stats, brief overview of comments (most recent etc) This is a publisher centric solution that provides basic reports to publishers whereever we decide to stick them in the UI,
    • Medium.
  24. "Mark Comments as Unread" function. Refer to "More on 'Mark as Read'"
    • Medium to High.
  25. Paging to work on day/month views Well, let's look at it this way. Let's settle on implementing the minimum working model that doesn't kill the database. We can make it better as we progress.
    • Low to Medium.
  26. Related posts This can be done manually or programmaticly. (ie - a search which lets you check off titles of previous posts and then go on to post the new article... like related items in a shopping cart.)
    • Medium.
  27. Rotating entries in a particular template. This really is MOTD - where "M" equals "media", "message" or "method".
    • Medium-low.
  28. Last n Entries template (recent posts).
    • Medium to high.
  29. (WYSIWG Editor/Bookmarklets/Blogroll-let)
    • The most extreme version of high that exists before we are publicly embarassed.
  30. Notify to blog (when photoalbum is updated) Mini-editor within post photo to album interface that allows you to simply add a title and description that says "Hey, I posted some pictures that might like...link, link" etc.
    • Medium.
  31. Domain name upgrade.
    • Kill? Ask Eric.
  32. Invite Readers/Authors/Admins
    • High
  33. Keywords for articles
    • medium
  34. BlogwareQ
    • Top Secret