05 December 2004

Special note to readers of Jeff Barr's Blog

Thanks for the plug, Jeff.

I thought it might be useful to share a few thoughts on what Mug's Tests is about: As an end-user, stress-test publicly available XML-RSS products and identify issues with human-RSS interface.

Goal of the Mud's Tests blog is to inter alia:

  • provide constructive feedback to XML-RSS developers;
  • share end-user experiences with products;
  • give developers a fresh look at their products;
  • document for users errors with RSS-validation;
  • suggest improvements to validation-error reports so that users can fix their blogs; and
  • outline "user-view" solutions and approaches to address issues.

    One example: RefThis was after reviewing several comments while testing Feeddemon.

    Also, just after MyYahoo released from beta the "Add this RSS feed to My Yahoo", we did testing on the integration between the button and the various feeds and browsers.

    Philosophy

    The blog is about moving forward, not just commenting. It's about contributing to new things.

    In many cases, the developers have already noticed the issue and are working on a solution. However, in some cases, the user notices something new.

    In short, rather than simply say, "This is wrong," the blog hopes to aggregate the common problems other feed-users experience, and outline an approach that might address the core challenges.

    If we notice trends, problems, or recurring problems in the RSS-products, we'll outline a larger vision of what might be a solution. Obviously, whether the proposed solution is implemented is up to the XML-RSS community.

    Also, the blog hopes to share with other users the nature of error reports, workarounds, and identify whether the issue is something that needs new attention.

    Open Invitation to Developers

    If you have a specific requirement to have something test-run, feel free to leave links in the most recent blog-entry, and desired feedback.

    State your deadline, turn-around time, and whether you want a quick-look or a comprehensive analysis with a thorough test report.

    Current blog shows a range of feedback on various products. If you desire something different or specific focus of a test, would be glad to provide developers with something more suitable.

    Public report format

    The various blog-entries give a sample of the tone, length, and structure of test-run reports. This will give you a starting point to calibrate your request as in, "something like..." or "avoid....", etc.

    With time, certain products in the RSS pipeline may have more formalized test-plans and templates, while others may be more "first impression" and less formal. Flexibility is a good word.

    Good luck to all developers. I appreciate the hard work you are doing and understand there are some aggravations with XML. I'll do what I can to help.

    Mud
  • Thanks for the plug, Jeff.

    I thought it might be useful to share a few thoughts on what Mug's Tests is about: As an end-user, stress-test publicly available XML-RSS products and identify issues with human-RSS interface.

    Goal of the Mud's Tests blog is to inter alia:

  • provide constructive feedback to XML-RSS developers;
  • share end-user experiences with products;
  • give developers a fresh look at their products;
  • document for users errors with RSS-validation;
  • suggest improvements to validation-error reports so that users can fix their blogs; and
  • outline "user-view" solutions and approaches to address issues.

    One example: RefThis was after reviewing several comments while testing Feeddemon.

    Also, just after MyYahoo released from beta the "Add this RSS feed to My Yahoo", we did testing on the integration between the button and the various feeds and browsers.

    Philosophy

    The blog is about moving forward, not just commenting. It's about contributing to new things.

    In many cases, the developers have already noticed the issue and are working on a solution. However, in some cases, the user notices something new.

    In short, rather than simply say, "This is wrong," the blog hopes to aggregate the common problems other feed-users experience, and outline an approach that might address the core challenges.

    If we notice trends, problems, or recurring problems in the RSS-products, we'll outline a larger vision of what might be a solution. Obviously, whether the proposed solution is implemented is up to the XML-RSS community.

    Also, the blog hopes to share with other users the nature of error reports, workarounds, and identify whether the issue is something that needs new attention.

    Open Invitation to Developers

    If you have a specific requirement to have something test-run, feel free to leave links in the most recent blog-entry, and desired feedback.

    State your deadline, turn-around time, and whether you want a quick-look or a comprehensive analysis with a thorough test report.

    Current blog shows a range of feedback on various products. If you desire something different or specific focus of a test, would be glad to provide developers with something more suitable.

    Public report format

    The various blog-entries give a sample of the tone, length, and structure of test-run reports. This will give you a starting point to calibrate your request as in, "something like..." or "avoid....", etc.

    With time, certain products in the RSS pipeline may have more formalized test-plans and templates, while others may be more "first impression" and less formal. Flexibility is a good word.

    Good luck to all developers. I appreciate the hard work you are doing and understand there are some aggravations with XML. I'll do what I can to help.

    Mud
    " />