Re: GUI interface to Subversion via web browser?

[Justin MASSIOT | Zentek]

Hello,

You can find screen captures of the three previously mentioned tools just
here:
https://superuser.com/questions/559261/looking-for-a-web-based-svn-code-browser-alternative-for-trac-anything-like-g
Some ticket trackers like Redmine also have Subversion browsing
capabilities.

If you're willing to manage you repositories as well as browsing them, I
would recommend having a look at:
* SCM-Manager: https://scm-manager.org/docs/3.1.x/en/user/repo/code/
* RhodeCode: https://rhodecode.com/features
Both are compatible with Subversion, Git and Mercurial backends.

Justin MASSIOT  |  Zentek


On Wed, 22 May 2024 at 10:25, Philippe Andersson  wrote:

> On 22/05/2024 10:06, Bo Berglund wrote:
> > ... I hope this is not totally OT ...
> >
> > I am running an SVN server on an Ubuntu 20.04 LTS system and I have the
> Apache
> > connection so I can access it via its web interface.
> >
> > This works but is *very limited* in functionality, so I am looking for
> some kind
> > of GUI interface that can be added to my Ubuntu SVN installation and
> gives me
> > functionality to view file revisions, logs etc and also diff revisions
> using the
> > web view.
> >
> > Many years ago (like 20+ years) when I worked at a company using CVS
> there was a
> > web interface which had very useful functions in this regard. It was all
> running
> > on Windows Server.
> >
> > It was named ViewCVS (Python based) and was accessed using a web browser
> towards
> > the CVS server.
> >
> > I have tried to search for something similar for SVN and found WebSVN on
> Github:
> > https://github.com/websvnphp/websvn
> >
> > and:
> >
> > https://websvnphp.github.io/
> >
> > However, I have yet to find any examples on how its displays look or
> work and it
> > also seems to be a rather old project...
> WebSVN is still actively maintained (version 2.8.4 was released 2 months
> ago) and offers the features you're looking for (view files, logs and
> diffs) and more.
>
> I'm not aware of any screenshots, but installing it for evaluation
> purposes is reasonably straightforward.
>
> For small to medium-scale projects, I find it a really helpful addition
> to the Subversion server. For large-scale projects with more than a
> thousand branches or tags, performance will become an issue.
>
> HTH
>
> Ph. A.
>
> --
>
> *Philippe Andersson*
> Unix System Administrator
> IBA Particle Therapy |
> Tel: +32-10-475.983
> Fax: +32-10-487.707
> eMail: p...@iba-group.com
> <http://www.iba-worldwide.com>
>
>
>

Re: PoshSvn – Subversion for PowerShell

[Justin MASSIOT | Zentek]

Awesome work Timofey, bravo and thanks for sharing!

Justin MASSIOT  |  Zentek


On Fri, 17 May 2024 at 09:55, Daniel Sahlberg 
wrote:

> Den fre 17 maj 2024 kl 06:45 skrev Nathan Hartman <
> hartman.nat...@gmail.com>:
>
>> On Thu, May 16, 2024 at 1:50 PM Timofey Zhakov  wrote:
>> >
>> > Hello everyone!
>> >
>> > I like Subversion and use it for my projects.
>> >
>> > PoshSvn is a PowerShell module which provides a tab competition and
>> > typed output for the Subversion cmdlets. I found it useful for
>> > scripting and everyday life.
>> >
>> > For example to get the status of a working copy, you could use the
>> > svn-status cmdlet:
>> >
>> > [[[
>> > PS C:\> svn-status
>> >
>> > Status  Path
>> > --  
>> > M   PoshSvn\CmdLets\SvnAdd.cs
>> > M   PoshSvn\CmdLets\SvnLog.cs
>> > M   PoshSvn\SvnCmdletBase.cs
>> > M   README.md
>> > ]]]
>> >
>> > This is useful for scripting because of typed output. For example:
>> >
>> > [[[
>> > PS C:\> $info = svn-info https://svn.apache.org/repos/asf
>> > PS C:\> $info.Revision
>> > 1917749
>> > PS C:\> $info.LastChangedAuthor
>> > projects_role
>> > ]]]
>> >
>> > Documentation is available at: https://www.poshsvn.com/
>> >
>> > The installation is very easy. Just type `Install-Module PoshSvn` in
>> > the PowerShell command prompt.
>> >
>> > This module is fully free and open source.
>> >
>> > Any kind of feedback would be much appreciated.
>> >
>> > Thanks!
>> >
>> > --
>> > Timofei Zhakov
>>
>>
>> Thanks for sharing!
>>
>> I'm not a Windows user or a PowerShell user so I can't try it out for
>> myself, but I am always glad to hear about new additions to the
>> Subversion ecosystem.
>>
>> If you ever feel like participating in Subversion development, there
>> are plenty of opportunities around here :-)
>>
>> Cheers,
>> Nathan
>>
>
> Dear Timofei,
>
> Very impressive work and I think this is the biggest addition to the
> Subversion ecosystem in may years.
>
> I'm a Windows user although I use PowerShell way to seldom. I will try to
> find time to test this out a little bit in the next few weeks.
>
> I was thinking about adding a link to your project on the Subversion
> website. There is already page for Binary packages[1] and this would make a
> nice addition. (Although, we have previously limited that page to strictly
> Apache Subversion builds and this a different kind of client, so we might
> have to create a new page for "ecosystem" - this should be discussed in the
> dev@ list).
>
> Kind regards,
> Daniel Sahlberg
>
> [1] https://subversion.apache.org/packages.html
>
>

