Hi,
The engg team in my company is replacing the legacy Gitolite-based repository manage to BitBucket. The Technical Publications team currently does not have any source-control software and we are planning to use Flare with BitBucket as well. Can someone explain the process, pros, and cons. Assuming some of the technical writers are not very tech-savvy, will the GUI help in checking the sources files in and out of the repository without someone having to approve it? Thanks in advance!
Moving to BitBucket
-
Techno
- Sr. Propeller Head
- Posts: 193
- Joined: Fri Dec 09, 2005 9:23 pm
- Location: NORTHAMPTON, England, UK
- Contact:
Re: Moving to BitBucket
Provided Flare's Bind Detection can be linked to BitBucket with the GIT option checked, you may well be in luck. Since both Flare and BitBucket have free trials, you may well be able to prove things one way or the other.
Assuming they do work together, running Flare in a GIT environment is a straightforward as any single-source editing software. You do have to accept that a degree of RTFM is a good policy. (Read The Flaming Manual!). You can certainly set Flare up to check out files being worked on by an individual author.
After that, you will find a world of time saving techniques using things like Conditional Text where text will only appear under specific conditions. Text which is repeated in many topics can become a "Snippet", so aside from not having to copy/paste, etc., if changes are required, you only have to change it in one place.
In our own case, we have two main products. But each product has a Windows and Mac Version. Consequently a great deal of text content is the same between the two versions, and only screen shots and keystrokes differ. In terms of product there is around 50% common to both.
The net result for us is that one source Topic shows all versions, but compiles correctly for each version.
And FWIW, we have 1,740 Topics and 721 images.
Assuming they do work together, running Flare in a GIT environment is a straightforward as any single-source editing software. You do have to accept that a degree of RTFM is a good policy. (Read The Flaming Manual!). You can certainly set Flare up to check out files being worked on by an individual author.
After that, you will find a world of time saving techniques using things like Conditional Text where text will only appear under specific conditions. Text which is repeated in many topics can become a "Snippet", so aside from not having to copy/paste, etc., if changes are required, you only have to change it in one place.
In our own case, we have two main products. But each product has a Windows and Mac Version. Consequently a great deal of text content is the same between the two versions, and only screen shots and keystrokes differ. In terms of product there is around 50% common to both.
The net result for us is that one source Topic shows all versions, but compiles correctly for each version.
And FWIW, we have 1,740 Topics and 721 images.
George Bell
Techno-Vision Systems Ltd., U.K.
Techno-Vision Systems Ltd., U.K.