How to Collaborate on SourceForge

ErichSt

unread,

May 22, 2013, 8:16:57 AM5/22/13

to

Do we have a summary how one would go and collaborate on ooRexx on SourceForge?

Which Version Control client is suggested?
Any etiquette to follow?
Write access needed?
Other pitfalls to avoid?

Mark Miesfeld

unread,

May 22, 2013, 11:11:57 AM5/22/13

to

On May 22, 5:16 am, ErichSt <erich.steinbo...@gmail.com> wrote:

> Do we have a summary how one would go and collaborate on ooRexx on SourceForge?

Here is a sort of summary.

Register as a SourceForge user.

Subscribe to either or both of the ooRexx developers list and ooRexx
users list.

https://sourceforge.net/p/oorexx/mailman/?source=navbar

If you want to have an idea of what is happening on the project you
can subscribe to some of the other mailing lists which are mostly
notification lists. For instance, the svn mailing list sends out an e-
mail notice for each commit to the source code. The bugs mailing list
sends out a notice of each bug update, etc..

Participate in the mailing list discussions and initiate your own
discussions.

> Which Version Control client is suggested?

You have to use subversion. I personally would use a command line
client. But a lot of people like Tortoise SVN.

> Any etiquette to follow?

Common usenet etiquette.

> Write access needed?

Only a committer has write access. Any one has read access of all the
code.

The best way to become a committer is to participate in the mailing
list discussions and to contribute patches. If you submit patches
that are accepted, at some point one of the current committers is
likely to nominate you to committer status.

> Other pitfalls to avoid?

One pitfall is thinking that if you aren't skilled in C / C++ you can
not contribute. Help with the documentation and with writing test
cases is something any one can do and that help would be very much
appreciated.

Not really pitfalls, just a couple of other things.

Ask these questions on either the ooRexx developer's mailing list or
the ooRexx user's mailing list. For instance if you want to check out
the source code and don't know where to start, ask on one of the
mailing lists.

The project also has some "forums." I personally find them cumbersome
to use, so I suggest using the mailing lists rather than the forums.

--
Mark Miesfeld

w.david...@gmail.com

unread,

May 22, 2013, 11:16:12 AM5/22/13

to

Erichst -

The ooRexx development team welcomes all who want to contribute to the project. We need all the help we can get.

My first suggestion for introducing yourself is to jion the oorexx-devel mailing list. Most of our conversation happen here. There are other lists that you may want to join later. The conversation can be sporadic but this is the best place to get going.

Although we have both a CVS and a Subversion repository the only active one is the Subversion repository. The CVS repository is only historical and no longer used.

Of course you will need a SourceForge userid to join anything but that is easy.

We need help in a number of areas so pick an interest and go to work. If you have fixes to offer submit them and the team will evaluate them. Once we get comfortable with you and you are ready we can promote you to a commiter to the SVN repository.

It really is as simple as that.

david Ashley

ErichSt

unread,

May 22, 2013, 5:52:12 PM5/22/13

to

Mark, David, thanks

> Register as a SourceForge user.

Done - I'm registered since a few years

> Subscribe to either or both of the ooRexx developers list and ooRexx users list.

Done - I've subscribed since a few months

> a lot of people like Tortoise SVN

Done - installed since a few hours :-)

I then did a (UI, not Command line) SVN Checkout for http://svn.code.sf.net/p/oorexx/code-0/main
As a warm-up in branches\4.1.3\trunk\readme I corrected two typos in newinrelease.xml and did an SVN Update.

Is that what it takes? What's next? Will David now see those changes, check whether they're OK and then commit, after which I will then see the changes on SourceForge?

Some more questions:
- How do I supply a comment to SVN what was changed why?

- What XML/SGML Tool is suggested to edit the Docs?

- The SVN Checkout downloads all files with current date/time. Would be nice if they had their actual last modification date/time .. is that possible?

- When editing files is it expected to be careful to keep the file's current line-end - style (either '0A'x Unix-style, or '0D0A'x Window-style)? Are all files generally kept in '0A'x Unix-style?

Thx

Rick McGuire

unread,

May 22, 2013, 6:09:42 PM5/22/13

to

On Wednesday, May 22, 2013 5:52:12 PM UTC-4, ErichSt wrote:
> Mark, David, thanks
>
>
>
> > Register as a SourceForge user.
>
> Done - I'm registered since a few years
>
>
>
> > Subscribe to either or both of the ooRexx developers list and ooRexx users list.
>
> Done - I've subscribed since a few months
>
>
>
> > a lot of people like Tortoise SVN
>
> Done - installed since a few hours :-)
>
>
>
> I then did a (UI, not Command line) SVN Checkout for http://svn.code.sf.net/p/oorexx/code-0/main
>
> As a warm-up in branches\4.1.3\trunk\readme I corrected two typos in newinrelease.xml and did an SVN Update.

SVN update only updates your local version with any changes that have been committed to the master since your last update. A commit operation is necessary to change the master, but you currently only have read-only access since you are not yet a committer.

>
>
>
> Is that what it takes? What's next? Will David now see those changes, check whether they're OK and then commit, after which I will then see the changes on SourceForge?

For now, your only option is to commit patches. You can open a patch here:

https://sourceforge.net/p/oorexx/patches/?source=navbar

Attach a patch file containing your updates. You can generate a patch file by using

svn diff > myupdate.patch

This will generate a file containing updates relative to your current directory location. The committers will then apply the update to the master if it's found acceptable.

>
>
>
> Some more questions:
>
> - How do I supply a comment to SVN what was changed why?
>

That is done at commit time...something you don't have the capability to do yet.

>
>
> - What XML/SGML Tool is suggested to edit the Docs?
>

Just any flat-file editor. I've yet to find a tool that works well without out having undesirable side effects when the file is saved.

>
>
> - The SVN Checkout downloads all files with current date/time. Would be nice if they had their actual last modification date/time .. is that possible?
>
>

Not sure it is.

>
> - When editing files is it expected to be careful to keep the file's current line-end - style (either '0A'x Unix-style, or '0D0A'x Window-style)? Are all files generally kept in '0A'x Unix-style?
>

You need to update your SVN options files to handle the line-ends properly. The options file is located at:

http://svn.code.sf.net/p/oorexx/code-0/svnconfig/config

Once this is done, the files will be checkout out with native line-ends for the recognized file extentions.
>
>
> Thx

Can I suggest you move these sorts of questions to the oorexx developers list? You'll probably get quicker answers that way.

Rick

Swifty

unread,

May 23, 2013, 1:38:06 AM5/23/13

to

On 22/05/2013 16:11, Mark Miesfeld wrote:
> You have to use subversion. I personally would use a command line
> client. But a lot of people like Tortoise SVN.

Talking of Subversion and SVN, I have three textbooks that I'm willing
to post within the UK:

TortoiseSVN 1.7 Beginner's Guide by Lesley Harrison
Pragmatic Version Control Using "Using Subversion"
Version Control with Subversion (O'Reilly)

I bought these when we started using Subversion at work, but then IBM
bribed me to retire 12 months early, so they are almost unused.

--
Steve Swift
http://www.swiftys.org.uk/