On Nov 13, 2011, at 10:33 PM, Julian Fagir wrote:
For people who dislike fossil as a wiki or vcs, there are still other
solutions, but they're not automated, so that wouldn't stop me.
So, my question: Do you think fossil is appropriate?
As a vcs yes. The ticketing system needs some setup
On Wed, Nov 16, 2011 at 12:29 PM, Remigiusz Modrzejewski l...@maxnet.org.pl
wrote:
As a vcs yes. The ticketing system needs some setup to fit my taste, but
that's not hard. But, sadly, the wiki is way too simplistic to be
practical. But this probably will be resolved one day.
Actually
On Nov 16, 2011, at 4:11 PM, Stephan Beal wrote:
As a vcs yes. The ticketing system needs some setup to fit my taste, but
that's not hard. But, sadly, the wiki is way too simplistic to be
practical. But this probably will be resolved one day.
Actually the JSON API is far enough along
On Sun, Nov 13, 2011 at 4:33 PM, Julian Fagir listensamm...@komkon2.de wrote:
So, my question: Do you think fossil is appropriate?
It really depends on your and your customers' needs. It works well for
decent number of projects. Certainly has has served the needs of the
projects my coworkers
Hi,
I'm somewhat new to fossil, but I'm absolutely astonished by the features it
provides despite its simplicity.
I'd like to provide fossil for our (ISPs) users because of its ease of
automation:
1. fossil init
2. fossil user password
3. Generate DNS records, config and CGI for webserver
5 matches
Mail list logo
