Thank you for the tremendous feedback.
>From Franz first.
· Furthermore, as I said, this was a pretty linear scenario. One of
the kind SVN likes. But Git (and other distributed version control systems)
was developed for a reason, and the reason is flexibility and … well …
distribution. Using Git, there is no need for linearity in your history.
Git was made for all kinds of different and customized workflows. And since
Git has a well-established tool-set (and community, see GitHub!), one
should not try to rebuild this functionality, but instead facilitate it. As
a tool developer, you need to find out, what the actual needs of your
“clients” (aka developers) are. If 90% of the developers’ problems could be
solved just by applying a smart combination of Saros and Git, you can save
an incredible amount of development time just by finding, describing, and
teaching these smart ways of combine the tools. ·
I'm not used to use Git because my lack of experience. That's why I my
proposal came up. I'll definitely accustomed myself with version control
system first. Any pointer on how I should learn it?
The leverage point I mentioned above: I can imagine that for Bob it might
be quite hard to determine what Alice did *since the end of their session*,
since the built-in diff tools only know about the commits and nothing
in-between. So for this particular use case and maybe several others, I
would be nice for Saros users to gain a deeper insight in what the other
developers actually did during a session. Actually, we would be interested
in such amendments which help the Saros users by providing a better
“awareness” of their co-workers.
This is interesting. Is it like at one time Alice did A, view minutes later
Alice did B? I guess the problem is how to display what Alice did in a way
that can be understand and not annoying to Bob, right?
Next is from Stefan.
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.
>
Actually those two features were what I think to be implemented, but from
the discussion it is better to use version control for those two features.
What do you mean with persistent session ? If you leave a session(N>2
> users) you are "out of sync".
>
Not technically a persistent session, but a predefined session. Some
developers make predefined session to work for one project. When they're
connected they're automatically join the session.
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.
>
I hadn't known Saros could do that. The project site doesn't mention in
obvious way. I just found out it is mentioned in feature list page.
Best regards,
Raydhitya
--
Raydhitya Yoseph
Informatics Engineering
Institut Teknologi Bandung
http://raydhityayoseph.blogspot.com
------------------------------------------------------------------------------
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
