Subject: Re: Helping Out
From: Daniel E. Lautenschleger (dan@www.molbio.wisc.edu)
Date: Sat Feb 24 2001 - 09:43:24 EST
I think many folks would like to see dropkludge, a DID database, and the
feature that allows files created in netatalk volumes to have the same
ownership and permissions as the parent (correct)?
Maybe a "hit list" of items that need fixing by v1.5 release?
If someone can (with detail) spell out the items that need fixing so we
all understand each problem, folks can begin working on these items.
Can we make a list on the site for developers to see what needs fixing and
what's fixed as time progresses?
-Dan
On Fri, 23 Feb 2001, Marc J. Miller wrote:
> So far, it has been pretty much fixing anything we see needs to be fixed
> and adding what features we'd like to see. Myself, I'd love to see
> dropkludge get fixed, but the reason I stopped working on it was that I ran
> out of ideas on how to fix it and I ran out of time to work on it. I've
> got other duties to attend to before I change occupations in about a month.
>
> At 03:03 PM 2/23/01 -0600, Daniel E. Lautenschleger wrote:
> >Jeff:
> >
> >I would love to help out and assemble documentation that would ease
> >installation/operational issues. The problem is, I don't fully understand
> >what changes have been made since the whole shebang got moved to
> >sourceforge and truly what all the options and challenges are for the
> >various installs on the different platforms.
> >
> >If you have a general direction or thoughts of how I might proceed, I
> >am more than willing to help out. I've thought for quite some time that
> >there are not enough people helping you out.
> >
> >Here's another thought meant to be non-offensive:
> >
> >You for the courage and talent, have signed on to administor the Netatalk
> >project on SourceForge. Therefore, you need to spell out *exactly* what
> >areas you need help with (besides documentation) and say I need someone to
> >do this, somone to do this other thing, etc... and approach it that way.
> >
> >Who are the current members of the team that are strong at programming?
> >Who is good at writing documentation? Who can communicate on a regular
> >basis regarding bugs that need to be resolved? Is it even a bug? Who is
> >going to regularly respond to people in the help forum (besides other
> >users) to assist with simple and/or major issues?
> >
> >I gues we need some structure added to the SourceForge site and I'm as
> >guilty as anyone else for not doing more to promote this as I have signed
> >up as developer. Well, I suck at C but I don't mind doing some
> >administrative work if you'd like me to.
> >
> >Just some thoughts that I think may move us forward with a more
> >presentable operation as v1.5 release approaches.
> >
> >Tell ya' what, rather than rambling any longer, I will seriously examine
> >what I think needs to happen with regard to making a more effective
> >SourceForge presence over the weekend and present you with my ideas next
> >week via e-mail.
> >
> >I can stop my complaining and contribute that energy to the project :-)
> >
> >Sorry for the ramblings...
> >
> >-Dan
> >
> >On Fri, 23 Feb 2001, jeff wrote:
> >
> > > "Daniel E. Lautenschleger" wrote:
> > > >
> > > > You've got to be kidding me...
> > > >
> > > > What the heck does --enable-redhat do? In fact, where the hell is
> > complete
> > > > documentation on the various installation options as well as what's been
> > > > fixed after each release!!!!!!
> > > >
> > > > Not trying to piss anyone off. Jeff has done a fine job so far :-) It
> > > > justs gets frustrating at times.
> > > >
> > > > No flaming please. Just a bit of venting. I am now patient and
> > > > grateful once again...
> > >
> > > That's okay. I'm not offended.
> > >
> > > I *know* that documentation is lacking, other than the usually unhelpful
> > > "./configure --help", which still doesn't explain much about the
> > > options.
> > >
> > > If anyone would like to help out, it would be much appreciated, since
> > > the README was last slightly patched when I had a little bit of free
> > > time, and I haven't really had time to maintain it.
> > >
> > > Might move the --enable-redhat,--enable-suse, etc switches to
> > > --enable-sysv=(redhat|suse|...) or something in the future, since a ton
> > > of switches like that is just bound to get confusing.
> > >
> > > jeff
> > > (with tremendous apologies for the cross-posting)
> > >
> >
> >--
> >
> >Daniel E. Lautenschleger
> >University of Wisconsin
> >R.M. Bock Laboratories
> >Network Administrator and Computer Support
> >dan@www.molbio.wisc.edu
>
>
--Daniel E. Lautenschleger University of Wisconsin R.M. Bock Laboratories Network Administrator and Computer Support dan@www.molbio.wisc.edu
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:33 EDT