Re: How much is too much data in an svn repository?

[Justin MASSIOT | Zentek]

Hello Sean,

I have not enough experience to answer your question, but I'm very
concerned about large binary files. Whereas I have a more "splitted"
structure of repositories.
I'm following this discussion ;-) Can anyone bring some inputs on this
topic?

Justin MASSIOT  |  Zentek


On Thu, 22 Sept 2022 at 21:59, Sean McBride  wrote:

> Hi all,
>
> Our svn repo is about 110 GB for a full checkout. Larger on the server of
> course, with all history, weighting about 142 GB.
>
> There haven't been any performance issues, it's working great.
>
> But now some users are interested in committing an additional 200 GB of
> mostly large binary files.
>
> I worry about it becoming "too big".  At what point does that happen?
> Terabytes?  Petabytes?  100s of GB?
>
> Thanks,
>
> Sean
>

Re: svn::auto-props and svn:needs-lock

[Justin MASSIOT | Zentek]

Not if the needs-lock attribute is also set by a "svn:auto-props" property,
I suppose.

Justin MASSIOT  |  Zentek


On Thu, 9 Dec 2021 at 11:18, Sebastian Weilhammer <
sebastian.weilham...@madheadgames.com> wrote:

> Is that not what I'm doing by setting svn:auto-props to *= on the child
> node?
>
> On Thu, Dec 9, 2021 at 10:46 AM Justin MASSIOT | Zentek <
> justin.mass...@zentek.fr> wrote:
>
>> By overcharge I meant "define a new property with a value which differs
>> from the one that is inherited", either for svn:auto-props or
>> svn:needs-lock.
>> I'm really not sure it would work, but it's worth the try.
>>
>> Justin MASSIOT  |  Zentek
>>
>>
>> On Thu, 9 Dec 2021 at 10:43, Sebastian Weilhammer <
>> sebastian.weilham...@madheadgames.com> wrote:
>>
>>> Hello Justin,
>>>
>>> So that's the thing, I cannot seem to remove the svn:needs-lock from
>>> svn:auto-props for the node in question and I can't change it's value in
>>> such a way where it will stop adding svn:needs-lock to newly added files.
>>> If that's what you mean by overcharge?
>>>
>>> Essentially setting svn:auto-props to *=, *=svn:needs-lock= or
>>> *=svn:needs-lock does not get this to work.
>>>
>>> On Thu, Dec 9, 2021 at 9:18 AM Justin MASSIOT | Zentek <
>>> justin.mass...@zentek.fr> wrote:
>>>
>>>> Hi Sebastian,
>>>>
>>>> As far as I've understood, since Subversion 1.8 the property
>>>> "svn:auto-props" is automatically inherited.
>>>> Have you tried to overcharge the property at the node you want
>>>> a variation? Not sure but it might take precedence...
>>>>
>>>> Justin MASSIOT  |  Zentek
>>>>
>>>>
>>>> On Wed, 8 Dec 2021 at 23:30, Sebastian Weilhammer <
>>>> sebastian.weilham...@madheadgames.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I'm having trouble with these features.
>>>>>
>>>>> I have a folder on which I have set svn:auto-props to
>>>>> *=svn:needs-lock=*.
>>>>> I have another folder within this folder for which I would like
>>>>> anything inside to not require locks.
>>>>>
>>>>> It seems, I have no way of removing auto setting the needs lock
>>>>> property on newly added files?
>>>>>
>>>>> This makes sense I guess, considering svn:needs-lock doesn't require a
>>>>> value, just needs to be set.
>>>>> Feels like the needs-lock requiring either 0 or 1 as a value would
>>>>> make this customizable?
>>>>>
>>>>> Am I correct in my assumption? Or is there a way of handling this
>>>>> specific scenario gracefully?
>>>>>
>>>>> Best,
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> --
>>>
>>> *Sebastian Weilhammer*
>>>
>>> Technical Director
>>>
>>> madheadgames.com <http://www.madheadgames.com/>
>>>
>>> <https://www.facebook.com/madheadgames>
>>> <https://www.instagram.com/madheadgames/>
>>> <https://www.linkedin.com/company/mad-head-games>
>>> <https://twitter.com/madheadgames>
>>>
>>
>
> --
>
> *Sebastian Weilhammer*
>
> Technical Director
>
> madheadgames.com <http://www.madheadgames.com/>
>
> <https://www.facebook.com/madheadgames>
> <https://www.instagram.com/madheadgames/>
> <https://www.linkedin.com/company/mad-head-games>
> <https://twitter.com/madheadgames>
>

