> Sorry for answering off list again, I can not post to the list. That's unfortunate. I'm happy to post this to the list.
>>> There is one thing to mention about parsing tips. Are we going to put >>> the additional comments to the wiki? There are many useful comments >>> but there are also many useless junk. It would be _lots_ of work to >>> look at every comment and see if they're useful or not. What are >>> your ideas? >> The comments *are* a necessary part of the tip, and should be included >> with the import. In general, I would like to move 100% of the content >> from the tips on the vim.org web site to the wiki, even if some of the >> data doesn't fit very well into the wiki. After that, the tips >> information can be "refactored" as necessary by the community. > What I thought was that maybe it's possible to use SpamAssassin (or > some of its modules) while converting the tips, to at least get some > score that will make it easier to filter this later. I don't know if > spam assassin can be used in this way, at least part of the filters > are email specific, but maybe some are general. > > Moshe I think we should focus on a non-automated solution for filtering comments. Basically, I think that we'll convert all of the old tips to the new wiki with all of the content, metadata, and comments. 90 % of those tips will stay that way forever since they're fine just the way they are and require no comments or updates. The commonly-used tips, however, will be refactored according to community's preferences where comments (along with metadata) will be merged or deleted.
