Thanks Brenden!<br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 11:36 PM, Brenden Kuerbis <span dir="ltr"><<a href="mailto:bkuerbis@internetgovernance.org" target="_blank">bkuerbis@internetgovernance.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br><br>I've taken the liberty of revising the VPS request based on your comments and discussion on list(s). Please take a quick peek, but I believe its ready to ship off to the EC for approval. Lets get moving on this so we can setup the VPS, an instance of WordPress and migrate the email lists.<br>
<br>-- B<br><br><div class="gmail_quote"><div><div class="h5">On Thu, Feb 21, 2013 at 2:46 AM, Wilson Abigaba <span dir="ltr"><<a href="mailto:wilson@isoc.ug" target="_blank">wilson@isoc.ug</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Team,<br>
<br>
Below is the feedback I have gotten from finance team so far. Points<br>
are randomly listed.<br>
- We need to create a platform that is not technically demanding and<br>
time consuming so that it can be easily maintained beyond the current<br>
team.<br>
- We need to add more detail about specific requirements and costs<br>
- I think we need to justify why we should drop ning and adopt a VPS<br>
- Proposal should be sent to (and approved by) the EC<br>
- We might also need to formally consider (at least 3, as per the<br>
standard procurement procedures) other vendors so that we justify why<br>
Gandi was chosen.<br>
<br>
I am stepping out for a few hours but here is our current proposal. I<br>
think we can edit it concurrently and send it to EC by end of today.<br>
<br>
<a href="https://docs.google.com/document/d/1NxYgmqlhoBX9BQJOIcZ6EVsbctzn3WZHMGDty63xLxs/edit" target="_blank">https://docs.google.com/document/d/1NxYgmqlhoBX9BQJOIcZ6EVsbctzn3WZHMGDty63xLxs/edit</a><br>
<br>
Reading Tapani's response below, I personally wouldn't recommend<br>
anything significantly below the suggested $400 as I think it's<br>
already at 'minimum requirement' considering what we want to do :)<br>
<br>
Kind Regards,<br>
Wilson<br>
<div><div><br>
On Thu, Feb 21, 2013 at 7:48 AM, Tapani Tarvainen<br>
<<a href="mailto:ncuc@tapani.tarvainen.info" target="_blank">ncuc@tapani.tarvainen.info</a>> wrote:<br>
> On Wed, Feb 20, 2013 at 11:01:06PM +0100, William Drake (<a href="mailto:william.drake@uzh.ch" target="_blank">william.drake@uzh.ch</a>) wrote:<br>
><br>
>> On Feb 20, 2013, at 22:22, Milton L Mueller <<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>> wrote:<br>
><br>
>> > One must be careful of ongoing expenditures, especially if they<br>
>> > lock us in to anything that would be costly to get out of, but<br>
>> > $400/year is certainly not out of reach.<br>
><br>
>> > It does seem a bit high (without knowing the requirements) as the<br>
>> > current Ning site is $235/year but if VPS does something that<br>
>> > normal hosting doesn't, I am sure you can convince EC to approve<br>
>> > it.<br>
><br>
>> Wilson and Tapani, were there other vendors/options? Agree with MM a<br>
>> little more detail/background wouldn't I hurt for an ongoing<br>
>> expenditure, even if it's less for a decade than we spend at a time<br>
>> on other stuff.<br>
><br>
> We did not do a formal comparison of vendors, it was felt<br>
> unnecessary due to the relatively small amount involved and<br>
> the fact that we already are using Gandi for DNS registration<br>
> so using it for hosting as well avoids extra work in account<br>
> management. But we did discuss the features we wanted<br>
> (listed in Wilson's document) and we're well enough aware of<br>
> the market situation to know Gandi is cheap for what they offer.<br>
><br>
> We could cut down on the $400 figure, however, by settling on a less<br>
> powerful VPS. The smallest available VPS at Gandi would be about<br>
> $170/year or $16/month (or $0.53/day!), and if you want to keep<br>
> tighter rein on the expenditure we could start with that.<br>
> It would probably to run out of power pretty soon though if we get<br>
> around to doing all we've been planning to, but it would be enough to<br>
> get us started and buying more oomph in small chunks only as needed<br>
> is of course possible, even down to daily basis if desired.<br>
> The downside there would be the extra time required to manage it<br>
> and to process and approve the bills piecemeal.<br>
> So I guess it boils down to how much people's time is worth, how<br>
> small amounts merit a separate decision in the EC, how much time<br>
> the sysadmins need to spend to monitor the machine and adjust<br>
> it as needed, &c.<br>
><br>
> One possibly money-saving alternative would be for the EC to authorize<br>
> expenditure of up to a certain amount, like that $400, but<br>
> recommending that it be used cautiously, buying more power bit by bit<br>
> as the need arises. That way it would only use up e-team's and<br>
> Milton's time rather than EC's and could be done faster.<br>
> That's actually a good reason for having some pre-approved<br>
> budget not spent at once, we might have an unexpected peak<br>
> in bandwitdh or something we'd like to react to fast<br>
> (maybe some outreach effort explodes our popularity and<br>
> we get a billion people hitting our site at once...)<br>
><br>
> But, since we're just starting to work out new processes here,<br>
> I would be OK with going slowly: as I said that $170 would be<br>
> enough to get us started, just don't be surprised when the<br>
> e-team asks for more later.<br>
><br>
> --<br>
> Tapani Tarvainen<br>
> _______________________________________________<br>
> Finance mailing list<br>
> <a href="mailto:Finance@lists.ncuc.org" target="_blank">Finance@lists.ncuc.org</a><br>
> <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/finance" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/finance</a><br>
</div></div></div></div><div><div>_______________________________________________<br>
E-team mailing list<br>
<a href="mailto:E-team@lists.ncuc.org" target="_blank">E-team@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team</a><br>
<br>
</div></div></blockquote></div><br>
<br>_______________________________________________<br>
E-team mailing list<br>
<a href="mailto:E-team@lists.ncuc.org">E-team@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team</a><br>
<br></blockquote></div><br>