The Father's Day Weekend Bootstrap Party Invite

Posted by Dave Winer, 6/16/05 at 2:46:26 PM.

This is a cc of the email that went to the Gang of 25...

First, thank you for volunteering to help us test the Windows version of the new OPML Editor application.
 
We're about ready to start with the second group of testers, and you're one the 24 people in this group.
 
 
Focus
 
The focus in this group is:
 
1. Windows.
 
2. Podcasting directory authors.
 
3. People with workgroup applications.
 
4. Developers.
 
 
It's the second step in the bootstrap of a community
 
Our goal in this round is to determine whether we can do a broader round, with perhaps as many as 200 people in the group. We want to know if the documentation answers most of your questions. We want to know if you can use the software to edit OPML files, directories, instant outlines, XML files. We want to know if you hit walls, or deal-stoppers, things that make it impossible to use the tool for its intended purpose.
 
We know that the product does not at this time have a complete feature set, and that it has display bugs and will under some circumstances crash and lose data. One of our goals with this release is to attract the developers we need to serve a larger community of users. It's a bootstrap.  
 
 
What happens next
 
Dave Luebbert will send you an email with instructions on how to join the OPMLSUPPORT mail list. This is a requirement for this stage of testing, and it will be our primary way of communicating.
 
I will send you an email with your password for http://support.opml.org/ which is where you'll find the download and documentation. There's also a weblog there, and a discussion group. It has an RSS feed you can subscribe to.
 
Anyway, that's the plan. We're basically ready to go. It's exciting!!
 
And thanks again for joining our group. We totally look forward to working with you.
 
Dave
 
PS: You may write about the software publicly, on your weblog, on mail lists, where ever you want. However you may not reveal your password, or the contents of the website, or posts on the mail lists, until the software is publicly released. This requirement is necessary so that we can fix problems before the public release.