"Must Fix"

1. Allow publisher in their control panel that basic HTML (bold, ital, ul and link) should be allowed in comments and replies to their blog entries.
2. "Articles" Tab not selected in "Edit" mode. (When editing an article, the Main Menu tab is highlighted instead of Articles. )

"PV7 Target List"

1. Community stats
   • top blog
   • most recent post
   • newest blog
   • most visited blog
   • least visited blog
   • most referenced blog
   • least referenced blog
   • follow the trackback mesh
   • random blog
   • random post
   • random comment
2. Marketplace (automated subscription expiry)
3. Allow post article from file manager to photo album or text blog.
4. Post via mail.
5. Import OCS into Favorites.
6. Import OPML into Favorites.
7. Add excerpts to Trackbacks. Optional trackback display in each or none of body, mail, trackback and RSS.
8. WYSIWYG editor (for comments and articles).
9. "recent comments" component
10. "recent articles" component
11. "recent trackbacks" component
12. "recent visitors" component

"Fixes/Deficiencies" (should be in BugZilla?)

• Invite Poster should be Invite Author
• Pager Settings should be renamed "Navigation settings"
• Rename "Template Variable" to "Entry Tag"
• Blogwide should be "Blogware-wide"
• remove email address column from Notifications Page.
• Notifications should be "Subscribers" and be linked to from the Dashboard, not "Settings".

1. password reminder function should ask for "username" -or- "email address" -or- "hostname" and mailout info based on this data.
2. use time *and* date in dashboard stats...
3. include "total number of entries/trackbacks/comments" that live in the blog in the Dashboard view....
4. rename "Main Menu" - "Dashboard"
5. rename "Articles" - "Article Manager"
6. Category Explorer needs a label
7. after creating photoalbum, link says "click here to view" photoalbum, but links to the photoalbum settings. Either we need to link better or describe better.
8. photoalbum should have "small, medium and large" upload settings.
9. uploading an image that is smaller than the specified size shouldn't error, it should simply leave the image to its original size.
10. "photo title" should be renamed "photo caption"
11. "Photo Body" should be renamed "Photo Description"
12. Avoid Time Paradox.
13. File manager needs "Show N results" drop down.
14. File manager and categoryu manager labels need click sort options.
15. Add "Add Favorites to Layout" in "Edit Favorites" mode.
16. Friendly Title/Label conversion - label normalization that can be overridden as an advanced option.
17. File manager entries should be alpha sorted.
18. directory indexing should be off.
19. Escaping Characters. This needs to be handled much better. (ie - from Guile: I know some of us covered this in some email yesterday, but I bring it up for two reasons. One, I think the best logic to figure out whether or not to escape an & is to check if there's a semicolon following an ampersand without a space in between. So & or ’ aren't escaped, but "& so on;" is. Two, because I think this can be used throughout the product, not just in Blogrolls Favourites. I got an email when Joe commented on an article yesterday that said someone had posted a comment at "Guile's World". )
20. The default templates should link the blog tite to the root of the blog. Currenty it is not a link.
21. Control Panel and blog category pages should have titles which denote their function or their "title" (in the case of blog categories).
22. Comments (and articles for that matter) should show the date as well as the time.
23. Auto-link url's unless "don't auto-link urls" is checked for posts and comments.
24. The bookmarklet should save the last "favorite list" that you added to as the new default.
25. The bookmarket goes behind the current window in Firebird (same problem with "post an article" bookmarklet). This needs to be fixed.
26. validate all xml output
27. gen both rss
28. Allow a reader to log in directly from error pages if they aren't logged in and specificy that logging in, if they have an account, is appropriate behavior, and if they don't have an account to point them to the signup page.
29. Allow a reader to log in directly and submit a comment simultaneously. See mockup
30. blog.blogware.com
31. Different image in the category tree to indicate if one is a photo album or text category.
32. respect new line in comments by default, allow publisher to change default.

Futures (unprioritized)

• Keywords for articles
• Blog Stats!
  • Stats Summary
  • Daily Report
  • Referrer Report
  • Referring Site Report
  • Search Query Report
  • Search Word Report
  • Browser Report
  • OS Report
  • Posts Report
  • Category Report
  • Posts Filter
  • Category Filter
