Hello folks,
I've been looking for a DVCS and ticket system for a while now, to make my job
easier at work and I find Fossil looks really enticing. I've read the docs
about fossil for 3-4 hours now, and I think it's time for some questions I have
that do not seem to have immediate obvious answers. I'm sorry the answers I
look for are already somewhere, feel free to send me there to look if you have
the right pointers.
To give you some background : We have a central office with satellite offices.
The satellite offices are on ships, so they very often are disconnected, and
they suffer from low bandwidth and high latency connections (satellite
connections in the very space and stars sense of the term). We have many
(10-100) users in each ship/office. Some users are teams, some users are
individuals. Basically the satellite users mostly get support from the central
office. Sometimes this support needs to happen in near realtime and is so done
by email (which prevents any easy history tracking and knowledge spreading).
Is it possible to have a setup with a central server and multiple satellite
servers with near realtime replication going on between them ? I imagine a
scenario where each site has a server and where users use the server at their
own site.
My mains goals are :
* speedy user interface for every one. (central or satellite office)
* low use of bandwidth btw offices (meaning no user go and try to talk
to the central server from a satellite office).
* low latency in ticket replication (seconds desired, a few minutes at
the most) between offices.
Other desirable features :
* ease of creation or suppression of a satellite office
* the possibility to segregate tickets by office (I think that can be
done with tags and maybe branches)
The first step in our use of it would be for the wiki and the ticket system. Do
ticket get replicated automatically to a central server when the user clicks
"send" ? or does this require other user action ? Same for answers from a
central office that would get posted to a central server, do satellite users
need to do something to receive new data, or is it automatically pushed to
satellite office servers ?
Do the tickets support the limitation in size of artifacts attached to them ?
It happens sometimes that satellite office use diverging code compared to our
main branch. Is it possible to segregate the tickets by branch ? and is it
possible perhaps to synchronise a satellite server only on one branch of the
main server ?
Is there a way to see when a satellite server has replicated a ticket to the
central server ?
Also I can easily see the wiki interface being used as a distributed help and
documentation system by the technical minded people at each sites. But there
needs to be some measure of control in this area for us. Is it possible
currently to show only the latest "approved pages" and along that modifications
that have been proposed by users ? Is merging of wiki pages possible ?
Does the wiki support images ?
Anybody knows of something that allows tracking and answering tickets from a
mobile phone ?
Thanks in advance for your input.
Brgds,
Charles.
This e-mail, including any attachments and response string, may contain
proprietary information which is confidential and may be legally privileged. It
is for the intended recipient only. If you are not the intended recipient or
transmission error has misdirected this e-mail, please notify the author by
return e-mail and delete this message and any attachment immediately. If you
are not the intended recipient you must not use, disclose, distribute, forward,
copy, print or rely on this e-mail in any way except as permitted by the author.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
