Donations? Logos? Leprechauns?

Time for a few quick updates.

We have received a couple requests to put up a donation button. While we really like the idea of making a little bit of cash (really, who doesn't), Crossman and I have decided to hold off on any donations at least until the release of 0.5. We feel that we need to get a release out there before this really becomes a legitimate project.

Thankfully, Shift has received a decent amount of attention lately. Thanks for the kind words in the comments and on the interweb tubes. To those who offered to help, thanks a million. To those who didn't, and can, you really should. We are looking to keep the core of the project small at the moment, but we need contributors to UI, logo/brand development, testers, and brainstormers. However, if you are a true cocoa ninja, there is definitely a place for you here. MySQL experts (and after 0.5, other databases) are totally welcome as well.

We have some new ideas and hopefully some new mockups coming down the line. We also will be drafting a requirements list on the trac wiki here in the coming weeks to help guide development through 1.0. Please post any feature requests so we can get them in there.

Let's be honest, most database apps suck. We have the power to make a better mousetrap, so we're going to do it.

Leprechauns? No comment.

12:04 AM | 2 Comments | Tags: ,

Comments

  1. I couldn't figure out how to make an edit on the Trak wiki (heh) so a feature request here.

    I'd be great if Shift could optionally keep a log of any schema changes (like CREATEs, ALTER TABLEs etc) somewhere that could be viewed and exported to a text file for replaying against another server.

    The idea being I could make a load of changes on a local copy of a database, then take the log file and execute it against other copies in order to bring them up to date with my changes.

    Ultimately it'd be really nice to have a schema synchronisation tool like Navicat has, but that's obviously a large chunk of work. I figure just logging out the SQL statements that are already being generated would be much simpler and be nearly as useful.

    Drew McLellan on

  2. Crossman actually just brought this up the other day. Looks like it is a requested feature by several people at this point, so we will definitely work to get it in at some point. Thanks for the suggestion.

    Nate Todd on