gphoto - github migration status

TLDR

github not in production yet. Details are being worked on.

website	status
gphoto.org	running on sourceforge
gphoto.sourceforge.net	the current production site
gphoto.github.io	migrating to Github Pages from custom PHP templates

repository name		github repo production status	svn2git success	build from git repo	doc refers to git	repo importance
svn on SF.net	git on github	github repo production status	svn2git success	build from git repo	doc refers to git	repo importance
website	gphoto.github.io	yes	OK	80%	OK	website
m4	gphoto-m4	testing	OK	OK	OK	essential
libgphoto2	libgphoto2	testing	OK	OK	OK
gphoto2	gphoto2	testing	OK	OK	OK
gphotofs	gphotofs	testing	OK	OK	OK	important
gtkam	gtkam	testing	OK	OK	OK
gphoto2-manual	gphoto2-manual	testing	OK	OK	20%
libgphoto2-python	libgphoto2-python	testing	OK	OK	OK	less important
libgphoto2-sharp	libgphoto2-sharp	testing	OK	OK	OK	less important
libgphoto2-java	libgphoto2-java	testing	OK	TBD	OK	outdated
gphoto-suite	gphoto-suite	testing	OK	TBD	TBD	outdated

OK: Work finished. WIP: Work In Progress. TBD: To be done.

github repo production status: Whether you can git clone this repo and work on it. Some repos will still have their history rewritten, and thus are not clonable (no). Some should be finished but are still in testing, and when testing has succeeded, the repo will be marked yes.
svn2git: Whether the automatic conversion from svn to git worked.
build fixes: Whether the build has been fixed to work with the git repos.
doc fixes: Whether the documentation has been fixed to reference git repos.

m4 aka gphoto-m4

Renamed from m4 to gphoto-m4 in order to make it easier for people to fork.
website aka gphoto.github.io

Renamed from website to gphoto.github.io to make github serve the web site.
gphoto2-manual

README files etc. refer to git repos. The actual manual section still refers to SVN, though.
libgphoto2-sharp

Building test programs (*.exe) for testing libgphoto2-sharp.dll is broken. Does not appear to be related to git migration, though.
libgphoto2-java and gphoto-suite

These code bases have aged so much they need serious work to do anything useful again, regardless of whether built from SVN or git repos.

The things we have to do for migrating the gphoto.org source code from subversion repos on sourceforge.net to git repos at github.com.

Pull requests welcome.

Verify all commit messages in the converted repos are valid utf-8 and contain the proper characters. [DONE]
Find and list existing documentation for how to get the sourcecode and how to build it. [DONE]
Add a git tag to all generated git repos at their important branch heads clearly marking this as the point where the automatic SVN conversion stopped. [DONE: svn2git-conversion-done]

Not having these done at the time of the "switchover" incurs a day or two of something approaching a downtime.

Make git clone and building the code work. [DONE]
Make github fork and git clone and building the forked clones work. [DONE]
Document how to get the source code and how to build it.
Add a git tag to all generated git repos at their important branch heads clearly marking this at the point where the builds should work from git clones. [TBD: "github-start"]

Verify git clone and builds works. [DONE]
Update existing documentation (gphoto2-manual, website, etc.)
Forward-port patches from SVN repos where necessary.
Find and document a way to compose and publish code releases.
Get hold of release tarballs and use git bisect to find the git commits they were created from. Then re-create the appropriate tags and github releases.