05.10.08

How do you describe…

Posted in Life at 7:46 pm by Smokey

…the smell of honeysuckle?

In a sure sign that summer is about upon us, the honeysuckle is out all over the yard, and it smells heavenly. It even overpowers the smell of lawn-mowing, no easy task, I assure you.

As I was mowing the lawn, I couldn’t help but wonder, though: how do you describe the smell of honeysuckle? Were you to describe something to me and say it smelled like honeysuckle, I would comprehend your meaning, but I can’t think of any primitives or comparisons I’d use to describe the smell to someone unfamiliar with honeysuckle.

How do you describe that smell?

05.03.08

Fantastico no longer so fantastic (and other long-delayed WordPress upgrades)

Posted in Life, Software at 6:44 pm by Smokey

A few years ago, Fantastico was the must-have feature when choosing a web-hosting company. Fantastico offered one-click installation and upgrades of popular web software packages (e.g., blogs, fora, wikis), which made it trivial for the average user to join the “participatory” world of the so-called “Web 2.0” rage. Indeed, when comparing hosting providers (something I had been doing since about 2002 when .Mac became a subscription service), I made sure to settle on a “Fantastico-enabled” host.

Initially things were great; WordPress updates appeared in Fantastico within about a week of release (given that the Fantastico developers needed to QA any changes a WordPress upgrade might need in their software and that hosting providers should QA any Fantastico upgrade on their servers before deploying, six or eight days seemed both relatively fast and reasonable). As time went on, however, new versions of WordPress and their security upgrades started taking longer and longer to appear in Fantastico (the last WordPress upgrade I did with Fantastico, to 2.3.3, took almost 40 days to appear in Fantastico, and both WordPress 2.5 and now 2.5.1 have been released without Fantastico upgrades appearing yet), and exasperated users complained in hosting providers’ forums, and exasperated providers complained in the Fantastico forums. Fantastico was no longer so fantastic.

Seeing the writing on the wall, I had been looking for solutions that were elegant, efficient, and easy. WordPress recommended putting your WordPress install in a Subversion repository (not easy), and later the WordPress Automatic Update Plugin appeared (not efficient), but, frankly, I wanted something tested and supported, in case something happened (and if I was going to have to mess around with things, I’d rather just use patch like phpBB used to support; patch and I are friends). Not too long ago, my host announced support for SimpleScripts, which promised more up-to-date releases and updates. The only drawback was I’d have to do some sort of “migration” to get افكار و احلام into the SimpleScripts system, either migrate the installation itself or migrate the data. Yay, more deferred maintenance.

Finally, this weekend, I set aside some time to perform all of these delayed changes. I had been reading the threads about Fantastico→SimpleScripts WordPress migration in the BlueHost forum (as well as lots of other documentation) for the past few weeks, so I knew I needed to set aside a couple of hours in case anything went wrong. The steps were simple enough; they just required some quiet and time. ;)

I ended up mostly following these instructions (phpMyAdmin database backup instructions I followed are here) to get my existing WordPress 2.3.3 install into SimpleScripts, though I changed steps 5 and 6, which eliminated steps 7-10:

  • Use Coda (Have I mentioned how much I love Coda? No? OK, I will soon, then.) to copy afkar/ to afkar_copy/. This took more time than just renaming the existing directory, but it also meant that I didn’t have to re-upload themes, plug-ins, and other stuff in wp-content when I was done, but I still had a pristine copy to revert to in case of problems.
  • Instead of having SimpleScripts create a new database, I had it update the existing database (I had several backups, from cPanel, WordPress itself, and the SQL backup from phpMyAdmin) using the information from my wp-config.php file. This is more “dangerous” and probably more trouble if something were to go wrong, but fewer steps if things went well (which they did for me).

Of course, I also had to fix the DB_CHARSET in wp-config.php again after the migration. :P

I then made another series of backups (though SimpleScripts will also create and restore backups when/after upgrading), disabled my installed plug-ins, and upgraded from 2.3.3 to 2.5.1. “Shiny,” as they say. I backed up again for good measure and then upgraded all of the WordPress plug-ins I had installed (a couple didn’t show updates in the WordPress UI, but I visited their sites and found there were updates available anyway).

