-
2017.11.21 14:50 "Re: [Tiff] Write a tif with JPG compression", by Emmanuel Cosnard
-
2017.11.21 15:48 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
-
2017.11.21 19:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
-
2017.11.21 23:15 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
- 2017.11.22 00:02 "Re: [Tiff] Write a tif with JPG compression", by Lee Howard
-
2017.11.22 17:24 "Re: [Tiff] Write a tif with JPG compression", by Larry Gritz
- 2017.11.22 17:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
-
2017.11.22 18:27 "Re: [Tiff] Write a tif with JPG compression", by Roger Leigh
- 2017.11.22 19:28 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
- 2017.11.22 23:12 "Re: [Tiff] Write a tif with JPG compression", by Roger Leigh
- 2017.11.23 09:10 "[Tiff] [PATCH] CI improvements for GitLab and GitHub", by Roger Leigh
- 2017.11.22 07:00 "Re: [Tiff] Write a tif with JPG compression", by Even Rouault
-
2017.11.21 23:15 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
-
2017.11.21 19:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
-
2017.11.21 15:48 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
- 2017.11.21 15:08 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
2017.11.30 08:58 "Re: [Tiff] Switching to gitlab ?", by Even Rouault
On jeudi 23 novembre 2017 11:37:11 CET Even Rouault wrote:
On mercredi 22 novembre 2017 17:58:52 CET Bob Friesenhahn wrote:
I have used the two attached files to import the CVS history into git. I've pushed this here:
https://gitlab.com/libtiff/libtiff
This looks very nice. I think that we need to hear an opinion from Even Rouault since he is the most active recent committer. A switch needs to be reasonably-well synchronized.
I'm fine with the gitlab solution. Regarding tickets, we can remain with the bugzilla solution for now. This will not change much things since there was no tight SCM vs ticket database connections. But at least we could put an URL to a gitlab changeset in the ticket, which was not really possible with CVS without web interface.
The web content is currently pulled from the CVS repository by polling. If we switch to a Git repository, then the two sites hosting web sites will need to change their polling scripts to using Git. I am able to take care of the simplesystems.org site.
I just got admin rights on libtiff.maptools.org so I could take care of using the gitlab repo as the master repo to clone now to refresh the HTML pages
Any contributors who expect to remain active would need to get Github accounts and be assigned as maintainers for this Github project.
You meant gitlab I suppose
We will need to update the HTML pages to reflect the change.
And I suppose the "$Id: tif_close.c,v 1.21 2016-01-23 21:20:34 erouault Exp $" thing at top of source files which was refreshed at each CVS commit should now be dropped (unless there's something equivalent on the git side ?)
Agreed that at least foks listed as past and present maintainers on http:// www.simplesystems.org/libtiff/ should be granted admin rights on the gitlab repo if they request it (I do :-))
Have we acted the switch to the gitlab repository? I'm +1
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com