According to the latest news on the YPN home page, there was supposed to be a sasq beta soon. Is that up yet?

_________________
If VB is fun, what's everything else?


[ This Message was edited by: dxprog on 2002-06-30 00:06 ]

no, Moxx and I had some difficulties with the design of cetrain stuff, which Moxx is working on atm. I think we'll be able to put up a beta at the end of july or something. I will inform you as soon as we've put it up.
But, at least there are ppls that are readin the news
[addsig]

End of July is a realistic date.

If only fabs was back again!
[addsig]

if fabs won't be back to coding on sasq till I'm back from germany (25th July), I'll finish the users authentication and such stuff, so that it's at least usable.
[addsig]

Well, that'll be the only way to go. To be honest, I think we could finish the whole site alone, it would just take longer. [addsig]

I think so too, but fabs already started that user module thingy, so he should finish it, cuz I think he also had some ideas about how to design it
It'd ofcourse be no prob to code it with 2 ppls, but it'll take it's time
[addsig]

Thanks. I'm just really itching to get rolling on my theme. [addsig]

if you have CVS installed, you could maybe also try to help us. To access our CVS server, you need CVS, and a valid SSH1/2 key
[addsig]

CVS
lol
who uses CVS
d-:

sacah: professionals and others wanting a powerful tool for project handling

sacah tried CVS once, but since he's a windows user he isn't used to such powerful shell applications
[addsig]

lol. aren't there frontends for windows?

I have CVS but I have no idea what to do, so I'll need a little help getting things set up. For starters whats a SSH1/2? [addsig]

dxprog: I went through the same trouble, though I knew what everything was, looks like you are in for some hard times.

fsvara: There are frontends, but they did not work, they were shocking, I got CVS to work, and can use it, its just stupid in my mind.
(-:
Though my mind is stupid.
Logical.

dxprog:
SSH is the "Secure SHell". With it you can send date to a server without worrying that somebody is listening to you, cuz even if somebody is, he won't be able to get a thing out of your transmission. It's a server/client based program. And, now to the SSH key thingy:
there are 2 versions of the SSH protocol, 1 and 2. For both versions there is something that is called "SSH Key". It's like a doorlock irl. Imagine you're standing infront of a door. The door is locked by a lock. You need a key to open the door (unless you break it....). This is almost the same as in SSH. But in SSH's case, you are the lock of the door, and the server has the key. When you generate a SSH key, you always get a key pair. One is the private key - which you mustn't show to _anybody_ - and the public key. You copy the public key to all hosts you want to use the key for. Like this you will be able to log into a server without entering your password. This is extremely secure, because nobody can tap your line and get the password out.
We use this SSH Key authentication for the CVS server we've got our Sasquatch stuff on. It's not our server, so we can't change this.
This was just a rough description, and may be a bit unclear. Maybe you should take a look at the docs of OpenSSH.
http://www.openssh.com/
[addsig]

You know ppl are able to sniff and decode SSH transmissions, have been able to for quite a while now?
Just correcting the last posted message
(-:

sacah: proove it! i don't believe you

even tho everybody knows OpenBSD lollipops (read this, JaZper? ) openssh works quite well afaik at least... well, if you don't count that remote root bug in

CVS can't be that bad. I mean it has a fish for a logo. I love fish!

And about the SSH key where do I go to get one? And I'll need the path to the server where sasq is. [addsig]

To conclude this discussion:

If you're going for a bigger project you'll need version controlling. CVS is a free version controlling software.

Find a better one in its price class and you have convinced me that it is crap...

[addsig]

Bingo!! [addsig]

Quote:
On 2002-07-04 03:54, MoX wrote:
If you're going for a bigger project you'll need version controlling.


Linux (the kernel!) isn't a big project?

Well, I think Linux (the kernel) is too big for efficient cvs use. When I say to big I don't mean the program but the number of people working on it. Btw: I have no idea how the kernel code is maintained, so please tell me!

For a group of people working on a project consisting of lots of files cvs saves a you a lot work. I won't go without version controlling in bigger projects. [addsig]

as far as i know, linux kernel development works with people just writing patches. they then send them to the subsystem maintainers (a person responsible for the part of the kernel the patch changes, like Alan Cox, and all those other famous maintainers.) If the patch is any good, they pass it on to Linus who commits it to his own kernel tree (if he thinks it's good, too). I guess that's the idea behind it. But in realuty it's a bit more complicated, with people having their own trees (like Alan Cox's -ac, arkangeli's -aa. etc) that might take other patches than linus' vanilla tree. So sometimes linus just syncs with some parts of the ac treefor example...
and people usually send their patches to the subsystem amintainer, AND directly to Linus...
A lot of the maintainers themselves use CVS o similar systems internally. Linus used to use CVS privately, but he switched together with a lot of othe maintaines to BitKeeper, which seems to be somewhat more advanced, but it is subject to some strange license.. I'm not really sure, but it isnt free software...

All this fun going on can nicely be watched on the linux-kernel mailing list

Ah, wasn't that the reason for some trouble between the FSF and Linux?

Well, as much as I regard Linus, I'm with RMS when he says it should stay as free a project as possible.

But that's only my opinion. [addsig]

afaik CVS is also used in professional (if you can call it like this...) programming companies. Not sure about this, but if it is true, that'd mean that CVS is really good
[addsig]

I'm sure that it's pretty good!

But the industry still prefers commercial products in most cases, because they consider it these more reliable. Anyway, CVS is a cheap and useful way to do things. And, what features could commercial version control software have which CVS does not offer? [addsig]

unfortunalety I don't know what features you could still include... maybe that it doesn't scandisk up when you are working on 1 file with more than 1 guy?
[addsig]

Well, how should that be done? It would have to merge the files somehow and to me this sounds like it could create much more trouble than do any good.

For editing the same file with more than one person you probably need something like a multiuser text editor [addsig]

heheh, let's work on that after sasquatch! I need something else than WebDev
[addsig]

Why would two people want to work on the same file at once? Such a situation would indicate that the code tree is badly structured

why? for example in web-dev. Let's say you have a bug in a stylesheet. One sees it and fixes it, the other one extends it. There we already have it
[addsig]

Don't forget to mention the extreme fun of doing so.

Seriously, I think it'll work out better than two people working on the same file in different locations (like with cvs) so that they have to merge it afterwards in some painful process. [addsig]

How would you do it though, both would have to update in real time, but someone could just see what you type and delete it, real time,
(-:
I can see some fun there

Well, we already thougth of different methods here. One, which might be the easiest, is that the line someone edits is "locked" so that nobody else can interfere there. Another, probably more chaotic method is to do a realtime update, where everything like network lags and stuff might cause a lot of mess.

At least it will be possible, no matter which method we use. Maybe only practical testing will show which method will work better. [addsig]

locking the line sounds reasonable... you'll just have to keep track of the line number somehow in case somebody else inserts a line above...
anyway i don't think (i hope at least ) no two people would want to edit the same line at once.

Think of two people editing the same [i]word[/i} the same time [addsig]

painful = good
that's how I've fixed my PC, it was painful
[addsig]