Having now completed almost all deferred maintenance, and without any problems, I decided it was high time to fix that pesky DB_CHARSET issue once and for all. After all, nearly a year had passed since WordPress 2.2, and there were finally WordPress “instructions” on how to fix their poor database encoding choice/upgrade bug—except the instructions were just a general overview, suitable for folks familiar with databases, but not for average users. Fortunately, a user had written a plug-in to do the job for you. I had been reading about it for a while, it had been updated a couple of times, response had generally been positive (I had seen a couple of comments indicating it hadn’t worked at all, but also this recent one indicating success even with 2.5), and I had fresh database backups and some time left! ;)

The plug-in dutifully warns that it’s only been tested against WordPress 2.2, but after I acknowledged that I was taking my database’s life into my own hands, it offered to proceed anyway. After the converter finished its work, the only thing I had to do was set the DB_CHARSET back to utf8 in wp-config.php; I hope this is the last time I will ever have to change that variable!

The end result of an hour or so of “work” is a fully up-to-date WordPress installation, a sane database, no more deferred maintenance sitting around, and, hopefully, quick upgrades to newer versions of WordPress in the future. SimpleScripts seems simple, efficient, elegant, and it even addresses my other complaint about Fantastico), so I’m hopeful it will remain simple for much longer than Fantastico remained fantastic. Thanks, as always, to the great folks on the internet whose commentary and instructions facilitated my afternoon of upgrades.

04.16.08

Feeling Old

Posted in History, Life at 3:43 am by Smokey

I’m feeling old tonight. I read (via John Gruber) that Stan Flack, co-founder of MacCentral (and later MacMinute), had died.

As I read the posts from his former co-workers and friends in the Mac community, I began to wonder…had it really been nearly 15 years since I’d started following the Mac web? I remember when MacCentral switched from publishing every-other-day to daily, I remember how MacCentral would always commemorate Remembrance Day (Stan was Canadian; it’s Armistice Day or Veterans Day to the rest of us), and I remember the tiny little icons that MacCentral used in the early days to help differentiate the story type.

In fact, it’s those little icons (part of a bygone era on the web, and perhaps happily so) that are the reason I’m writing this at all. Shortly after a redesign in which they disappeared, I sent a little note to MacCentral’s feedback address politely lamenting their demise. Much to my surprise, I later received a response from none other than Stan Flack, Publisher of MacCentral, himself. The email is lost to the depths of time, but I recall him thanking me for the feedback, explaining why the icons went away, adding that he missed them a bit, too, and he’d look to see if there were other ways to use them (or something to that effect). The top guy responding to inconsequential feedback himself. I can’t claim to have known him, but from reading what others have written, that was the kind of person Stan Flack was.

As for those little icons, maybe it’s just my mind, but I’ve always thought that MacCentral’s post-redesign site logo and, later, its site icon () were reminiscent of those little globe-like icons that made reading only the stories I was interested in so easy. Those days seem so long ago and far away now….

And so, feeling older and with a sadness over the untimely passing of one the Mac web’s pioneers and enduring figures, I offer my happy memories of one of the greatest Mac news sites during the golden age of the Mac web, and of the man behind it, and I offer my condolences to the family and friends of Stan Flack.

Posts from some of Stan Flack’s friends and former co-workers:

04.15.08

Counting commands

Posted in Camino, Life at 2:06 pm by Smokey

Just because I need a break right now and sometimes it’s fun to play along with Planet Mozilla: what does a Camino QA lead/website peer/tester/sometimes-hacker’s command-line history look like?

[Qalaat-Samaan:dev/trunk/mozilla] smokey% uname -a
Darwin Qalaat-Samaan.local 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386
[Qalaat-Samaan:dev/trunk/mozilla] smokey% history | awk ‘{a[$3]++ } END{for(i in a){print a[i] ” ” i}}’ | sort -rn | head
24 make
11 cvs
10 cd
8 open
6 history
5 edit
4 patch
3 diffscrape
2 touch
1 svn
1 ls
1 cp

Notes:

  1. This is the sum for my six current active Terminal tabs from the tail end of One License to Rule Them All (Phase 2) on (I had to quit Terminal once I had the fix mostly complete because of some sort of corrupted environment setting). For the morbidly curious, there are another 11 open tabs for other branches and trees I haven’t built since restarting Terminal.
  2. If there were some way to track Coda saves and MediaWiki edits…that would tell the tale!
  3. Pretty much every launch of Camino to test something goes through Troubleshoot Camino these days, so all of those would-have-been open path/to/one/or/another/Camino.app commands are also missing.
  4. Thanks to bz for tcsh variant; otherwise I wouldn’t have been able to play along and take this needed break. :)

