I’ve installed a ‘trouble ticket’ system to manage support issues for FrameAlbum. \u00a0Some (Ok, most<\/em>) of you who have emailed me in the past (at framealbum@gmail.com) may have received a reply stating that a ‘…human will reply shortly.’. \u00a0I’m in the process of sorting through those, and replying to folks to whom I’ve been woefully remiss.<\/p>\n I’ve also installed a ‘bug tracker’. \u00a0I’ll use this to record bugs that are discovered by you,\u00a0intrepid\u00a0users, and to manage the ‘feature roadmap’ for future versions of FrameAlbum.<\/p>\n Both of these items are ‘behind the curtain’ but are important for the\u00a0maintenance\u00a0of my sanity as well as the experience of folks using the service.<\/p>\n Lastly, but of greater significance to many folks here, I’ve finally managed to cobble together a GIT repository of the FrameAlbum source code. \u00a0I’m using the new bitbucket.org<\/a> service from\u00a0Atlassian<\/a> (makers of Jira, Confluence and many other tools for developers). \u00a0I’m going to open this up only to a few people at first so that I can insure that I’ve left nothing ‘secret’ in the GIT version of the code. \u00a0If you are interested in having a look at the sausage machine that is FrameAlbum, hop on over to bitbucket.org and register yerself. \u00a0Ping me when you’re registered.<\/p>\n Ciao for now!<\/p>\n","protected":false},"excerpt":{"rendered":" I’ve been a busy little code monkey… I’ve installed a ‘trouble ticket’ system to manage support issues for FrameAlbum. \u00a0Some (Ok, most) of you who have emailed me in the past (at framealbum@gmail.com) may have received a reply stating that a ‘…human will reply shortly.’. \u00a0I’m in the process of sorting through those, and replying … Continue reading Your call is very important to us…<\/span> Source code ready for ‘early review’<\/h4>\n