[Gvsig_english] About contributing to gvSIG code (was Re: gvSIG 1.9.1)

[Jorge Gaspar Sanz Salinas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29/03/10 23:37, Benjamin Ducke wrote:
...
> On April 1st, I will start feeding my modifications for
> gvSIG OADE back into the main SVN, most important bug
> fixes first. This will start the re-consolidation of the
> two code lines. Let's see how it goes. If there are no
> major issues, then version 1.9.1 will be a common code
> base again. If not, differences will be minor and it
> will be largely a matter of personal preference whether
> you go with the official gvSIG, OADE or any of the other
> distributions that may be around by then. I don't think
> choice has ever been a bad thing for customers (users).
>


Ben,

First at all, we are really thankful about having you on board working
for a better release of gvSIG.

Before you start submitting code we need to ensure everything is clear
between both parts (project and you as contributor).

Well, before anything take in account that next weeks we will start
migration of Trac/SVN to OSOR.eu forge so take care about tickets
because they have to be correctly filled in order to avoid errors
during the migration.

Some days ago Manuel Madrid sent you a basic procedure to contribute
on the gvSIG SVN repository. We think this procedure is quite easy and
"light" but it let us to have control about what is being changed on
the repository. In fact is lighter than the procedure we imposed to
ourselves to change any core code, as some developers can tell you on
this list.

As that procedure was sent off-list, let me copy it again here:

"""
In this case, if you agree we would work this way:

1. You would create a ticket for each change including a comment
regarding source code affected parts.
2. We would study the change and if we accept it, we would assign the
ticket to you. This will mean you can do the change.
3. You would do the change following some basic rules [1]. The most
important thing is to link ticket and commit Id's bi-directionally so
we can undo a change if we need to.
4. We would validate the bug fix in the next build.

Of course and, as I said, in the future we'll work in a more agile way.
"""

In essence, we ask you to fill a ticket with any change in order to be
able to link it with the revision number on the commit, and before you
do it, we want to let the person in charge of the module involved to
review yo confirm if your proposal it's acceptable or not.

This procedure needs a review in the near future for a more general
public. But as we said, you can start with it when you think is more
appropiate.

Best regards

- -- 
Jorge Gaspar Sanz Salinas
gvSIG Team
Technical Steering Committee Manager
http://www.gvsig.org
http://www.gvsig.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLsfCHAAoJEAOYD75lvHdB7CsH+wW04i6t6DGFNE5CMoj/tpzc
8YCI/1b2ofv0SEcPbk1z8zyfikG4vN/YiaRKszSXVgN5nkFSmpFkZl58crvepKSg
qYHwQLRMF6tdAsAzwcIQXRuOZFaKSs/l8ZcsNCATJoSfPnNypBkm1HW/fqsBv1Mc
0wjwBTGXOpQwgcFj53TnMkc1TWcLYeR4Ox3fRPUkH3ruof/VlxbwEzlW8t/OetTI
v1xKdlXBLocJlOBYMHjfc9MwBXuDiIooIegLjSLQ4uP9eAnEK72qQybS7HvvePGy
8pTPta7RD0NhOzNK0zNjjttYSw7Cnf41w/WVn4oLhF5cnEO18HXzhSexYjo+WYE=
=dx7Y
-----END PGP SIGNATURE-----