We are still working on getting our POS system ready to put out there. At the moment, the basic stumbling blocks are making sure that all the code is sanitized (i.e., no specifics of bank accounts, merchant services accounts and the like) embedded in the code, and that it still requires a MS SQL Server installation to run. Unfortunately, volunteer programmers do have a lot of projects they want to work on, so I'm not sure how long it will be.
On the bright side, it sounds like it does everything on your dream list. --David David Kominsky [email protected] 503-206-3500 CubeSpace 622 SE Grand Avenue Portland, OR 97214 On Mon, Feb 16, 2009 at 9:21 AM, Alex Hillman <[email protected]>wrote: > Hey All, > > So IndyHall finds itself in an interesting situation...a good situation, > but a situation nonetheless. Low-tech whiteboards worked, but now... > > We're increasingly full, almost every day. Desk reservations for non-full > time members are becoming a *must. *People need to know if there is even > an available desk before they make the trip down to the space. We're > moderately oversold, but not dangerously so. So long as everyone is using > the reservation system, we're good. > > The policy (as unofficial as any policy that comes out of my mouth) is that > if you show up without a reservation and there's a desk, rock on. But if a > reservation holder shows up, you get to move to the couch (not the ugliest > of fates, IMHO). > > Systems-wise: > > We've been using Genbook.com, and...it works, but it isn't ideal. > > I've been playing with HourTime.com too, and...it would work, but isn't > perfect. > > I know Amit and Darrell are working on JellyDesk, but to my knowledge > haven't shared a prototype yet. > > I just tried out divvy.com, and it's SO close...but clearly incomplete, > slow, and still....not quite right. > > We need the ability for multiple levels of users to share the same pool of > resources, including desks and our conference room. > > What are you using, and how does it work for you? > > -Alex > > P.S. For the record, my dream app goes something like this: > > - Two data models: Members and resources. > - Resources have properties (like when they can be reserved, how often, > and for how long). > - Members have properties (like how often they can reserve, what > resources they can reserve, etc). > - Non members can reserve utilities too (no account required, but > process aided by account details). > - Reporting and even automatic billing would be *nice* (and certainly > useful) but aren't as required as the flexibility of multiple member levels > sharing the same pool of resources. > > > > -- > ----- > -- > ----- > Alex Hillman > im always developing something > digital: [email protected] > helpful: www.unstick.me > visual: www.dangerouslyawesome.com > local: www.indyhall.org > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Coworking" group. 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/coworking?hl=en -~----------~----~----~----~------~----~------~--~---
