Fwd: [Xastir] RE: Tiger -> Shapefile Processing

Kyle Kienapfel doctor.whom at gmail.com
Wed Oct 4 16:55:07 EDT 2006


Whoops, forgot to go for reply to all. Again

---------- Forwarded message ----------
From: Kyle Kienapfel <doctor.whom at gmail.com>
Date: Oct 4, 2006 1:54 PM
Subject: Re: [Xastir] RE: Tiger -> Shapefile Processing
To: James Ewen <jewen at shaw.ca>


Hah we're coordinating how to be uncoordinated, I like that.

We could also issue tacit consent to help things on.

"Hi I didn't read your post but go for it!"

On 10/4/06, James Ewen <jewen at shaw.ca> wrote:
> > All I can say is that I stated that I'd wait for
> > someone to say "Yeah, sure, go ahead" or "No
> > that's okay" and I didn't receive any direction
> > one way or another.
>
> Sometime you have to assume tacit consent... Waiting for an "Attaboy!", or a "Way to go!" can leave you sitting for a long time!
>
> If nobody screams "No, don't do it!", you can probably consider that a yes.
>
> > Let's change the protocol to:  Tell the list if
> > you're going to do it.  In other words, don't ask,
> > don't coordinate, just do it.  ;-)
>
> I think Curt fell in the deep end here... He's got a good idea, but let's forget the don't coordinate bit.
>
> This list is a resource that can be used to coordinate all kinds of tasks associated with the Xastir project. This is enough of a "geek" list that you won't get flamed for discussing the inner workings of your script processes. Unlike other SIGs that I belong to, never once that I can recall have I ever seen one "I don't want all this useless garbage in my Inbox!" type message.
>
> I would suggest modifying Curt's new policy to something more like this:
> Tell the list you are going to do it.
> Ask if anyone is working on something similar.
> If so, possibly share ideas, coordinate and work together and do it.
> If not, just do it.
>
> Notice that no matter whether you get a yes or a no, the job still gets done!
>
> Xastir is a quasi-uncoordinated group project. There's no official project manager to go to to be assigned a task. (I didn't know you could use 'to' so many times in close succession!) You can always make changes to code, or add to the pool of resources available. If what you have done is a good thing, it will be incorporated in the code base, or used by others.
>
> James
> VE6SRV
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>



More information about the Xastir mailing list