Re: svn::auto-props and svn:needs-lock

[Justin MASSIOT | Zentek]

By overcharge I meant "define a new property with a value which differs
from the one that is inherited", either for svn:auto-props or
svn:needs-lock.
I'm really not sure it would work, but it's worth the try.

Justin MASSIOT  |  Zentek


On Thu, 9 Dec 2021 at 10:43, Sebastian Weilhammer <
sebastian.weilham...@madheadgames.com> wrote:

> Hello Justin,
>
> So that's the thing, I cannot seem to remove the svn:needs-lock from
> svn:auto-props for the node in question and I can't change it's value in
> such a way where it will stop adding svn:needs-lock to newly added files.
> If that's what you mean by overcharge?
>
> Essentially setting svn:auto-props to *=, *=svn:needs-lock= or
> *=svn:needs-lock does not get this to work.
>
> On Thu, Dec 9, 2021 at 9:18 AM Justin MASSIOT | Zentek <
> justin.mass...@zentek.fr> wrote:
>
>> Hi Sebastian,
>>
>> As far as I've understood, since Subversion 1.8 the property
>> "svn:auto-props" is automatically inherited.
>> Have you tried to overcharge the property at the node you want
>> a variation? Not sure but it might take precedence...
>>
>> Justin MASSIOT  |  Zentek
>>
>>
>> On Wed, 8 Dec 2021 at 23:30, Sebastian Weilhammer <
>> sebastian.weilham...@madheadgames.com> wrote:
>>
>>> Hello,
>>>
>>> I'm having trouble with these features.
>>>
>>> I have a folder on which I have set svn:auto-props to *=svn:needs-lock=*.
>>> I have another folder within this folder for which I would like anything
>>> inside to not require locks.
>>>
>>> It seems, I have no way of removing auto setting the needs lock
>>> property on newly added files?
>>>
>>> This makes sense I guess, considering svn:needs-lock doesn't require a
>>> value, just needs to be set.
>>> Feels like the needs-lock requiring either 0 or 1 as a value would make
>>> this customizable?
>>>
>>> Am I correct in my assumption? Or is there a way of handling this
>>> specific scenario gracefully?
>>>
>>> Best,
>>>
>>> Sebastian
>>>
>>>
>>>
>>
>
> --
>
> *Sebastian Weilhammer*
>
> Technical Director
>
> madheadgames.com <http://www.madheadgames.com/>
>
> <https://www.facebook.com/madheadgames>
> <https://www.instagram.com/madheadgames/>
> <https://www.linkedin.com/company/mad-head-games>
> <https://twitter.com/madheadgames>
>

Re: svn::auto-props and svn:needs-lock

[Justin MASSIOT | Zentek]

Hi Sebastian,

As far as I've understood, since Subversion 1.8 the property
"svn:auto-props" is automatically inherited.
Have you tried to overcharge the property at the node you want a variation?
Not sure but it might take precedence...