04.11.08

One License to Rule Them All (Phase 2)

Posted in Camino, Life at 1:40 am by Smokey

Over a year ago, I filed bug 368091 to make it possible for Toolkit’s copy of license.html (about:license) to serve as a licence file appropriate for all mozilla.org projects, not just the then-Corporation Fire/Thunder pair. (That bug was itself the result of a September 2006 bug to fix the XPFE copy of license.html to stop telling Camino and SeaMonkey users their official binaries were released under the Corporation EULA, which in turn was the result of a June 2006 bug to clarify the licensing references for Camino.)

For a long time bug 368091 sat unloved, with the neglect punctuated by brief flurries of activity which generally ended with exasperation and stalemate over seemingly mutually incompatible requirements. In the meantime the two copies of license.html grew to three, and every change to about:license had to be made either three or six times across mildly-forked copies of the file. This was no fun for anyone involved, including branch drivers approving changes for licensing compliance. Finally, after Stefan Hermes filed a bug last month about bad redirects on mozilla.org (and indirectly about bad URLs in SeaMonkey following its switch to Toolkit), I decided to post an interim patch for 368091 just to get the discussion moving again. Several weekends (and two additional patches for 368091 and one for Thunderbird), we’re down to only two copies of license.html on the trunk, and the Toolkit copy is now suitable for all mozilla.org applications. Phase 2 is complete!

For the curious, toolkit/content/license.html is now pre-processed before being packed into toolkit.jar, which ensures the copy of the license in toolkit.jar is devoid of application- or organization-specific EULA blocks. Firefox now takes toolkit/content/license.html, pre-processes it to include the Mozilla Corporation EULA block, stuffs that file in browser.jar, and sets up a chrome override so that about:license’s chrome URL (chrome://global/content/license.html) is overridden with the chrome URL for the Firefox-specific version. Thunderbird currently strips out the “about:license” fragments of all of the anchors in toolkit/content/license.html and ships a stand-alone file instead of shipping a stand-alone forked copy of license.html; after bug 428144, Thunderbird will also post-process in its EULA block. If you’re building a browser-type application, you can use the Firefox model to build your own license file; if you’re building a non-browser application, the Thunderbird model (most of Phil Ringnalda’s original “ship a stand-alone file” work in bug 339117 plus my patches from bug 427316 and bug 428144) should work well for you.

When I started filing these bugs back in June of 2006, I never intended that “one license to rule them all” would turn into what appears to be an obsession (at that point, I certainly didn’t expect I would fix any of the bugs along the way, let alone most of them). For over a year bug 368091 has been my #2 tab—perhaps that should have clued me in to the borderline obsession—and I’m delighted that I can finally close that tab. We’re not quite done with the quest to drive the number of license files on the trunk to one—XPFE (and thus Camino) still has a copy, but its days are numbered once I’m done with Camino 1.6 release work—and there are a couple of other follow-ups to finish, but we’ve completed the hard part of the trek.

This has been an interesting journey for me, and I extend thanks to everyone who helped out along the way—Gerv Markham and Frank Hecker at the Foundation, Robert Kaiser, Chris Thomas, and Stefan Hermes from SeaMonkey, Phil Ringnalda from Thunderbird (who, among other things, kept reminding us that any solution had to work for non-browser apps), Reed Loden on the www.mozilla.org side of things, Benjamin Smedberg for finally driving me to the correct solution, code review, and the SunOS tinderboxen bustage fix, and Samuel Sidler for getting things rolling (perhaps I should be cursing him instead? ;) ).

Stay tuned for Phase 3, coming in a few weeks, and then our long international nightmare will be over. :)

03.25.08

Camino 1.6 Beta 3 now available

Posted in Camino, Life at 9:21 pm by Smokey

This afternoon, we released Camino 1.6 Beta 3. If you’re using Camino 1.6 Alpha 1 or newer, please let software update notify you of the new release or or choose Check for Updates… from the Camino menu. If you’re not using Camino (why not? ;) ), you can visit our preview site for more information. The automatic updates are now using Stuart’s new script, which allows us greater flexibility and which will facilitate a completely localized update experience for users of Camino 1.6 Multilingual.

