01:14:13 <unknown_lamer> #startmeeting 01:14:13 <hcoop-meetbot> Meeting started Fri Jan 26 01:14:13 2018 UTC. The chair is unknown_lamer. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:14:13 <hcoop-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 01:14:16 <unknown_lamer> #topic roll call 01:14:26 <unknown_lamer> if you were here, please write #info $hcoop-username 01:14:28 <unknown_lamer> #info clinton 01:14:29 <jackhill> #info here jackhill 01:14:36 <keverets> #info here keverets 01:14:36 <eronel> #info eronel 01:14:37 <jackhill> oops 01:14:39 <jackhill> #info jackhill 01:14:44 <terpri> #info bpt 01:14:46 <keverets> #info keverets 01:15:04 <unknown_lamer> alright 01:15:06 <unknown_lamer> #topic agenda 01:15:15 <unknown_lamer> anyone want to add any agenda ideas? if not, we'll start 01:15:18 <unknown_lamer> *items 01:15:46 <jackhill> talk about long term direction if we have time at the end 01:15:57 <eronel> I would like to talk about that, too. 01:15:59 <jackhill> https://wiki.hcoop.net/IrcMeetings/20180126 is the agenda for easy access 01:16:24 <unknown_lamer> #info https://wiki.hcoop.net/IrcMeetings/20180126 01:16:32 <terpri> #info 990n tax form filed for 2017 01:16:40 <jackhill> terpri++ 01:16:58 <terpri> that's the only extra item from me :) 01:17:22 <unknown_lamer> I added long term direction to the agenda, good to go ? 01:17:32 <terpri> +1 01:18:01 <unknown_lamer> +1 01:18:26 <jackhill> +1 01:18:27 <eronel> +1 01:18:41 <keverets> +1 01:18:49 <unknown_lamer> alright 01:19:07 <unknown_lamer> wanted to quickly divert into the registered agent, will take just a sec 01:19:10 <unknown_lamer> #topic registered agent 01:19:20 <unknown_lamer> we never received an invoice for 2018 from incorp... 01:19:37 <unknown_lamer> I emailed them about it two days ago but haven't gotten a response, their EMS lists us in good standing so I'm not sure what's up 01:20:24 <unknown_lamer> going to mail them again monday if I haven't heard anything, but we miiiight need to worry about finding a new registered agent, hopefully not, I'll update over email if/when I hear from them 01:20:52 <unknown_lamer> that was about it 01:20:58 <unknown_lamer> #topic financial status 01:21:40 <jackhill> current balance is $140.71 01:22:24 <jackhill> we're not really getting enough in dues to cover our expenses. unknown_lamer keeps needing to bail us out. 01:22:50 <unknown_lamer> I can continue to do so for another couple of months, but then I'm gonna coast on that balance once we lower expenses for a while ;) 01:23:10 <unknown_lamer> obviously not ideal for the coop, and not ideal for me ... motivation to fix things 01:24:16 * smichel17[m] just remembered this was tonight and not tomorrow. Wrong thing in the calendar despite knowing the right thing -.- 01:24:34 <jackhill> yes, not idea :/ 01:24:46 <jackhill> I'm hopeful that there is light in the future. We're here to help 01:24:52 <unknown_lamer> so, what to do about it ... 01:25:23 <unknown_lamer> a -announce post is warranted (really months ago, but that's me procrastinating...) 01:25:28 <jackhill> I think the only thing to do on that timeframe is lower costs. Then the discussion is how to do that. 01:25:36 <jackhill> ah yes 01:25:40 <jackhill> +1 to announce post 01:26:01 <unknown_lamer> maybe see if some members are willing to pitch in a share or two extra, to give a small short term boost to cash flow 01:26:07 <terpri> do we know how much we're losing on a monthly basis? we should be getting over $450/month pledges 01:26:22 <terpri> (although that's not a sustainable source of funding) 01:26:40 <unknown_lamer> terpri: I doubled my pledges or something this month, so it looks like we have more now 01:26:49 <smichel17[m]> I'm interested in helping draft the email. Maybe we could fire up an etherpad to work collaboratively on that? 01:27:43 <terpri> +1 for the announcement 01:27:51 <unknown_lamer> terpri: the major issue is we were deficit spending for a long time, so balances vs what we have in the bank is off by a lot :-\ 01:28:07 <jackhill> so far in January we've received $123.60 from people not unknown_lamer 01:28:17 <smichel17[m]> Just checking if the IRC bridge is working: can you all see this? 01:28:31 <unknown_lamer> smichel17[m]: yep 01:29:07 <jackhill> in Dec it was $458 01:29:18 <jackhill> including my dues 01:29:34 * jackhill waves to smichel17[m], welcome 01:30:59 <unknown_lamer> so, for the email... we need to let the membership know we're basically broke, see if anyone wants to pitch in a few extra pledges, and put out a call for ideas to reduce expenses, at least 01:31:33 <unknown_lamer> (or, really, if anyone wants to price out other virtualized hosting options) 01:31:36 <eronel> I think it's bad to have such a drastically inflated balance value in the portal, because people won't understand how much we need money at all. 01:31:37 <jackhill> could we also adopt a proposed was to reduce expenses as a board? 01:31:40 <smichel17[m]> My account is negative and I'm going to restock it now. I've been putting it off because I'd like to give a little more than the minimum as I have been, but I need to figure out my finances in more detail first. I wanted to it all as one payment to minimize fees but I'm just gonna go ahead and do the minimum thing now. 01:32:37 <unknown_lamer> eronel: that is thanks to years of not entering bills :-\ started two treasurers ago 01:32:44 <unknown_lamer> we have all of the records from the bank though 01:33:17 <jackhill> pricing has already been done, no? http://wiki.hcoop.net/VirtualizedHosting2016 01:33:20 <eronel> How hard is it to just remove the info? 01:33:34 <unknown_lamer> just stop displaying the coop balance? 01:33:41 <unknown_lamer> just have to comment a line out in the mlt file 01:34:15 <eronel> It seems like that would be a good idea. 01:35:31 <jackhill> +1 01:36:05 <unknown_lamer> bylaws don't seem to forbid not presenting that information, it's a lie anyway right now 01:36:27 <terpri> i could help get the records in order if we want to fix the portal at some point 01:36:34 <smichel17[m]> Why not hard code the actual amount, for now? 01:36:43 <unknown_lamer> I'm ok with doing that, since given current time constraints me writing a cli tool to import transactions seems unlikely (and the code for dealing with that is ... no fun) 01:36:59 <terpri> in theory, the secretary is supposed to audit finances occasionally, although i think ntk was the last person to do so 01:37:12 <unknown_lamer> yeah, I think we had one audit total, ever 01:37:33 <unknown_lamer> and I don't think we can just do a one-off charge to reconcile 01:37:38 <smichel17[m]> "As of 2018-01-25, the balance is $140." 01:38:01 <jackhill> I think we should fix it (and make the bills workflow more conducive to keepting it updated), but at this jucture, there are more pressing things for anyone fixing it to spend their time on. 01:38:04 <smichel17[m]> And then we can change it back to the current way when someone's had the chance to enter the reciepts 01:39:13 <jackhill> I'm fine with that 01:39:18 <unknown_lamer> smichel17[m]: someone would have to keep it updated, ... probably me ;) 01:39:48 <eronel> It seems like it should be the Treasurer's responsibility. 01:40:07 <smichel17[m]> unknown_lamer: Or we can not worry about it, as long as it's within an order of magnitude of correct. 01:40:09 <unknown_lamer> jackhill: we can do the manual way if you're up for a tutorial on how to run mlt and publish the portal 01:40:41 <jackhill> yes, I can do it! And I would love to have a tutorial. That sounds much better than trying to figure it out on my own. 01:40:57 <unknown_lamer> ok, then: 01:41:03 <smichel17[m]> One reason I like the manual way is because if the page goes out of date, it gives some insight into how under"staffed" we are. 01:41:57 <unknown_lamer> we will temporarily remove the current coop balance from the database and replace it with a statically updated balance, second or amend? 01:42:10 <eronel> second 01:42:20 <unknown_lamer> #info vote: we will temporarily remove the current coop balance from the database and replace it with a statically updated balance 01:42:22 <unknown_lamer> #info +1 01:42:27 <jackhill> #info +1 01:42:28 <terpri> #info +1 01:42:32 <eronel> #info +1 01:42:42 <smichel17[m]> (should I be doing anything with the #'s or is that a board member only thing?) 01:42:48 <unknown_lamer> #agreed we will temporarily remove the current coop balance from the database and replace it with a statically updated balance 01:42:53 <unknown_lamer> smichel17[m]: only board members are voting right now 01:42:58 <smichel17[m]> d 01:43:05 <unknown_lamer> (but anyone may participate generally, of course) 01:43:36 <smichel17[m]> Is conversation not preceeded by #info logged? 01:43:47 <terpri> yeah, everything is logged during meetings 01:43:51 <unknown_lamer> smichel17[m]: everything is logged, but #info and other commands cause the line to be highlighted in the log 01:43:55 <terpri> it's not in the minutes though 01:43:55 <unknown_lamer> https://wiki.debian.org/MeetBot 01:44:24 <unknown_lamer> #action unknown_lamer will privmsg jackhill and coordinate a quick mlt tutorial and replacing the balance info on the portal page 01:46:47 <eronel> Still need an action for the announce post? 01:47:04 <unknown_lamer> does anyone want to volunteer to draft that? 01:47:28 <smichel17[m]> I can draft it given a chat about what it should say, first. 01:48:45 <terpri> proposal: smichel17[m] will draft an announcement about the current financial situation 01:48:50 <terpri> (with input from the board) 01:48:55 <jackhill> second 01:49:06 <unknown_lamer> #info vote: smichel17[m] will draft an announcement about the current financial situation (with input from the board) 01:49:11 <unknown_lamer> #info +1 01:49:14 <jackhill> #info +1 01:49:14 <terpri> #info +1 01:49:15 <eronel> #info +1 01:49:26 <keverets> #info +1 01:49:27 <unknown_lamer> #agreed smichel17[m] will draft an announcement about the current financial situation (with input from the board) 01:49:57 <smichel17[m]> #action smichel17[m] will draft an announcement about the current financial situation (with input from the board) 01:50:03 <unknown_lamer> does having a draft ready by monday/tuesday sound reasonable? 01:50:17 <unknown_lamer> I guess timelines matter for this... 01:50:53 <jackhill> Wednesday is the last day of Jan. 01:51:07 <smichel17[m]> Goal would be to do it immediatley after this meeting. 01:51:11 <unknown_lamer> I think it would be preferable to aim for the end of march as getting to cheaper hosting, end of feb seems overly optimistic and we have to account for time to notify/poll members (cooperative principles and all that) 01:51:21 <unknown_lamer> smichel17[m]: excellent 01:51:40 <unknown_lamer> so, draft asap, then review && try to get it out by wednesday? 01:51:49 <smichel17[m]> d 01:52:22 <unknown_lamer> earlier if it works out, no reason to delay arbitrarily 01:53:50 <smichel17[m]> What agenda item are we on right now? 01:54:08 <unknown_lamer> may as well figure out the email content quickly before moving on 01:54:19 <jackhill> smichel17[m]: "financial status" 01:54:35 <smichel17[m]> Let's do it after the meeting, as it may include several topics 01:54:57 <smichel17[m]> or at least after all the other agenda items 01:55:08 <unknown_lamer> works for me if it works for everyone else 01:55:18 <jackhill> I agree that we should wait as we might want to include information from those topics 01:56:32 <unknown_lamer> did anyone have anything else they wanted to discuss for financial stuff (aside from virtual hosting related topics, as that is the next item ;) ) 01:56:45 <unknown_lamer> otherwise, I move to move to the next agenda item 01:56:53 <jackhill> I do not 01:56:57 <eronel> no 01:57:26 <smichel17[m]> nor I 01:57:35 <terpri> me neither 01:57:39 <unknown_lamer> cool 01:57:46 <unknown_lamer> #topic transition to virtualized hardware 01:58:43 <unknown_lamer> so, it seems fiscal reality is that we have to stop doing hardware for the foreseeable future, thoughts? 01:58:59 <jackhill> I concur with that thinking. 01:59:30 <jackhill> Also, given how user-hostile current hardware is, I'm not sure if we lose anything by going virtual. 01:59:42 <smichel17[m]> +1. Unfortunate, but it is the reality as far as I can see. 02:00:03 <eronel> Why is it unfortunate? 02:00:33 <smichel17[m]> We lose some capacity to switch to more user-friendly hardware in the future. 02:00:56 <smichel17[m]> And some control over our stack 02:01:01 <jackhill> do we? Wouldn't we be able to migrate back? 02:01:12 <unknown_lamer> I don't see any reason we couldn't go back to hardware later 02:01:23 <terpri> i also think dedicated hardware would be preferable long-term 02:01:38 <smichel17[m]> Only because it's work. Maintaining the status quo is easier 02:01:48 <eronel> I don't understand why hardware is preferable at all. 02:02:24 <terpri> for example, we wouldn't be dependent on a vps host for dealing with meltdown/spectre, which some smaller hosts still haven't mitigated 02:02:38 <unknown_lamer> terpri: status quo is that we can't reboot fritz at all 02:03:07 <terpri> but i think moving to a vps setup is a good idea for the near future, given our membership levels 02:03:24 <jackhill> I think physical storage gives us more flexibility, but we don't currently have the scale. 02:04:02 <smichel17[m]> I think a discussion of whether we would prefer physical hardware long-term is out of scope for this agenda item. 02:04:07 <jackhill> I don't think migrating from our old hardware to new hardware meaningfully harder than virtual to physical, so don't think we're painting outselves into a corner. 02:04:17 <jackhill> good point 02:05:00 <unknown_lamer> if everyone thinks moving to a vps in the short term is at least not a disastrously bad decision I think we're good 02:05:09 <eronel> +1 02:05:16 <terpri> +1 02:05:19 <jackhill> +1 02:05:24 <keverets> +1 02:05:27 <smichel17[m]> +1 02:05:47 <unknown_lamer> now comes the fun: what sort of timeline are we looking at / does anyone have any comments... 02:06:53 <jackhill> I liked asap, but at least before the end of March 02:06:54 <smichel17[m]> If the decision were made right now and we didn't care about notifying members, how soon could we complete the migration? 02:07:25 <unknown_lamer> I was thinking a week or two after informing members to request any input before making a final decision on the provider, during which time I can begin preparing in the background 02:07:37 <unknown_lamer> a few packages need some dusting off and whatnot before we can actually start any migration 02:07:42 <keverets> are the values on http://wiki.hcoop.net/VirtualizedHosting2016 still valid? 02:08:07 <unknown_lamer> for linode, yes, assuming we can get block storage -- terpri mentioned attempting to use it in the NJ datacenter and it being at capacity 02:08:36 <smichel17[m]> unknown_lamer: how much time for the migration itself once we have decided on a provider? 02:08:38 <jackhill> I think they are all recent except auro.io, which I priced a while ago. Also, I probably got more block storage than we'll need. 02:09:20 <terpri> linode's price is still decent if we can't get block storage 02:09:28 <unknown_lamer> smichel17[m]: six weeks minimum (absolutely nothing at all goes wrong, in the entire world...), eight realistically 02:09:49 <jackhill> I volunteer to do work parties with unknown_lamer 02:11:53 <smichel17[m]> unknown_lamer: can you take on a task of writing out all the steps required, so we have a roadmap? 02:12:00 <jackhill> brb 02:12:24 <unknown_lamer> to start, how about I update the requirements to match what we really need right after the meeting, then jackhill can update the auro.in quote and I'll make the linode one more usable, anyone else can fill in other vps providers? 02:12:34 <unknown_lamer> smichel17[m]: in progress already 02:12:51 <smichel17[m]> Cool 02:12:58 <unknown_lamer> in my planner, need to copy to the wiki 02:13:32 <jackhill> back 02:13:46 <jackhill> sounds good to me 02:14:12 <unknown_lamer> #action unknown_lamer will update VirtualizedHosting2016 with actual current hardware needs tonight 02:14:31 <terpri> #info +1 02:14:43 <jackhill> #info +1 02:14:47 <keverets> #info +1 02:15:03 <eronel> +1 02:15:03 <jackhill> yes, that will be helpful for updating the auro.io quote 02:15:07 <eronel> #info +1 02:16:58 <unknown_lamer> for a general timeline: 1-2 weeks to get input from members before a vote? then we vote and secure hosting and kick off the admin part? 02:18:21 <smichel17[m]> If the admin part is going to take 8 weeks, then 1 week (end of Jan) is all we can afford if we want to be migrated by the end of March. 02:20:35 <smichel17[m]> And we should try to get a final draft done tonight or tomorrow. 02:21:12 <unknown_lamer> I won't be able to provide input on a final draft tonight (getting late already...) but if anyone else wants to that is fine, let's discuss that after... 02:21:37 <smichel17[m]> Yeah, we need to get through this meeting in a reasonable amount of time. 02:22:07 <smichel17[m]> What, if any, other actions do we need to add for this agenda item? 02:22:18 <unknown_lamer> I would say we need to plan to be at peer1 until april in the worst case, can't skip democracy. but that also means more time before we start incurring the expense of a second hosting site 02:23:10 <unknown_lamer> I think we should agree on how long to allow member input before making a final decision and getting hosting, two or three days is too little 02:23:47 <unknown_lamer> my propsal would be to accept input through Feb 9, then we meet either that weekend or mon/tue the week after and vote and then get the actual migration going 02:23:49 <smichel17[m]> Although I am in favor of solliciting input from people, I would also like to note that representative democracy is still democracy. 02:24:47 <smichel17[m]> It would beperfectly valid to have the board just make these kinds of decisions without the need to consult everyone in the coop 02:24:56 <unknown_lamer> smichel17[m]: the board is empowered to make most decisions, but something as major as ditching our entire hosting setup for a new one is something cooperative principles require input from the general membership imo 02:26:28 <unknown_lamer> it also doesn't save us time, I won't be ready to begin a migration in an organized manner for at least another week, and incurring expenses before I can clear my schedule and dedicate as much time as possible to it will end poorly (our migration from one hosting provider to peer1 years ago took months and months because we did not plan properly, and just kind of went for it...) 02:26:51 <jackhill> I'm split. I think both things make sense. We haven't really had much engagement at electons time. 02:27:02 <jackhill> Maybe this crisis will get people out to the polls :) 02:28:00 <smichel17[m]> I'm not saying we shouldn't get input (I think we should). I think it might make sense to start moving forward immediately as if we had already recieved that input (eg, decide on which vps provider to use and start the prerequisite sysadmin stuff, which I suspect would be good things to do anyway). 02:28:16 <eronel> If it makes one member feel better about being part of hcoop, then it's probably a good idea to make that person feel more involved. 02:30:57 <smichel17[m]> Anyway, let's move on. What else is needed for this agenda item? 02:31:31 <unknown_lamer> how long do we want to solicit input from members before calling the vote on which provider to move to? 02:31:41 <unknown_lamer> if Feb 9 seems too long, maybe Feb 2 ? 02:31:53 <jackhill> sure 02:32:06 <unknown_lamer> assuming there is no mass dissent or something ;) 02:32:36 <eronel> 1 week from sending the announcement? 02:33:00 <smichel17[m]> Of course. Just because we've done some sysadmin work to prep for migration doesn't mean we can't pivot if we get negative feedback 02:33:10 <unknown_lamer> eronel: a week sounds fine to me 02:33:24 <terpri> a week sounds reasonable for a major change like this 02:33:47 <jackhill> I move that we solicit feedback for one week 02:34:09 <unknown_lamer> second 02:34:31 <unknown_lamer> #info vote: we will solicit input from members on potential vps providers for one week from the time the announcement is sent 02:34:36 <eronel> #info +1 02:34:37 <jackhill> #infor +1 02:34:37 <unknown_lamer> #info +1 02:34:40 <keverets> #info +1 02:34:41 <terpri> #info +1 02:34:42 <jackhill> #info +1 02:35:35 <unknown_lamer> #agreed we will solicit input from members on potential vps providers for one week from the time the announcement is sent 02:35:45 <jackhill> shall we go ahead a schedule a brief board meeting for after the feedback period to ratify the final decision? 02:36:02 <jackhill> so, for at least one month we 02:36:13 <jackhill> 're going to be paying for both hosting providers? 02:36:17 <unknown_lamer> indeed 02:36:39 <smichel17[m]> Presumably March at this point? 02:36:45 <unknown_lamer> the new one will be lower cost enough it will only be pretty painful but not undoable 02:37:42 <jackhill> shall we try to meet on Friday, Feb 2 EST? Same time? 02:37:45 <smichel17[m]> I want to get through this meeting. What's next? 02:38:24 <jackhill> long term direction, but I suggest we do that separately 02:39:07 <unknown_lamer> jackhill: let's finalize the date of that meeting in the next day or two... not sure of availability atm 02:39:22 <jackhill> okay, I'll send out options 02:39:33 <jackhill> #action jackhill send out time options for next meeting 02:39:44 <smichel17[m]> Can we do it, quickly? I want to put some text about long term direction into the email. 02:39:48 <unknown_lamer> actually one minor issue 02:40:08 <unknown_lamer> jackhill: do you recall when peer1 asked us about a year lease? 02:40:20 <unknown_lamer> I feel like it's been about a year now... 02:40:24 <jackhill> no. I'll look it up 02:40:33 <jackhill> #action jackhill find out about peer1 lease renewal 02:40:54 <unknown_lamer> #action unknown_lamer will email peer1 about any terms for breaking in case they decide to be terrible 02:41:18 <unknown_lamer> lease didn't really have breaking penalties, at least not the one we actually signed signed so... 02:41:55 <smichel17[m]> Where is peer1 physically? 02:42:10 <smichel17[m]> *where in NY? 02:42:13 <unknown_lamer> if that was it, i move to move on to the long term direction agenda item (we kind of merged in informing members there) 02:42:21 <unknown_lamer> smichel17[m]: right off of a broad street on the water 02:42:39 <unknown_lamer> right on top of the fiber to london 02:43:05 <jackhill> second 02:43:13 <smichel17[m]> In The City? 02:43:18 <unknown_lamer> smichel17[m]: yep 02:43:44 <smichel17[m]> Let's talk long term, then come back to that. 02:43:46 <unknown_lamer> #topic long term direction 02:44:11 <unknown_lamer> i don't really have any strong opinions, aside from doing what we do and removing me as a support quality bottleneck 02:44:29 <jackhill> peer1 was 10 months handled in Feb 2017, so we should be fine with that 02:44:48 <unknown_lamer> #info <jackhill> peer1 was 10 months handled in Feb 2017, so we should be fine with that 02:45:05 <jackhill> do we really want to do the long-term discussion now? 02:45:18 <jackhill> Will it affect anything we're doing with the move? 02:45:43 <smichel17[m]> Yes. I am interested in what reasons coop members have for staying with the coop. Eg, I personally am here because of FLO values. 02:45:49 <jackhill> okay 02:45:58 <smichel17[m]> I want to put something in the email asking about this 02:46:02 <jackhill> Uh, so how should we start? 02:46:04 <jackhill> Ah. 02:46:40 <jackhill> I too am hear because of software freedom, and because computers are hard, so doing it together makes sense 02:47:21 <jackhill> Long term, I would like use to have enough users that we are doing more than just staying afloat, we are also making a difference in the world. 02:47:26 <unknown_lamer> I would say let's try to keep this bit under 15-20, if anyone wants to throw anything out there to get a longer term conversation started (we are kind of just floating about doing the same thing we've always done, and not super well right now and all...) 02:47:31 <smichel17[m]> To the effect of "As we're thinking about this transition, we're also thinking about the future of the coop, what direction to take it in. So, we're interested in hearing about what reasons you all have for sticking with hcoop. Here's some reasons we could think of: <examples>. I'd appreciate it if you reply and let me know at <s@smichel.me>" 02:47:37 <jackhill> (immagine if we could contribute to OpenAFS development for example). 02:47:58 <unknown_lamer> smichel17[m]: keeping it open ended in the first mail sounds good imo 02:48:17 <eronel> Maybe most people will conteplemate this question and ask to quit. 02:49:10 <jackhill> To get to that point, we may have to consider a different model (are services to individuals really in our sweet spot? Should we get a loan and hire someone? Is conflaiting ownership and subscription to services the right decision?) 02:49:55 <smichel17[m]> eronel: We can mitigate that by phrasing it as "why did you choose hcoop", I think 02:50:03 <jackhill> okay, so reasons: 1) software freedom 02:50:03 <unknown_lamer> certainly a risk... 02:50:17 <jackhill> 2) ease of doing things together 02:50:22 <jackhill> 3) community 02:50:29 <unknown_lamer> if we don't benefit anyone by existing, dissolution would probably be a reasonable course... (boo) 02:50:36 <smichel17[m]> But honestly, if asking that question prompts a mass exodus, maybe it is better for the coop to dissolve 02:50:47 <eronel> I think asking this question in the same email as the query regarding hosting a mistake. 02:51:04 <smichel17[m]> That's fair. When would you rather ask it? 02:51:45 <eronel> Most people don't have time to do much contemplation and we want their feedback on the hosting issue. 02:51:50 <unknown_lamer> +1 02:52:04 <smichel17[m]> Ask after the migration is complete, maybe? 02:52:31 <eronel> I think it's something you can ask as an individual anytime, but it shouldn't be a part of this message. 02:53:13 <smichel17[m]> I'm convinced. Motion to drop this discussion until a later time? 02:53:22 <jackhill> so moved 02:54:34 <smichel17[m]> okay. That our last topic in the agenda? 02:54:49 <smichel17[m]> I actually have one more to add. 02:55:25 <smichel17[m]> Everyone else done with long-term discussion before we move on? 02:55:39 <smichel17[m]> This last thing is sysadmin, could probably happen with just myself and unknown_lamer 02:55:57 <unknown_lamer> no reason to have it be a formal part of the board meeting unless a board decision has to be made 02:56:25 <smichel17[m]> I happen to be in NY for the next week, if there's anything you want done on site at peer1. 02:57:04 <unknown_lamer> small possibility, but I think atm the rack is "stable" 02:57:17 * smichel17[m] isn't sure if that concerns the board at all 02:57:22 <unknown_lamer> we can keep discussing long term plans or call it a meeting, either is fine for me 02:57:41 <jackhill> I move we adjourn 02:57:53 <terpri> seconded 02:58:01 <jackhill> afterwards we also need to make sure smichel17[m] has a good start on the draft mail 02:58:41 <smichel17[m]> I would like you all to tell me what the contents should be. Then (probably tomorrow, this meeting went longer than I anticipated) I'll take all that and put it into email form. 02:58:55 <unknown_lamer> #info vote to adjorn 02:58:57 <unknown_lamer> #info +1 02:58:59 <jackhill> #info +1 02:59:00 <terpri> #info +1 02:59:05 <eronel> #info +1 02:59:23 <keverets> #info +1 02:59:27 <unknown_lamer> #endmeeting