• Blog search (with category granularity).
• Blogware-wide search
• Files must be "designatable" as secure.
• Create a method by which a blog publisher can add a persistent description to various cateories. Should allow for different descriptions for each category. Used to provide more information about ht econtents of a category.
• We need a secure file directory that respects category permissions.
• Publishers should be able to prevent Readers, on a username basis, from accessing all blog content and separately from reading and leaving comments (3 restrictions).
• Publishers should be able to specify time and date formatting from the control panel.
• Publishers should be able to embed time and date formatting into their templates by hand.
• Publisher should have a method to return to their last Article List view after editing an article and saving their changes. Currently, the only way to do this is to click the "Articles" tab which doesn't know the state of the prior list.
• Article Editing: Trackbacks. The link to view trackbacks from the article editing page is broken. I guess this actually qualifies as a full-fledged bug, and I'll try to remember to add it to Bugzilla after I post this article. - Fixed.
• Publishers should be able to add a "font sizing" component to the layout manager for use by their readers.
• Investigate using mod_gzip on the server - implement if feasible.
• Trackbacks should work if secured point-to-point within Bware....kinds of defeats their purpose for internal lan-like applications if they don't.
• It would be nice if there was an "edit this article" button for the blogowner. It's a pain to go into the backend and find the article to edit it. This would appear on both the category level as well as the article level. - done!
• create a "print this article" link that would should show the article in a print friendly format. Linked to from the entry permalink page.
• import from other CMS
• export to archive for publisher/reseller retrieval
• Allow publishers to view a list of all people who have subscribed to my blog via email alerts.
• I just tried to post a comment, when I hit submit, I was greeted with: "You need to log in to post a comment". That should appear in the place of the comment box if anonymous posts are disallowed.
• The blog owner should be able to specify that anonymous comments include name, email and url fields. The name could be prefixed with: "non-blogware user"
• Comments need permalinks
• Readers should be able to "subscribe" to an article and get emailed all comments for that article.
• When a reader subscribes to a blog, I should have the option to get emailed all comments posted to that blog.
• ability to include HTML in comments.
• notify a publisher when a Reader subscribes.
• extend HTML editor to comments editor.
• Spell-checker for comments and articles.
• Reader's info from comments listing and elsewhere needs to be consistently linked up to their url and or email address.
• what is that "PV5 thing that just popped up in my post? It only show's up in "preview" mode - fixed.
• The bookmarklet should allow you to create a new favorite list.
• Need to implement a "find blogware userid" function for authors and publishers?
• If you change or add an article to a category that is not restricted, and that article was previously restricted, you should get a warning.
• provider authors the capability to write text entries into templates without the entries showing up as part of the regular blog.
• allow html in comments - done
• allow publishers and authors to post text to photo album without associating the text with a photo.
• provisoning server deets?
• need to be able to change default blog in the quickpost bookmarklet.
• formatting doesn't properly display in "preview" mode for comments.
• dates on article pages and comments - duplicate
• next to each article, a count for the number of comments to date, if not at least an indication that there were or were not any comments so far.
• If you have posting or other rights to a blog, display the lock next to categories as we do in the backend.
• As a reader, show me a list of all blogs for which I am subscribed to receive email.
• Be able to click a link within the email to unsubscribe myself
• If not posting a comment anonymously, allow me to choose whether my username is linked to my web site or some sort of a vcard. - folded into foaf support plan.
• Notify blog owner whenever someone signs up to get my posts via email and provide some minimal data on that user.
• Add comment posting option which requires anon users to type in the word found in some oddly shaped image as a criteria for posting anonymously. This would be to prevent automated anon posting.
• Themes (No access to customize templates)
• Provide system widgets for the layout manager area
• technorati integration
• persistent category panel in subcategories

"Pended"

• Post via MMS -> mail Also for the moblogging crowd.
• Allow reseller to pre-define options for particular packages which they create. The packages may not necessarily have different prices from Tucows but can allow the reseller to control what his clients see. So he can give luser clients less options while he gives advanced clients the full gamut of features.
• Stats on users who have opened my mail, for those who have requested notifications. Can be done by adding a reference to an image which is a unique identifier.
• Allow me to define some sort of character to be associated with my comment posting, an image of sorts.
• Allow blog owner to define the max frequency with which any IP# can request my RSS feed, so I can control my outbound bandwidth.
• Allow reseller to specify default text in various message for end users as found in the blog admin general settings.
• Specify popular languages (Russian, Spanish, etc.) for Paging links in settings area.
• For a given article, it would be nice to see a different image if an article used to be locked and now is not or vice versa.
• Extend category tree to the user facing blog as an option.
• when looking at the list of recent articles publisher should see a count for the number of people who received the email notification, linked to the actual list of usernames.
• allow subscribers to subscribe to notices with digest and real-time options.
• upgrade layout manager to include "drag and drop" functionality
• implement a "staging area" for use with the layout manager.
• "show comments inline" with article entry (ie - http://shanni.org/) Provide option for blogowner to always show comments inline
• ability to easily include emoticons in comments. example: http://www.shanni.org/blog/mt-comments.cgi?entry_id=1202
• blogowner can flag that certain users always need moderating and/or certain users never need moderating, also, perhaps a threshold so that if someone posts 4 good comments, they have passed the threshhold and go into the "no moderation needed" group.
• The blogowner should be able to moderate comments. i.e. all comments must be approved before posting.
• 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. ;)
• 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.
• Post to multiple blogs.
• 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) - no plan to support.
• "Mark Comments as Read/Unread" function. Refer to "More on 'Mark as Read'"
• 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.)
• Rotating entries in a particular template. This really is MOTD - where "M" equals "media", "message" or "method".
• 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.
• 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.
• 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.