Justin MASSIOT  |  Zentek


On Wed, 8 Dec 2021 at 23:30, Sebastian Weilhammer <
sebastian.weilham...@madheadgames.com> wrote:

> Hello,
>
> I'm having trouble with these features.
>
> I have a folder on which I have set svn:auto-props to *=svn:needs-lock=*.
> I have another folder within this folder for which I would like anything
> inside to not require locks.
>
> It seems, I have no way of removing auto setting the needs lock
> property on newly added files?
>
> This makes sense I guess, considering svn:needs-lock doesn't require a
> value, just needs to be set.
> Feels like the needs-lock requiring either 0 or 1 as a value would make
> this customizable?
>
> Am I correct in my assumption? Or is there a way of handling this specific
> scenario gracefully?
>
> Best,
>
> Sebastian
>
>
>

Re: A project I've been working on

[Justin MASSIOT | Zentek]

Hi Robert,

Interesting initiative.
What is the "two copies of everything in a checkout" problem you are
talking about?

Justin


On Sat, 13 Nov 2021 at 01:54, Robert Hickman <
robert.e.hick...@googlemail.com> wrote:

> Hi people,
>
> I've been working on a 'subversion replacement' for the last 5 ish
> years called 'simple http file sync' (shttpfs), a centralized version
> control system for binary files.
>
> SHTTPFS was created to manage changes to a lot of binary image and
> video files across multiple computers. The nature of my own data is it
> is primarily added to and very rarely changed. i.e. video is edited
> 'non destructively', and a new video is rendered. I created shttpfs to
> solve subversion's 'two copies of everything in a checkout' problem,
> which was causing data bloat to an extent that made it completely
> unusable. Nothing else worked reliably, or had the required features
> (simple design, atomic commits, arbitrary partial checkouts, good
> command line interface, stores version history on a central server).
>
> https://github.com/robehickman/simple-http-file-sync
>

Re: Current project status

[Justin MASSIOT | Zentek]

TortoiseSVN is stable and mature, so its development status is slow :-)
But I mostly agree with Mark, using SVN is better than nothing after all.
And because it's mature, it's unlikely that you find a bug that is critical
for your everyday use...

Justin MASSIOT  |  Zentek


On Thu, 28 Oct 2021 at 15:43, Mark Phippard  wrote:

> On Thu, Oct 28, 2021 at 9:26 AM Luke Mauldin 
> wrote:
> >
> > Is the SVN repository still in use or was it transitioned to something
> else?
> > The primary users of this SVN repo will be engineers who are not
> software developers so I think the less complex nature of SVN compared to
> Git could be a definite advantage.  However, I am concerned about the
> long-term viability of the SVN project because I would like the repo to
> still be usable by in 5-8 years.  Just looking at the development mailing
> lists, it looks like almost all development has stopped on Subversion which
> is concerning to me.
>
> IMO, this should not be a big concern. Subversion development is slow
> because the project is mature and stable. But for example, there was
> some recent discussion and activity about making even more
> improvements to handling of large binary files (your use case):
>
> https://mail-archives.apache.org/mod_mbox/subversion-dev/202107.mbox/%3c874kcf6xin@red-bean.com%3e
>   I think this is an example of the type of improvement that will come
> to this project in the coming years, but there are only so many of
> these refinements left to make. I do not think any of the really big
> problems, like how renames are handled, are likely ever to be solved.
>
> Ultimately what is the alternative? Not use version control at all? If
> some better alternative emerges in the next 5-8 years it will almost
> certainly provide a migration path for SVN repositories. You are
> probably going to want to use a GUI client like TortoiseSVN. I have
> not followed that recently but it is usually pretty active and there
> is always room to make significant improvements in GUI clients that do
> not require any changes in the core SVN API as most of them are just
> about optimizing workflows.
>
> Mark
>

Re: Current project status

[Justin MASSIOT | Zentek]

Luke,

If the 3D models are "source" files, then I personally approve to put those
files into a Subversion repo. That's what I do everyday with Electronic
engineering CAD files.
By the way, don't forget you may not be able to "diff" between two versions
of a file. If not, you lose one the main strength of a Version control
system: doing even a small rollback may become a pain... Plus if you can't
diff, you probably can't merge either! I encourage you to use locks to
avoid any form of conflicts. The "needs-lock" property can be useful.

