Complete.Org: Mailing Lists: Archives: discussion: February 2002:
[aclug-L] Re: volunteers
Home

[aclug-L] Re: volunteers

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: discussion@xxxxxxxxx
Subject: [aclug-L] Re: volunteers
From: "Ryan Hunt" <ryan@xxxxxxxx>
Date: Fri, 8 Feb 2002 14:57:18 -0600 (CST)
Reply-to: discussion@xxxxxxxxx

Id like to see an database of members, giving information would be completly
voulntary but adding ur info to a searchable roster that could act like an
address book with people's names, instant messanger info, email addresses,
what distro linux they run, nick names or aliases, mebe pictures or
additional information... It would help the new people get fimilar with
other people's names and background... I dont know if the results would
outweigh the work but its an idea...

-Ryan

> 
> Jonathan Hall wrote:
>> 
>> The existing site uses Zope, which is much like OpenACS in many ways. 
>> I believe Zope is actually a much more feature-rich application than
>> OpenACS, although OpenACS is probably more 'mature'.  Unless there's a
>> good reason to switch to OpenACS, I suspect Zope is the better way to
>> go... simply because we have a server on an OC-3 already running zope
>> :)
> 
> I don't buy the argument that we should use Zope because it's what is
> already in use (which we've pretty much agreed is wanting). I also
> think that the hosting question should be separate from tools/content
> development (although the latter may impose some requirements that
> limit hosting choices; traffic and dataset size also impose
> requirements).
> 
> The real question is whether Zope is really better (multifaceted word)
> than OpenACS for our requirements. At this point I don't know Zope (or
> Python), and would appreciate any insights from anyone who has
> experience with Zope and/or OpenACS.
> 
> The other thing is to work out a list of things people would like to
> see on the website.
> 
>> There was some dicusssion on the committee list about moving the
>> server back to Kansas, and some suggested leaving it on the OC-3 is
>> best.  I'm still not entirely convinced, though.
>> 
>> I think if we have people willing and able to work on the software, we
>> sorta need the server where they can use it... Perhaps we can get a
>> good colocation deal from a local ISP?  Maybe iWichita, Websurf,
>> Datility? Something that would give us enough bandwidht, but also
>> local access if/when necessary?
> 
> -- 
> /*
>  *  Tom Hull * thull at kscable.com * http://www.tomhull.com/
>  */
> -- This is the discussion@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi


-- This is the discussion@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi


[Prev in Thread] Current Thread [Next in Thread]