There’s not a “by the numbers” this time around, but it feels like the release went pretty smoothly. So far (knock on wood). ;) Sam was pretty busy all day with today’s Firefox 2.0.0.13 release, so most of the final “releasing” work was in my lap again. This is the third release I’ve pushed live (I think), so the work is starting to feel like a routine (Sam’s Release Checklist and the incremental improvements we’ve made to our website code and the process really help). It only took me about twenty minutes to make all the changes and another to five fix the various typos. ;-) Other than the bizarre issue where the Camino Blog post isn’t showing up on either Camino Planet or Planet Mozilla, it looks like the final releasing work went off without a hitch.

Since the period between Camino 1.6 Beta 2 and Beta 3 was a little extended, I had forgotten some of the great features that are new to anyone using Camino 1.6 Beta 2. Here are some of the highlights:

  • Right after Beta 2, we landed Bryan Atwood’s patch that allows Camino to store and access login information for multiple accounts at the same site. That means Camino’s Keychain implementation, which predated the modern Keychain APIs, finally is all grown up. Thanks again to Bryan for all of his hard work on this feature.
  • We now support passing feeds to certain web-based feed readers. Though I wrote about this feature in February, it wasn’t until Stuart’s patch that landed Monday that the feed handlers were automatically activated for everyone to use.
  • There were dozens of user interface improvements and a couple of big web compatibility fixes, but the change you’ll notice most—or perhaps not notice at all, which is a bit by design—are the new icons for a number of our main toolbar items. They feature subtle polish to make them fit in much better on Mac OS X 10.5 while not looking completely out-of-place on 10.3 or 10.4 and maintaining the distinctive Camino look we all love. It wasn’t an easy task, but I think the new icons succeeded. As an added bonus, many of the icons that did not previously have specially tuned 24×24 pixel versions now do, so they look even sharper at small sizes.

As always, thanks to Mark Mentovai and Stuart Morgan for doing most of the dirty work related to today’s release, and I hope everyone enjoys Camino 1.6 Beta 3!

Edit: It turns out that the Planet problem, like every other problem I noticed this afternoon, was due to my inability to change all the required numbers correctly after copying and pasting. :-P

03.02.08

Adieu, Little Gardens

Posted in Life at 11:02 pm by Smokey

Today, after over 30 years as one of Gwinnett’s premiere fine-dining restaurants, Little Gardens closed its doors as a restaurant. For as long as I can remember, trips down US 29 from Lawrenceville to Lilburn were marked by the unassuming Little Gardens sign poking out from the forest (and later, as development encroached, by sights of the lawn’s magnolias and the columned mansion itself).

For all those years of passing by, however, it was not until “relatively” recently that I had ever dined there. I first dined at the restaurant the night of my senior prom, and the last was for my grandparents’ 65 wedding anniversary last April. In between those days, I experienced this fading tradition for retirement celebrations, birthdays, anniversaries, and other special occasions. Like many from this area, Little Gardens has written itself on my life….

So as an era draws to a close, with a tinge of sadness I say thanks for the memories of a lost time, and adieu….

12.31.07

Camino 2007 in Review

Posted in Camino, Life at 11:11 pm by Smokey

Wow, how time flies when you’re building web browsers! ;) It’s time again for my annual look back at the Camino Project’s progress during the year.

