| |
"Carsten Schmitz" <casz@gmx.de> wrote in message news:GCMtBs.ByD@lugnet.com...
> I think Tim has waited to long to get help from other volunteers. There has
> been at least some people in the newsgroups and some via email offering help
> to get the parts update on the way - including me. I did not even get an
> answer. It is one thing to be busy and stressed but it is another thing not
> to notice that you could accept some help when you are just overloaded.
>
> I have seen a whole company breaking down by this because some person did
> not know when to delegate tasks to manage the whole rest... and i see Tim
> Courtney more in the function of a manager.. I think he has to realize that
> by hisself first.
Good point, and I agree. I've gotta work out some management stuff on my own -
especially this week. I'll also be lowering my standards of expectations for
contributors - if people want to contribute pages, just make a text file of the
content, send me the images and the text, and I'll format it. Its too much of a
pain for both me and the contributor to have to format it my way themselves -
they have to get used to it, more demand on them, and I'm such a perfectionist I
end up fixing it anyways.
But back to the parts issue, I'm really not responsible at all. Steve's the
Head Parts Guy. And Steve is working on a parts update system now, we just have
to work out the issue of the immediate update (unofficial, disclaimers attached,
is my opinion of the way to go) to satisfy the users and come back and do the
update right later (using the new system) and have the parts officially added.
I think the parts should be zipped into an unofficial archive, hosted on the
site under /download/updates/unofficial/ and with a big disclaimer attached.
Then the system Steve is working on should be completed, and the parts run
through it and updated properly and added into the official updates.
--
Tim Courtney - tim@ldraw.org
http://www.ldraw.org - Centralized LDraw Resources
|
|
| |
"Tim Courtney" <tim@zacktron.com> wrote in message
news:GCMuJ8.E5M@lugnet.com...
> I think the parts should be zipped into an unofficial archive, hosted on • the
> site under /download/updates/unofficial/ and with a big disclaimer • attached.
> Then the system Steve is working on should be completed, and the parts run
> through it and updated properly and added into the official updates.
I think this needs a little modification - if the parts could be zipped
separately then people could just get the ones they want, and as new
unofficial parts are sent they could be added as individual zips rather than
having to keep creating new batches of parts. If only I had a web server
with MS ASP on I could throw together a system to handle uploading of parts
and automatic conversion to zip format in about 30 minutes, it's that
simple. I guess I'm going to have to look into getting ADSL at home and
running a web server on my laptop so I can help out with this sort of thing
:)
BTW: if the unofficial releases are individually zipped you could also link
the parts ref to them so people could search for and download just the parts
they want. Not sure how practical that would be (plus I guess you'd need to
link all the officially parts to a "offical release" page and the "not done"
parts to a "not done yet" page which could make things a bit difficult).
Dan
|
|
| |
In lugnet.cad.dev, Tim Courtney writes:
> I think the parts should be zipped into an unofficial archive, hosted on the
> site under /download/updates/unofficial/ and with a big disclaimer attached.
> Then the system Steve is working on should be completed, and the parts run
> through it and updated properly and added into the official updates.
This would work. Just don't take Steve off of the new system -- with him
working on it, it's gonna be good.
Cheers,
- jsproat
|
|
| |
In lugnet.cad.dev, Daniel Crichton writes:
> I think this needs a little modification - if the parts could be zipped
> separately then people could just get the ones they want, and as new
> unofficial parts are sent they could be added as individual zips rather than
> having to keep creating new batches of parts. If only I had a web server
> [...]
Let's not reinvent the wheel. This process is already largely done, I would
think, as part of the new parts update system now in development. The
interim solution needs to be quick & easy for the implementors.
Cheers,
- jproat
|
|
| |
In lugnet.cad.dev.org.ldraw, Jeremy H. Sproat writes:
> In lugnet.cad.dev, Tim Courtney writes:
> > I think the parts should be zipped into an unofficial archive, hosted on the
> > site under /download/updates/unofficial/ and with a big disclaimer attached.
> > Then the system Steve is working on should be completed, and the parts run
> > through it and updated properly and added into the official updates.
>
> This would work. Just don't take Steve off of the new system -- with him
> working on it, it's gonna be good.
You can't have your cake and eat it too, Jeremy! Who do you think would be
doing a significant portion (hopefully not all, but non zero) of the
packaging task?
++Lar
|
|
| |
In lugnet.cad.dev, Larry Pieniazek writes:
> In lugnet.cad.dev.org.ldraw, Jeremy H. Sproat writes:
> > In lugnet.cad.dev, Tim Courtney writes:
> > > I think the parts should be zipped into an unofficial archive, hosted on the
> > > site under /download/updates/unofficial/ and with a big disclaimer attached.
> > > Then the system Steve is working on should be completed, and the parts run
> > > through it and updated properly and added into the official updates.
> > This would work. Just don't take Steve off of the new system -- with him
> > working on it, it's gonna be good.
> You can't have your cake and eat it too, Jeremy! Who do you think would be
> doing a significant portion (hopefully not all, but non zero) of the
> packaging task?
Zipping up the parts already collected: 5 minutes
Writing the disclaimer: 2 minutes
Uploading zipfile and disclaimer to LDRAW.ORG: 3 minutes
Catching the warm glow as the parts preview is released: Priceless.
For the really big tasks there's a design committee. For everything else,
there's SmallTask.
Cheers,
- jsproat
|
|
| |
In lugnet.cad.dev, Jeremy H. Sproat writes:
> In lugnet.cad.dev, Larry Pieniazek writes:
> > In lugnet.cad.dev.org.ldraw, Jeremy H. Sproat writes:
> > > In lugnet.cad.dev, Tim Courtney writes:
> > > > I think the parts should be zipped into an unofficial archive, hosted on the
> > > > site under /download/updates/unofficial/ and with a big disclaimer attached.
> > > > Then the system Steve is working on should be completed, and the parts run
> > > > through it and updated properly and added into the official updates.
> > > This would work. Just don't take Steve off of the new system -- with him
> > > working on it, it's gonna be good.
> > You can't have your cake and eat it too, Jeremy! Who do you think would be
> > doing a significant portion (hopefully not all, but non zero) of the
> > packaging task?
>
> Zipping up the parts already collected: 5 minutes
>
> Writing the disclaimer: 2 minutes
>
> Uploading zipfile and disclaimer to LDRAW.ORG: 3 minutes
>
> Catching the warm glow as the parts preview is released: Priceless.
>
> For the really big tasks there's a design committee. For everything else,
> there's SmallTask.
Do you really think this is a 10 minute job? If so you must really have a
low opinion of the gang, then, that they would hold out on you to save a
mere 10 minutes of their time.
I hope that's not the case, but rather that you're just really confused
about how hard it is to do this.
What terrible choices you face me with, though.
Let this drop for a bit, eh? Something will be done. Time to let this rest
before emotions crest above flood stage.
++Lar
|
|
| |
In lugnet.cad.dev, Larry Pieniazek writes:
> Do you really think this is a 10 minute job? If so you must really have a
> low opinion of the gang, then, that they would hold out on you to save a
> mere 10 minutes of their time.
> I hope that's not the case, but rather that you're just really confused
> about how hard it is to do this.
Well tell me then. Larry. How hard is it to just zip up the parts that have
already been submitted, and why? Are they all not sitting in a directory
somewhere on someone's hard drive? Or are they really scattered in an
ad-hoc fashion?
Trust me, I don't intend to argue needlessly over this. But someone's
misinformed; and if it's me, I'd like to fix that.
Cheers,
- jsproat
|
|
| |
In lugnet.cad.dev, Jeremy H. Sproat writes:
> Let's not reinvent the wheel. This process is already largely done, I would
> think, as part of the new parts update system now in development. The
> interim solution needs to be quick & easy for the implementors.
The problem I see with releasing the current unofficial parts in a single
download is that it's going to make it harder for anyone who wants to help
out in checking individual parts - they're going to have to download a large
ZIP file of parts to find the one they want, and if the new system takes a
long time to get up and running then I can see that in the near future there
will be a call for yet another unofficial interim release and then there
will be 2, or 3, or more lumps of parts to download, making it even harder
to find individual parts. The whole point of posting unofficial parts to
cad.dat.parts, at least as far as I could tell in my short time here, was to
provide a way for LDraw (and clones) users to review the parts and suggest
fixes, basically providing a way to get the parts completed to near
perfection before being added to the official release. By providing a ZIP
containing all the current unofficial parts that Steve has collected it's
obvious that this just won't happen, and Steve doesn't have time to review
them all himself (I'm making a sweeping assumption here!). I can see why an
official release is better - unofficial releases will just end up with only
cursory checks made on the parts and dilute the quality of the existing parts.
What a turn around - I've gone from asking for individual part downloads to
none at all!
Dan
|
|
| |
In lugnet.cad.dev, Sproaticus wrote:
> In lugnet.cad.dev, Tim Courtney writes:
> > I think the parts should be zipped into an unofficial archive, hosted on the
> > site under /download/updates/unofficial/ and with a big disclaimer attached.
> > Then the system Steve is working on should be completed, and the parts run
> > through it and updated properly and added into the official updates.
>
> This would work. Just don't take Steve off of the new system -- with him
> working on it, it's gonna be good.
I think I can use my part-voting-preparation utilities to generate a
webpage like the ones we use for voting. So people could check out what
the unofficial parts are, and either download them all in one shot, or just
grab what they want.
Steve
|
|
| |
how about making all unofficial parts go to "unofficial" group like bricks
and plates?
--
And they said 'Computers will never be in general use'
"Sproaticus" <jsproat@io.com> wrote in message news:GCo1LK.Gpx@lugnet.com...
> In lugnet.cad.dev, Larry Pieniazek writes:
> > Do you really think this is a 10 minute job? If so you must really have a
> > low opinion of the gang, then, that they would hold out on you to save a
> > mere 10 minutes of their time.
>
> > I hope that's not the case, but rather that you're just really confused
> > about how hard it is to do this.
>
> Well tell me then. Larry. How hard is it to just zip up the parts that • have
> already been submitted, and why? Are they all not sitting in a directory
> somewhere on someone's hard drive? Or are they really scattered in an
> ad-hoc fashion?
>
> Trust me, I don't intend to argue needlessly over this. But someone's
> misinformed; and if it's me, I'd like to fix that.
>
> Cheers,
> - jsproat
|
|
|
