Reclaim Community Helps Scratch an Old Itch

Screenshot 2016-08-14 13.56.19

Been on a bit of a blog vacation over the last two weeks. Between traveling, hiking, entertaining and enjoying some mental downtime the bava was dormant. It has been a welcome break.* I still think in terms of blog posts, and when I go this long without posting I start to feel a bit like what I imagine a sidelined athlete must feel, just not nearly as svelte. I have a lot to blog about, including the novel I just finished by Richard Matheson, but that will be a bit longer affair. For now I want to quickly highlight the immediate dividends the resuscitated Reclaim Community site has paid.

A couple of weeks ago Tim decided to breath some life back into our languishing Community site. He started posting about specific topics and inviting others to contribute. Pretty soon thereafter others, like the great Kristen Eshleman, started jumping in with their own questions. It’s how this stuff works: you target open invites, seed conversation, and pray for rain. Tim also made a call for feature requests, and Tim Clarke from Muhlenberg University (one of Reclaim’s newest institutions!) requested we provide a more prevalent link to Installatron Applications. Tim Clarke had no idea that the Installatron icons in cPanel had been an ongoing issue for us, in fact Muhlenberg’s server has no issues with a broken Installatron icon that others had limped along with for almost a year.

Screenshot 2016-08-10 15.02.20
But, his request led to Tim Owens and I working through a possible fix for the broken Installatron icon on our shared hosting in public. This was one of the major bugs we had, and Adam Croom jumped onto the thread re-affirming as much. Installatron was a crucial element of making the cPanel interface user-friendly, and a broken icon that previously showed off WordPress, Omeka, Scalar, etc. was a major flaw. So, Tim did as Tim does, he figured out a way to create a custom section that highlights popular web applications  as well as link to all applications and an individual users applications (he even used Bryan Mathers’ record art.

5eb6bf151a42791c4bfdde4f671a0f56320edab3_1_690x417What was so cool about this was not only that it pushed us to solve for ourselves a major issue we had been hoping Installatron would fix, but it was accomplished as a result of a request and subsequent conversation within the Community site. For me, the value of the Community site is concrete now, and I was able to email a few folks soon after Tim added the fix to our shared hosting servers announcing the fix. It felt so good. It felt like we were truly responding to what people needed, and while we’re pretty good about that in general, doing it publicly amongst the community just makes the issues that much more pressing and relevant.


*Although, truth be told, I did post over on my other blog.

This entry was posted in reclaim and tagged , , . Bookmark the permalink.

4 Responses to Reclaim Community Helps Scratch an Old Itch

  1. Adam Croom says:

    I’ve really appreciated the interactions on the Community site and it’s only been a week. It’s nice to have a place where we can make suggestions without having to do so through the ticketing system. Something like this is critical to our community but never necessary mission critical so some respects I’ve failed here in getting that kind of suggestion to you guys.

    That’s really awesome to hear the back story about how Installatron didn’t fix this but it was Tim getting creative. That’s fantastic. I know he’s had a ticket in with CPanel/Installatron (not sure who) for some time and they’ve yet to follow up on it. Way to buck the system!

    • Reverend says:

      Yeah, we have been begging Installatron to look at this and getting zero response. That community thread did for us exactly what it did for you, gave us the impetus to say fuck this let’s fix it ourselves. We’re so fucking punk rock!

  2. Adam Croom says:

    Second comment… Let the public record show that my comment on the Community section was “I know this isn’t something likely to be fixed by Reclaim, but…”

    This was referring to knowing it was a plugin error and not that Reclaim COULDN’T fix it. 🙂 Tim strikes again and continues to beat the field!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.