I have set up a test TinyMCE in ILOG, and started inviting people to tes.
One thing that would be great however, is that you maintain a page somewhere
that states what is known to not working (tables) in the latest porototype so that my
users will not spend energy testing it first guinea pig: "why cannot I upload
a file while editing?"
Especially for us, the features that were present in kupu but not in tinymce
should be stated
Also, if you want the tests to focus on a specific area, please say so.
- 07 Sep 2007
page on this web lists all open bugs that affect the integration. Or did you want something else? It's an awful lot of work to maintain a separate bug database just for this extension, and I'd rather not have to do it, as it just takes time away from bug fixing.
As for specific test areas, I'd rather not say. i don't want everyone to end up testing in the same areas, so I'd rather people just tried to break it. They will probably succeed.
Not going to do this. The Bug DB and the FAQ should suffice.