I wouldn't worry that anything is going to up and disappear in the next
couple of days, even if it does stay under Owen's account. He may not have
been on IRC, but he's still been accessible in other ways when needed, and
provided he can find a spare second or two.

Also remember that "donations" are basically to Owen, who would then be
responsible for paying taxes on them. Unless we could find some existing
tax-free entity that works with open source projects and which we were
comfortable basically "owning" all our assets, there's really no way around
*someone* eventually footing that (admittedly very minor now) bill in one
way or another.


On Fri, Aug 9, 2013 at 7:03 AM, Sean T. Evans <[email protected]> wrote:

> If I had to guess, I'd suspect he's traveling. It's nearing the end of the
> summer, so he may very well have taken his kids for one last adventure
> before school starts.
>
>
> On Thursday, August 8, 2013, Drew Heath wrote:
>
>> Thank you for elaborating. I'm willing to "buy" a few months of server
>> hosting. Owen's absence from IRC and this list is worrying though.
>>
>>
>> On Fri, Aug 9, 2013 at 12:08 PM, Chris Meller <[email protected]>wrote:
>>
>> Sorry, Drew. We already have a plan for where to move so I didn't think
>> you still wanted an answer.
>>
>> To answer your question, we at one point ran Trac, which is a
>> Python-based beast of a machine killer. Since it is gone we run a Habari
>> instance for the blog and one for the addons directory (which includes some
>> packaging and what not overhead). Other than that there are a handful of
>> cron jobs that run between hourly and daily and the horridly outdated
>> MediaWiki install (that is bound to get us hacked eventually) that no one
>> likes.
>>
>> In other words, pretty much nothing significant. A 512 droplet should be
>> more than enough after a bit of MySQL tuning. Though since Trac is gone, we
>> could probably fall back to SQLite for the Habari instances. Not sure what
>> else MediaWiki supports or if its even worth exploring.
>>
>> If any of us had a little more time on our hands, we could actually
>> switch to Postgres so we actively have a testbed for it. But after
>> migrating my site to it, I'd not recommend that path for the unadventurous
>> with no free time on their hands.
>>
>>
>> On Thursday, August 8, 2013, Drew Heath wrote:
>>
>> Imma ask again: https://www.digitalocean.com/pricing
>>
>> Can someone please tell me what sort of plan HP needs?
>>
>>
>> On Fri, Aug 9, 2013 at 7:31 AM, Chris Meller <[email protected]>wrote:
>>
>> Owen, the one who is still paying the bills.
>>
>>
>> On Thu, Aug 8, 2013 at 7:29 PM, Chris J. Davis <[email protected]>wrote:
>>
>> Yes please. And who is “we” in this context?
>>
>> On Aug 8, 2013, at 6:26 PM, Chris Meller <[email protected]> wrote:
>>
>> We are secretly ahead of you. There is a Digital Ocean box set up that
>> had an Nginx + PHP + MySQL install script run on it. I've not had time to
>> do more than poke it, unfortunately. If you shoot me an SSH public key, I
>> can get you added.
>>
>>
>> On Thu, Aug 8, 2013 at 7:20 PM, Drew Heath <[email protected]>wrote:
>>
>> Forgive my ignorance, what sort of server capability does Habari need?
>> That way I can help in the provider search.
>>
>> - Drew
>>
>>
>> On Fri, Aug 9, 2013 at 7:05 AM, Chris J. Davis <[email protected]>wrote:
>>
>> We need to start a  discussion about moving these servers to a new host
>> (I would really like to move them to Digital Ocean (
>> https://www.digitalocean.com) and we need to come up with some mechanism
>> for paying for our infrastructure that doesn’t involve “Owen pays for it.”
>>
>> I am happy to contribute cash to our hosting needs, and would love to
>> help with maintaining servers. I already host a bit at Digital Ocean and
>> really love the service and you can’t beat the speed and cost.
>>
>> So, I would like to propose we get this decision made, and a plan of
>> action put in place by the end of August.
>>
>> Thoughts?
>>
>> --
>> --
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/habari-dev
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "habari-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>  --
> --
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/habari-dev
> ---
> You received this message because you are subscribed to the Google Groups
> "habari-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
--- 
You received this message because you are subscribed to the Google Groups 
"habari-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to