Over the last year or so I've started a bunch of mail lists. Basically one for each sub-project of the big project I'm working on. And a few more.  

Over the last few weeks, we've had a renewed interest in Frontier, in its most modern distribution, the OPML Editor. It's not actually all that new. I started it in 2005 when the Frontier-kernel list threatened to flame out. I was so tired of dealing with people's emotions. I just wanted to work on software. So I forked my own project, just to get some peace and quiet.  

It turned out pretty well, I think. The software needed some peace and quiet too. Some time for me to look at each of the components, to rethink where rethinking was useful, and to re-code, where that was necessary. The result is a much more mature development and runtime environment.  

http://hellofrontier.com/ 

Now there's confusion about which mail list users of the OPML Editor should join. I have an answer for that: 

http://groups.google.com/group/frontier-user 

It's a restart of a list that was very big in the late 90s. Lots of interesting people came through that list, and lots of interesting projects got done. It also was always on the edge of flaming out, which limited productivity. This time, however, there are excellent web-based moderation tools, and at the first sign of someone running a campaign to halt work, I'll just turn on moderation, and off-topic messages won't get through. So, in other words, it's fairly safe to join the list. And to would-be saboteurs -- it's not going to work this time. Find another place to vent your emotions.  

The list is quiet. Mostly just announcements. And there aren't many subscribers, but the people who are there are nothing short of a brain trust. So if you have a legitimate problem with the software, you can use this list to try to get an answer. 

Remember it's an open source project, so if people help you, they are doing it voluntarily, and without compensation. If you want a good response, provide a good question. If there's a file that has a problem, include a URL to it. Screen shots are a good idea too, because there might be a clue on the screen that you don't see that someone with expertise will. And remember to tell us what you were doing, what you expected to happen, and what actually happened. Saying "it didn't work, does anyone know why" isn't going to get you much help.  

Let's have fun!