As for the project status, I don't know anything but I would be curious to
get the developers' point of view.

Justin MASSIOT  |  Zentek


On Thu, 28 Oct 2021 at 00:47, Luke Mauldin  wrote:

> Let me clarify. The binaries can be unity 3d models or other engineering
> assets. They are not compiled code.
>
> > On Oct 27, 2021, at 5:42 PM, Nico Kadel-Garcia  wrote:
> >
> > On Wed, Oct 27, 2021 at 6:31 PM Luke Mauldin 
> wrote:
> >>
> >> We are considering using Subversion for a project with large binary
> files since it seems to have some strengths in that area compared to the
> alternatives. But now that the Apache Software Foundation and most other
> projects such LLVM and FreeBSD have migrated away from Subversion, what
> does the future of Subversion look like? Is it still being actively worked
> on? Is anyone sponsoring it?
> >
> > For me, subversion still has uses by compelling centralized change
> > tracking, and by permitting checkouts of very small directories from a
> > master repo or a designated tag.
> >
> > Large binaries. just don't put those in source control. Put those
> > in software packaging.
>

Re: SVN: PCSWMM Use

[Justin MASSIOT | Zentek]

Hi Jason!

David is right, I don't know PCSWMM either and you didn't provide any
information about the *file format* used/generated by this software.
And I second what David says: the way to go is to "version control" the
source files ; we don't care about output files much because generally we
don't want to put them under version control, since we are able to
re-generate all of them from the source files.

If your *source* files are in binary format, then you're in the same
situation as mine: I work everyday with binary files of ~10Mo and
Subversion really works well for that. If you're interested I wrote a blog
article discussing the use of SVN or Git in the Electronic/Mechanical
engineering context
<https://gotomation.info/2020/01/svn-or-git-with-solidworks/#which-one-is-good-for-solidworks>
(CAD files).
Unfortunately, with binary files you will generally miss the "diff" feature
which David talked about. Unless your software supports a "file comparison"
feature! Example: Altium Designer (electronic CAD)
<https://gotomation.info/2019/02/file-comparison-altium-designer/#with-tortoisesvn-from-the-windows-explorer>
Even MS Office files can be diff'ed quite easily
<https://gotomation.info/2019/01/svn-version-control-office-documents/#difference-between-two-versions-of-a-file>
;-)

Hope it helps.

Justin MASSIOT  |  Zentek


On Thu, 9 Sept 2021 at 23:29, David Chapman  wrote:

> On 9/9/2021 1:53 PM, Jason Kimmet wrote:
>
> Subversion Users,
>
> We are working on a large stormwater modeling program where we will be
> keeping track of a lot of PCSWMM file type models. We are exploring version
> management options and have come across the SVN community. I understand
> this is great for text-style files, however, I would like to know if you
> have seen users utilize this for engineering plans such as PCSWMM?
>
> Many version control systems, Subversion included, work best when the new
> version of a file looks much the same as the previous version.  Otherwise
> you could be storing multiple full versions of the files.
>
> Some features of Subversion (like "show lines that changed") aren't
> available for binary files, but if the changes in a binary file are limited
> to specific sections, you still get space-saving benefits in the
> repository; see http://help.collab.net/index.jsp?topic=/faq/svnbinary.html
> and https://svnbook.red-bean.com/en/1.7/svn.forcvs.binary-and-trans.html
> (both links are old, but binary file handling shouldn't be worse now than
> then).
>
> A quick search didn't tell me anything about the PCSWMM format; how much
> of a file changes between model runs?  Is it text or binary?  Are the files
> very large (gigabytes or more)?  Are they inputs to software, or outputs?
> Generally it is assumed that output files can be recreated given the full
> input configuration, so program outputs are often left out of the
> repository.
> --
>
> David Chapman  dcchap...@acm.org
> Chapman Consulting -- San Jose, CA
> EDA Software Developer, Expert Witness
> www.chapman-consulting-sj.com
> 2018-2019 Chair, IEEE Consultants' Network of Silicon Valley
>
>

Re: SVN hook

[Justin MASSIOT | Zentek]

Thanks Stefan, I thought I've seen that feature in the past but I've been
unable to find the documentation.
That's a pity there isn't an up-to-date documentation for the latest SVN
releases, apart from the release notes... (or, is there any?)