While we didn’t meet our goals of getting Camino 1.5 (né 1.1) and 1.6 (né 1.2) out in early and mid-2007, respectively, we still had a good year with lots of accomplishments.

  1. First and foremost, we released Camino 1.5 in early June. After over a year of work, our “quick follow-up to 1.0” became a significant new upgrade instead, fixing a large number of our bugs that had very high vote counts in Bugzilla. We’ve also released four stability-and-security updates to 1.5 since June. The Multilingual version of Camino 1.5.x currently ships with 15 languages.
    • In concert with the 1.5 release, we debuted a refreshed version of caminobrowser.org, made possible thanks to hard work from Samuel Sidler and designer extraordinaire Jon Hicks.
    • We also continued to support our users on Mac OS X 10.2 with Camino 1.0 security updates until August, just after mozilla.org discontinued support for the version of Gecko used in Camino 1.0.x.
    • Earlier this month, we released the first alpha of Camino 1.6, showing everyone (or those who haven’t been using nightly builds) what we’ve been working on since June.
  2. We held the first face-to-face meet-up of Camino team members, at which we articulated the Project’s mission statement and finalized development plans for Camino 1.6. This event, which followed Apple’s annual WWDC conference, was made possible in part thanks to the Mozilla Corporation.
  3. For the second year in a row, we were awarded a Google Summer of Code slot. Jeff Dlouhy worked on “tabsposé,” a sort of Exposé for tabs. Jeff’s summer work is available in trunk builds of Camino.
  4. We also were able to co-sponsor (with the Mozilla Foundation) a second summer project, work from Peter Jaros to overhaul and modernize our AppleScript support. While we can’t top Safari or OmniWeb yet, we do have some nifty features like custom toolbar items written in AppleScript (see PimpMyCamino for some to try out!); all of Peter’s work is available in the aforementioned Camino 1.6 Alpha 1.
  5. As is often the case in volunteer organizations, people come and go. While some old friends have had to cut back their contributions due to graduation or new jobs, we’ve also welcomed new faces to the team.
    • In addition to Jeff and Peter, Bryan Atwood arrived this year, contributing patches for Flashblock support in Camino 1.5 as well as an extensive patch under review that will bring support for multiple accounts per website to our Keychain integration.
    • As the year came to a close, Swedish localizer Markus Magnuson started submitting patches, too; we look forward to more great work in the future!
    • The Norwegian localization of Camino, which disappeared in Camino 1.0, returned for Camino 1.5; there are also localizers working on reviving the Chinese translation and starting a Hungarian translation. (If Camino isn’t, or is no longer, available in your language, contact caminol10n and see how you can help.)
  6. Along those same lines, our Teams Coordinator Samuel Sidler started working at Mozilla Corporation in the QA Department in March. This meant that Sam was working on Mozilla-related stuff 24/7 ;-) for most of the year, which in turn meant more bugs got fixed—in shared Gecko components, in Firefox, and also in Camino—and we had a better feel for release schedules and other changes. Even though he wasn’t working on Camino directly at the day job, his work helped us out.
  7. Much to the relief of Stuart Morgan, Ian Leue, and Mark Mentovai, I obtained cvs access in October. I can now check in my own (slowly rising number of) patches, as well as those patches we take for security and stability updates, instead of having to take our other developers off what they’re working on to land things for me. ;-)
  8. Like developers, tinderboxen come and go, too:
    • We said good-bye to our old friend pawn, which had served Camino and Mozilla well for seven years, compiling the latest code day-in and day-out.
    • Late in the year (November?), we welcomed the creatively-named cb-miniosx01 to our collection of tinderboxen. cb-miniosx01, a Mac mini, is the first Mac OS X 10.5 tinderbox in the Mozilla world and will catch any build problems on 10.5.
  9. Finally, thanks to an initiative by the Mozilla Foundation, the Camino Project is now able to accept monetary donations. If you can’t code to save your life and don’t have the time (or the stomach) for dealing with bug reports, you can contribute to the Project financially. No, we’re not going to use the money to buy pinkerton a Porsche. We’ll work with the Foundation to identify and fund specific projects, like Peter’s AppleScript work over the summer, where a little bit of money can make a noticeable difference in Camino. Thanks to the Foundation for starting this program and for matching 2007 donations 2-for-1.

Whew! I think that just about covers the major events of this past year. 2008 promises to be another good year, with Camino 1.6 expected early in the year with better tabbed browsing and software update, followed by a switch to what’s now the trunk, Gecko 1.9, for Camino 2.0. Gecko 1.9 will fix a large number of long-standing Mac-specific bugs in page rendering, form controls, international text layout, improve the situation with plug-ins, and include all sorts of other nifty changes, and we’ll wrap an even better Camino around it. For the nostalgic (or balding ;) ) types out there, 2008 is also the 10th anniversary of Netscape’s release of the browser source code that got this whole thing started; mozilla.org’s going to party like it’s 1998.

Thanks to everyone in the Camino community—our developers, our testers, our localizers, users, and friends—for a great 2007. Happy New Year and welcome to 2008!

12.30.07

Rain!

Posted in Life at 10:29 pm by Smokey

