[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[koi-dev] Collaboration tools question
|
- From: Alex Karasulu <aok123@xxxxxxxxxxxxx>
- Date: Thu, 22 Jan 2004 12:14:45 -0500
- Delivered-to: koi-dev@eclipse.org
- Organization: Solarsis Group
Hello,
Fogive for not checking the archives just yet (lost my password) but
I was wondering if the koi effort has the following class of tool in
mind:
Most repos like CVS have published branches of developement but one
could view a users working directory as a private branch especially
if there is some means to version local changes to the working directory.
Developers while working with their working directories are secluded
from each other. Conflicts often arrise in certain files where these
developers step on one anothers changes. The problem with this is the
fact that you don't know about the conflict until you check in. A good
practice when using concurrent versioning systems is to make your
changes as atomic as possible updating and checking in frequently to
minimize the potential for conflicts. But then again they do arrise.
If conflicts could be detect at the point in which they occur then
both parties could be informed of it at the point in which at least
on of the developers has a fresh mental stack regarding the conflict.
Rather than leave conflict detection on a public branch up until the
point of an update or a checkin by either developer a XP tool can
inform both parties of it immediately. Also these private branches
(within the user's working directory) as well as published ones residing
on the CVS server could be used to detect conflicts in real time.
Take this to an extreme (excuse the pun) and you could easily see a
subtle form of XP in the form of pair and group programing emerging.
With a peer to peer communication framework interactions between
developers can be followed and cordinated. Instant messaging and the
ability to see the activities of others on the code, if granted access
to do so, would allow for a high degree of collaboration between two
or more developers.
I'm sure these things to some degree have been discussed. If not what
are your thoughts and how possible and in what time frame do you think
the Koi project can create these XP tools?
Thanks,
Alex Karasulu