Justin MASSIOT  |  Zentek


On Wed, 25 Aug 2021 at 13:35, Stefan Sperling  wrote:

> On Wed, Aug 25, 2021 at 09:32:04AM +0200, Justin MASSIOT | Zentek wrote:
> > * As for the "can do / can't do", the standard way would be to enforce
> > "path-based
> > authorization
> > <
> https://svnbook.red-bean.com/en/1.8/svn.serverconfig.pathbasedauthz.html
> >",
> > but it isn't flexible at all because it doesn't support wildcards.
>
> Good news! Path-based authz does support wildcards as of 1.10.0:
> http://subversion.apache.org/docs/release-notes/1.10.html#authzperf
>

Re: SVN hook

[Justin MASSIOT | Zentek]

Hi Philipp,

Not an expert either but from what I know, what you expect seems to be
possible.
I think the best way for you to learn about hooks - apart from the official
doc <https://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html> -
is to look at the templates created by default when you create a repo
("svnadmin create"). You can also find some examples in the SVN repo:
https://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/
https://svn.apache.org/viewvc/subversion/trunk/contrib/hook-scripts/

In your case, the way to go seems to be a *pre-commit* hook.
* For the commit message restriction, look at the examples.
* As for the "can do / can't do", the standard way would be to enforce
"path-based
authorization
<https://svnbook.red-bean.com/en/1.8/svn.serverconfig.pathbasedauthz.html>",
but it isn't flexible at all because it doesn't support wildcards. I would
personally recommend the use of "svnperms
<http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/>"
which should do what you want: advanced path-based control (with regular
expression support).

I have a kind of "framework for hooks" hosted on GitHub
<https://github.com/justinmassiot/svnhooks>, this may help as an example.

Justin MASSIOT  |  Zentek


On Wed, 25 Aug 2021 at 07:36, Philipp Mueller 
wrote:

> Hello,
>
> I´m new to this topic and I have quite a hard time getting into
> programming hooks for my problem. I need a hook which can distinguish
> between three different user groups:
>
> Group A: can do anything (delete tags and trunks, commit without comment)
>
> Group B: can commit to tags and delete tags/branches; CANNOT delete trunks
> and CANNOT commit without comment
>
> Group C: can commit to tags; CANNOT change or delete anything
>
> Is there any way to do that?
>
>
> I am very grateful for you help !
>
> Greetings
>
> Philipp from Germany
>
>

Cheers from MSOfficeSVN

[Justin MASSIOT | Zentek]

Hello everyone!

I wanted to write you a few words just to say that we, Koki YAMAMOTO and I,
have dusted off the MSOfficeSVN project
. That's neither a revival nor
a reboot because the source code is still genuine, nevertheless the latest
released version  -which
dates back from 2013- is still current and works with today's working
environments: Windows 10, 64-bit version of MS Office 2019 and
Subversion/TortoiseSVN 1.14. Good news: the general documentation has been
updated a bit.
If you're interested in versioning MS Office documents through SVN, be sure
to check MSOfficeSVN !
--
MSOfficeSVN is a project originated by Koki YAMAMOTO -based on works
from Osamu OKANO and Kazuyuki NAGAMORI- in order to manage MS Office
documents under Subversion right from the MS Office interface. Customizable
keyboard shortcuts are also available! It comes as a package of three
separated add-ins, corresponding to Excel, PowerPoint and Word. English and
Japanese languages are available, but I'm not able to maintain the Japanese
version by myself :-(
It's mainly written in Visual Basic and is based on TortoiseSVN (command
line calls) and SubWCRev (through its COM interface), thus it's a
Windows-only piece of software. It has been managed through Google Code
, then SourceForge
 and now GitHub
. The project is largely
documented through inline comments, plus some pages gathered into a
dedicated wiki for developers
, even if: (1) it's mainly
in Japanese, (2) it was automatically imported from Google Code (some
format issues still exist).
Finally, it's Open Source software, distributed under the GNU GPL v2. As
we're open to further contributions, feel free to fork the code and create
pull requests ;-) Contributions to the wiki are also welcome.

I think Subversion could serve (almost) every domain, far beyond source
code management. Don't you?
Cheers.
*Justin MASSIOT* +33 6 44 66 94 14
 Zentek  zentek.fr