dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Hi all,

That error message means you are not authorised to commit code to the
repository. Only a selected team of dhis core developers can do that
directly.

Developers that are not members of the core team have read only access to
the repo, as it says in the error message. That means they can make a local
branch ("download and update the code"), but not commit code directly back
to the central trunk repo. However, to share your work you can send it as a
patch (work directive) to the dhis core developers (for now I suggest to
Lars Helge, but we need better routines soon) and they will revise your code
before one of them merges it into the trunk. This way you will also get
feedback and suggestions from experiemced developers on how to improve you
code or to better make use of the dhis2 architecture, available support
modules etc.

When a new developer's code style and quality have been approved by the core
team you will be invited to join the core team and get commit privileges to
the trunk directly. For now you and other aspiring dhis2 developers that are
not members of the core team must work on local branches of trunk and
produce patches (work directives) that you e-mail to the core developers, I
suggest to Lars Helge.

Please follow these guidelines on how to make a patch from a local branch:
http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html#merging-your-work-into-the-parent-branch

A short version is:
$ bzr send -o mycode.patch
and then e-mail the file mycode.patch to core team with explanations on the
changes you have made to the trunk.

These procedures are necessary to maintain a certain stability and
predictability on the quality of the trunk and is very common is most open
source projects. Our developer base is quickly growing which is great, but
before we know the new developer we need some measures to secure the code
base. I hope you all understand this.

On a related note I think it is necessary that we break up the trunk repo
into smaller pieces, e.g. separating out local modules to make commits more
flexible and open to local teams to manage. The security procedures above
are not meant to stop new initiaves and developers or to centrally control
all local development activities. Local teams should be able to control
their local repos and not wait for a global team to revise and accept
changes so by splitting up trunk we can achieve this. Making sure local and
core modules are compatible and build together at all time is of course
still of outmost importance and should be the reponsibility of the
committers.

best regards,
Ola Hodne Titlestad
HISP
University of Oslo


On Tue, Mar 31, 2009 at 8:00 AM, Chau Thu Tran
<tran.hispvietnam@xxxxxxxxx>wrote:

> Dear all,
>
> Please help me ! I can't commit source to server by Bazar. Message error:
>
> bzr: ERROR: Cannot lock
> LockDir(lp-46125968:///~dhis2-devs-core/dhis2/trunk/.bzr/branchlock):
> Transport operation not possible: readonly transport
>
> Chau Thu Tran
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> More help   : https://help.launchpad.net/ListHelp
>
>