Archive for October, 2010
Over the past week, BrianH has been busy with migrating the issues, bugs, and tasks from our existing Mantis bug tracker to the new YouTrack installation. All of the open tickets have been migrated and even their issue numbers have remained the same. In short, the migration was a success and BrianH will follow-up with a technical post on how he did it.
If you ever filed a bug or commented on one, you should have an account already created for you. However, you will need to reset your password. Just head over to the YouTrack login page and request the reset email.
Most of you suspect you’ve never heard of YouTrack and may wonder why we decided to switch to it. When I looked at all available options—and I looked at a lot of options—I realized what we needed the most was a tool that would make it super easy to cut through the data. YouTrack’s query language is amazingly powerful and is consistently available for searching, reporting, and creating release notes. It’s simply well thought out.
Aside from the query language, YouTrack has a convenient keyboard-friendly design that enables power users to navigate through search results quickly and update, annotate, tag, and comment all at the same time with minimal keystrokes. In short, it’s really efficient to work with.
Next, YouTrack also provides a voting feature. Yes, I said voting. Finally, you can participate in prioritizing what issues need the most urgent fixing. Please take advantage of this as it really helps us figuring out what you think is in need of immediate attention. To vote, you’ll just need to create an account. That’s it.
As with Mantis, YouTrack also has commenting and watching issues, but it works better by sending immediate emails when status changes happen or new comments are added. A big plus when we need to get more information and there is no other means to communicate with the reporter of the issue. In Mantis, we had to close quite a few bugs, because those who reported them never checked back in to read our questions. That was unfortunate.
Lastly, YouTrack has a very handy issue reporting bookmarklet (accessible from the issue submission form). You can drag it into your browser bar. When you need to file an issue for your installation or on developer.mindtouch.com, you click it and it immediately opens an overlay window, which allows you to file the issue without losing context. Both the bookmarklet and issue submission form also make it easy to attach a screenshot thanks to a bundled java applet.
My hope is that YouTrack will enable much better communication and management of submitted issues. We’ll be porting our Mantis DekiScript Templates next week, which should be the last piece in the migration.
Hope you enjoy our new bug tracker and keep filing away!
MindTouch version 10.0.3 is the latest stabilization release for the Olympic family of products (MindTouch 2010, MindTouch Platform v10, MindTouch Core v10).
This release contains 106 bug fixes. See the Changelog for complete details.
The 10.0.3 release is available via updateWiki.sh (for VM users) and a source tarball. RPM, DEB, and MSI packages will follow shortly.
MindTouch has recently announced a timeline for the decommissioning of Wik.is deployments. In order to continue to support the growing needs of our MindTouch Express/Wik.is users, we are providing migration options – all of which ensure your data’s integrity.
MindTouch Cloud – Similar to Wik.is, a fully hosted collaboration solution, perfect for teams and workgroups. Available for 10, 25 or 50 user deployments. To begin the process of migrating your Wik.Is instance to MindTouch Cloud, please click here.
MindTouch Core v10 – Free and open source, MindTouch Core is the industry’s most popular community-supported collaboration project. Ideal for developers and technology enthusiasts. If you are already running MindTouch Core, you can easily migrate your Wik.is site data by following these simple instructions.
No longer using your Wik.is site, or have no plans to migrate? Let us know and we’ll remove your site immediately.
Be sure to check the MindTouch Developer Blog for more updates on this announcement.
As part of my internship here at MindTouch, I’ve been investigating the use of Virtual Box as an alternative to VMware for the MindTouch product download package.
VirtualBox is an open source virtualization solution, originally developed by originally created by innotek GmbH, purchased by Sun Microsystems, and now developed by Oracle. Similar to VMware, it is installed on an existing host operating system; within this application, additional guest operating systems, each known as a Guest OS, can be loaded and run, each with its own virtual environment. As such, it’s fully capable of running the MindTouch VM.
To get community feedback on new delivery mechanism, we’ve posted the download package on the developer community – you can find the instructions here. It’s very simple and lightning fast – I’m confident you can be up and running in less than 5 minutes. By using VirtualBox, we’ve potentially simplified deployments on Windows, Linux or even OS X. The MindTouch VM will run in a fully functional and isolated environment – we’ve taken care of the infrastructure requirements for you – web server, database, etc. Everything is packaged and ready-to-go inside the MindTouch VM.
If you happen to an existing VirtualBox user, you do not have to install additional programs to run MindTouch. Follow this guide to get your MindTouch VM up and running.
If you have any questions regarding running the MindTouch VM on VirtualBox, feel free to provide feedback here on this blog post, on the download pages provided.
Because so much of what MindTouch is asked to do is display content and thus spread intelligence around topics, we choose to adopt a philosophy of Progressive Enhancement when choosing which browsers to support. For anyone unfamiliar with the concepts of browser support, Yahoo has done the Web developer world a great service by outlining which browsers their UIs will support and why. Moreover, we at MindTouch will follow Yahoo’s lead in supporting A-Grade browsers when testing and assuring the quality of our products.
Citing the Yahoo standard, in internal memo from Steve Bjorg, our CTO says:
A-grade browsers are identified, capable, modern and common. QA tests all A-grade browsers, and bugs are addressed with high priority (e.g. IE8, Firefox 3.5, …).
X-grade browsers are assumed to be capable and modern. QA does not test, and bugs are not opened against X-grade browsers (e.g Opera, Conqueror, …).
Steve also goes on to mention IE6 specifically which is officially an A-Grade browser for users who are on Windows XP.
Now, on the other hand, I am on a Mac, running Mac OSX 10.6 and I’m addicted to the Chrome browser. I am officially on an X-Grade browser and live with the results. There are times I find myself scratching my head where the editor or page-viewing experience is less cool than it would be if I were on Firefox. But because we have a progressive enhancement methodology here too, I personally don’t feel the effect of missing content, but instead lack a few nice to have features of the A-Grade set. I’m not missing the show. I’m just prefer to sit a little to the side of front and center.
That said, we don’t work in a vacuum. We realize Facebook, Google, heck, even Microsoft have all dropped support for IE6 in one way or another. We welcome feedback from the community. What browsers do you think we should support? Do you agree with the Yahoo YUI standards?