Anyone who is listed as a developer on the project page has CVS
rights. I don't believe there is anyway to restrict cvs use through
Sourceforge for members of the project.
Maybe Jordi can write up some mailing list rules/guidelines and post
them to the list every so often to refresh people's me
Who has CVS rights? I think that we need to start getting more delegation
going in the admin with regards to updates and the like.
How many people on this list are members of the other lists (i take -help as
a given)? I know that this list is aimed at doing that, but it has turned
into a "co
Because they are management, and are thuslly computer illiterate..
to them one distro is the same as the next..
This is the type that is using NS 4.08 "because it works" no
matter how often their admin's tell them to upgrade.
- Original Message -
From: "Bart Bizon" <[EMAIL PROTECTED]>
T
Don't wet your pants.
I missed that detail ;)
What am I supposed to get over?
I have no intention to fuck guy, don't even know him...
and... exhale..
So why are your employers looking at the DynAPI distro at all?
They should only be looking at a branch that is under your/their control.
Or a
> But here's another question.
> Why did you not develop your own branch independently of DynAPI.
> If you are coding a largescale commercial site, you should have absolute control
>over the code.
> With an opensource distro, you don't.
If you had read Doug's mail you would know that he *IS* usi
And yet AGAIN..
WE ARE STILL USING THE ORIGIONAL DISTRO.
THIS IS NOT THE PROBLEM.
THE PROBLEM IS WITH POTENTIAL USERS AND EMPLOYERS LOOKING AT THE 'STABLE
RELEASE'
AND FINDING THAT IT IS NOT STABLE
FUCK GUY. GET OVER IT.
- Original Message -
From: "Bart Bizon" <[EMAIL PROTECTED]>
Granted.
But here's another question.
Why did you not develop your own branch independently of DynAPI.
If you are coding a largescale commercial site, you should have absolute control over
the code.
With an opensource distro, you don't.
I did exactly this with dynAPI1 ways back, as stuff was
First off, I don't have to be involved in many open-source projects to know about what
the policies are.
You don't have to do drugs to know they are unhealthy ;)
And I didn't say you shouldn't test to make sure that a release is stable before
commiting it.
It only stands to reasons that you sh
I fully agree with the need to test ALL examples before applying code. I
also agree with the need to make the examples a "testbed" for any future
changes.
I do, however, want to know when files started disappearing from the
examples page. My distro is based on the files that existed when I s
> Sure it's good practise to check before you commit a stable release.
> But it's up to the developer doing it.
I don't know in how many open source projects you're involved, but
all projects I know have a quite rigid policy concerning commits into
the stable tree.
People with a write access bea
Actually, the end of the world is near.
DynAPI is to blame.
Period.
*s*
> I normally don't like to enter in such conversation, since I consider myself
> a real newbie compared to most of you Javascript GODS in this lists, but ..
> could you ALL cheer up a little? DYNAPI is not that much damage..
I normally don't like to enter in such conversation, since I consider myself
a real newbie compared to most of you Javascript GODS in this lists, but ...
could you ALL cheer up a little? DYNAPI is not that much damage...
However my project does also rely heavely on DYNAPI. I always use the late
Sure it's good practise to check before you commit a stable release.
But it's up to the developer doing it.
He/she is not beeing payed for it.
And he is not bound by any requirements/warranties, that usually come with a
commercial product.
A LGPL product is not by any means a commercial product
A fix was checked in that does ont work on ALL systems.
It was then release without checking.
I don't give a fuck what you do with your own time.
But I still don't think it's too much to ask for a cursory run through the
examples.
This was obviously not done as this critical error (not on browser
Doug,
whatever you do, it's your decisions. Nobody can force you.
> They are now questioning my salary.
They should. period.
Whenever you use anything that is GPL or LPGL (like dynapi) it means: "NO
WARRANTY"
Do I have to write it red?
I repeat: whenever you use GPL or LPGL stuff you have no wa
let's try this again.
Managagement went to dynapi.sourceforge.net
they downloaded the official 'stable' distro.
they ran the examples.
they found that hardly any of them worked.
they panicked.
they screamed.
They are now questioning my salary.
You dont call something the "Latest Stable Release "
Are you sure? I'm running:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001108
Netscape6/6.0
and the following page does not display scroll bars but messes up the
dynlayer.
8an
Title: DynAPI Distribution: Create Example
I feel sorry for your situation, but I think your comments are a bit
harsh. A couple of things I have to point out:
- Why was management being shown a "test" site without being warned that
there may be some bugs?
- Why was management able to trigger a bug that you hadn't noticed as
part of y
18 matches
Mail list logo
