Alistair Ward
Member
- Location
- Christchurch, New Zealand
I've been reviewing messages in the old Templot Club, and there are several that I feel need to be continued/actioned.
The first one that I think is critical if Templot3 is to go ahead as an open-source project is establishing a version control repository and determining who will have rights to update code in it.
I see that SourceForge supports several flavours of version control: subversion, mercurial or git. At this stage I think it is a done deal in the IT world that git has won (sadly), so I would suggest that git be adopted as the version control system of choice. It's not a simple system to use, but it is very powerful and as a distributed system it is very easy to fork or move to another host if that is ever required.
I've not worked on open-source projects before, but my understanding of the normal workflow is that a small group of people (maintainers) are given read-write access to the repository. Everybody else in the world only has read-only access.
If someone who is not a maintainer wants to make a change to the code, they can submit a "pull request" containing their changes. A maintainer can then review the code, and if it is acceptable, they can then merge the code into the repository. This can potentially be quite a bit of work for the maintainers, but is essential to prevent random vandalism of the code :-(
So the action items from here are:
From looking at the old messages, my immediate thoughts for possible maintainers (beyond Martin of course) would be Graeme in Bangkok and Andrew Hunt who appear to be people that have taken a serious interest in the code recently. I would also happily offer myself as well, but I am very new here so I wouldn't expect to be accepted immediately
Regards,
Alistair W.
The first one that I think is critical if Templot3 is to go ahead as an open-source project is establishing a version control repository and determining who will have rights to update code in it.
I see that SourceForge supports several flavours of version control: subversion, mercurial or git. At this stage I think it is a done deal in the IT world that git has won (sadly), so I would suggest that git be adopted as the version control system of choice. It's not a simple system to use, but it is very powerful and as a distributed system it is very easy to fork or move to another host if that is ever required.
I've not worked on open-source projects before, but my understanding of the normal workflow is that a small group of people (maintainers) are given read-write access to the repository. Everybody else in the world only has read-only access.
If someone who is not a maintainer wants to make a change to the code, they can submit a "pull request" containing their changes. A maintainer can then review the code, and if it is acceptable, they can then merge the code into the repository. This can potentially be quite a bit of work for the maintainers, but is essential to prevent random vandalism of the code :-(
So the action items from here are:
- create a git repository in SourceForge and populate it with the current Templot3 code
- nominate maintainers, and provide them with developer access to the repository.
From looking at the old messages, my immediate thoughts for possible maintainers (beyond Martin of course) would be Graeme in Bangkok and Andrew Hunt who appear to be people that have taken a serious interest in the code recently. I would also happily offer myself as well, but I am very new here so I wouldn't expect to be accepted immediately
Regards,
Alistair W.
message ref: 447