Just some short statements, see below
On 03.06.2013 13:12, Zieris, Franz wrote:
Hi Raydhitya,
You should have received a preliminary reply from me right after your
first request. However, I was ill last week so I could not compose my
follow-up mail earlier.
I just granted you the permission to push new changes which then can
be reviewed by the other developers. As every new developer, you are
not allowed to commit those changes to our central repository yet.
Your changes will stay in our review system until a senior developer
approves them.
The first thing that comes to my mind when I read your feature
proposal: That does not sound like Saros's main purpose. Instead, it
looks like you want to add version control features without using
version control. Did you consider using SVN or Git in your use case?
For clarification: Could you sketch the problems your proposal could
solve, which a workflow using Saros and version control couldn't?
http://sourceforge.net/p/dpp/feature-requests/107/
http://sourceforge.net/p/dpp/feature-requests/100/
Please keep in mind that I do NOT decide which feature should be
implemented, so that is the task of Franz.
Best Regards,
Franz
*From:*Raydhitya Yoseph [mailto:raydhitya.yos...@gmail.com]
*Sent:* Monday, June 03, 2013 11:22 AM
*To:* dpp-devel@lists.sourceforge.net
*Subject:* [DPP-Devel] Asking Idea
I asked for push permission a week ago and still waiting for the reply.
Meanwhile I explored Saros using JTourBus and it's log and now I want
to ask about my idea.
I'm currently an undergraduate student in Institut Teknologi Bandung
which located in Indonesia. I'm interested in Global Software
Development (GSD) and decided to make GSD as my final project. So,
after discussing with my supervisor and researching for tools which
help doing GSD project I found out about Saros.
My idea is basically adding asynchronous feature to Saros. The
feature's use case will be when two or more programmers working on one
project and they are separated geographically.
It consists of 3 features:
1. Record session so programmers can know their previous sessions;
2. Gives highlight to what have been changed from previous version
like diff;
3. Asynchronous messaging like email.
The use case will be one day the programmers sit in a session
together. Then one will logged out from the session first because of
time difference. Next day the programmers whom logged out first can
receive message from other programmers and his/her project synchronize
with the change after he/she left plus adding color highlighting to
the difference.
I tried sharing one project and when the remote user choose existing
destination Saros will overwrite the contents. So my first question:
is it possible to change this behavior to check the destination
project similarity against host project and add the difference?
The host is sending you the files that do not match. How to merge them
correctly and send it back ? I do not know, but to be honest we have
massive synchronization problems / defects when the session goes beyond
2 users.
Please keep that in mind when designing such features because they
should work with N>2 session users concurrently (other users may invited
during the merge process etc. pp.).
Second question, how about the concept of persistent session with
predefined project and users? Is this possible?
What do you mean with persistent session ? If you leave a session(N>2
users) you are "out of sync".
One last feature my supervisor suggested is non automatic
synchronization for some parts of the project. During one session, one
programmer can make the project uncompilable at the same time the
other programmer want to compile the project. Finally last question:
is it possible to synchronize only when the programmer wants to do so?
The projects are always synchronized on sharing start and stay
synchronized the full time.
This is currently a "mental problem" of Distributed Pair Programming.
Most users only see the benefits of DPP but not the "disadvantages". You
are collaborating on shared resources in real time and
so this is a common scenario. It depends on the programming language you
use. E.g: You can "run" Java programms with compile errors as long as
the class that could not be compiled is not loaded during JVM runtime.
As for C/C++ this will not work.
We already offering partial sharing mode (also not full defect free)
which offers you the opportunity to only share a subset of files of a
project where you can later add more files as necessary. This should
help to prevent some compile
errors on some sides.
BR,
Stefan
I'll really appreciate any given help.
Thank you,
Raydhitya
--
Raydhitya Yoseph
Informatics Engineering
Institut Teknologi Bandung
http://raydhityayoseph.blogspot.com
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
