Aaron is correct.
You probably need to start with a document that covers your initial
statement of direction and intent. I saw Nathans table structures but
didn't really know if he was trying to reinvent the wheel for
checkout/checkin or not. This may or may not be overkill depending on
the intention.
I am happy to provide input and will most likely donate any code that we
create to the project once we have it working here internally.
So here's an example overview statement of direction:
Overview
To allow iSeries source code to be managed via the Subversion source
code repository mechanism. Along with that, allow source members to be
checked out, edited, compiled and committed from the green screen via
PDM/SEU. Also allow source members to be checked out, edited, compiled
and committed from Windows Explorer, RDI, WDSC, RDP, Eclipse.
This was my initial statement of direction but will probably change
because I am thinking we will now support RDI or other PC file editing
only :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 8
date: Fri, 28 May 2010 10:05:53 -0400
from: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
subject: Re: Subversion and RPG source change management
We are still in the planning stage, and it is all here on this list. I
have created a source forge project "SVN Clinet for i", but we haven't
quite moved there yet. There is a mailing list for the project,
svnci-developers@xxxxxxxxxxxxxxxxxxxxx that exists but the discussion is
still here until the we actually move the discussion.
Let me know your source forge id and I will add you to the project.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
midrange.com
