[gphoto-devel] gphoto SF.net services summary

[Hans U. N. <gp...@n-...>]

Hi,

the two services which triggered the need to move away from SF.net right
now are related to the source code:

  * SVN source code repository

    To be replaced by git repos on http://github.com/gphoto/

    This requires all current committers to get themselves
    a github account and then one of us admins to enter those
    github accounts into the list of people allowed to commit
    to the repo.

    Stupid me forgot to ask the current committers for the names
    of their github accounts in the last mail, so I guess that
    will be an extra round of Q&A by mail.

    I'm working on the SVN->git conversion right now.

  * Release tarball hosting

    Reconstructing the partially untagged releases of the past
    few years will take a bit of work, but should be feasible
    with `git bisect`.

    This can easily be done after switching over to using github.

However, we are using more services on SF.net, and I have taken a look
around on SF.net to find out which services should or could be migrated
elsewhere.

  * Web hosting for http://gphoto.org/
    Contains a lot of content. Could probably be moved to
    github pages, as it does not contain real dynamic elements
    in PHP. Or does it?
    Could also be changed to jekyll-bootstrap or something similar
    for a more 21st century layout, but that is a lot more work
    than just putting the existing HTML files into a git repo.

  * "Wiki"
    Apparently contains only a list of the maintainers, i.e it could
    be scrapped without any loss.

  * "Mediawiki"
    Contains about three pages of content on file formats,
    but that does not appear to be very much to migrate to any of
    e.g. the github Wikis.

  * Ticket trackers:

    * Feature requests
    * Patches
    * Bugs
    * Support Requests

    After moving the source code over to github, using github's
    issue tracker for bugs and feature requests is the obvious choice.

    For Patches, github's issue tracker and pull requests should
    do the job in a much improved way.

    As to Support Requests... to be determined. github issue tracker?

  * Mailing Lists @lists.sourceforge.net

    Notification from the ticket trackers:

    * gphoto-bugs
    * gphoto-features
    * gphoto-patches

    Notifications from the source code repository:

    * gphoto-cvs

    Communication among developers and users:
    * gphoto-devel
    * gphoto-user

    Updates for translation files:
    * gphoto-translation

    The notification mails for bugs, features and patches probably
    are obsolete when using the github features instead of SF.net
    tickets.

    The commit notification ML could be fed from github, or replaced
    by the github feature to "watch" the github repos you are
    interested in.

    The gphoto-devel and gphoto-user mailing lists should be kept
    around. As they carry no manipulation critical function like
    a code repo, we could keep them hosted at SF.net. Alternatively,
    we could find a service somewhere to host them and change their
    mail addresses to <*@gphoto.org>.

    A similar argument is to be made for gphoto-translation.

    Two issues to solve in case of moving the mailing lists
    elsewhere:

    * Can we move the list archives as well?

    * Are there issues with taking over subscriber lists
      to the new host?

    * Can there be (temporary) mail redirections?

  * Anything I have overlooked: What?

My personal preference for keeping stuff and moving stuff for the next
few weeks would be:

  * github git code repos for the source code

  * Host http://gphoto.org/ on github pages

  * github issue tracker

  * github wikis

  * phase out gphoto-{bugs,features,patches} as we phase out
    the SF.net ticket system

  * keep gphoto-devel and gphoto-user MLs on SF.net
    (using these does not require an SF.net account)

  * keep gphoto-translation ML on SF.net
    (using these does not require an SF.net account)

This would mean that all developers only need a github account for
working on gphoto (no SF.net account). Only project and mailing list
admins need access to SF.net.

Uli