It’s been raining more-or-less daily for the past week or so. While it’s not enough to put a dent in our drought, it may prevent this year from being the driest since record-keeping began.

I’m not fond of dark, wet winters, but I don’t mind this rain….

12.01.07

What we’re up to

Posted in Camino, Life at 1:16 am by Smokey

One of the things that we keep trying to do as a project (and not succeeding very well, it seems) is to be more proactive in letting people know what we’re working on for Camino. From time to time, people (such as this commenter) wonder if anyone is even working on Camino any more. This confusion is definitely a bad thing, and it’s one of the things I hoped to help address when I started writing here (unfortunately, writing is hard :( ).

First off, I’d like to assure anyone who’s wondering, yes, we are hard at work on Camino (and I’m not sure how the gentleman at TUAW has missed Camino 1.1a2, Camino 1.1b, Camino 1.0.4, Camino 1.5, Camino 1.0.5, Camino 1.5.1, Camino 1.0.6, Camino 1.5.2, and Camino 1.5.3, all released in the past year).

As an all-volunteer team, though, we don’t have the same time we can devote to Camino as the full-time (development, build, quality assurance) teams of other Mac browsers. We have day jobs or are students, so Camino is a free-time labor of love. Most of us, I think, prefer to spend our limited Camino time triaging or fixing bugs rather than writing about Camino, so while we’re making progress, people who aren’t using nightly builds or visiting the forum on a regular basis often don’t know what we’re up to between releases.

Once again I’ll try to address our “what are the Camino developers doing” “problem” by making a concerted effort to provide semi-regular updates on Camino development.

Hereafter a quick summary of recent activities:

  • While Mozilla Corp may build releases and run quality assurance tests on them during the holidays, we’re a little less insane. However, for the last two weeks, we have been working on Camino 1.5.4, coming next week. I’ve been landing patches, Stuart Morgan backported a few patches, and Mark Mentovai spun the release candidate build.
  • Jeff Dlouhy has been working on tab dragging and has a new demo of dragging with some animation. Jeff’s also been doing some graphics work for us while our regular designers are snowed under with paying work.
  • Sean Murphy has been working for some time on making adding and editing search engines for the toolbar search field more Mac-like than this, and in the past week he posted new patches for editing engines and for supporting the OpenSearch format for automatically adding new search engines.
  • Bryan Atwood, who brought us Flashblock in Camino 1.5, has been hard at work at making Camino support multiple accounts per site when storing passwords in the Keychain. The feature seems on-track to make Camino 1.6.
  • Stuart has been busy; in addition to his work on 1.5.4, he has been fighting bugs rendering trunk nightlies unusable and reviewing patches for new features. He has also been hard at work implementing software update for Camino and fixing bugs in the update framework we’re using.
  • In addition to my work on 1.5.4 and general bug triage, I’ve been spending some time working on implementing small applications to enable users of web-based feed readers to use Camino’s feed UI just like users of desktop readers currently can. In mostly-Camino-related activity, I’ve also been working on an almost-ready update to Troubleshoot Camino that fixes a few bugs; more on that soon.
  • Some of you might have noticed that Apple released a major new OS version about a month ago, so Stuart, Jeff, Mark, Ian Leue, and Samuel Sidler have been tag-teaming changes related to Mac OS X 10.5. You’ll notice the new status bar in 1.5.4, and hopefully you’ll notice some annoying 10.5-related bugs have disappeared. We’re aware the tabs and the bookmark bar still look a little out-of-place on 10.5, and we are working on those, but there are a number of aesthetic and practical considerations we have to balance, so we’re not rushing those changes.
  • Finally, you may have noticed that we’re now accepting donations. Sam had also been working with the Mozilla Foundation coordinating our end of this project, and of course setting up the new page on our website.

Truthfully, we’ve been very busy. :) I can’t promise all the new features mentioned above will appear in Camino 1.6, but most of them are on-track to do so. We’re also getting ready to release Camino 1.6a1; it won’t contain any of the features mentioned above, either (except software update, but you won’t notice that until our next milestone release—alpha 2 or beta—is ready), but there are almost six months of changes, including the scrolling tab bar, waiting for you to explore!

That’s it for now, but I do hope to turn this into a semi-regular feature so that it will be easier for everyone to see all the work we are doing on Camino. ;)

« Previous entries