Atlassian Stash delivers a central, secure solution for creating and managing distributed Git repositories on your own servers. It has an easy-to-use interface for adding users and groups and creating and managing repositories, and a Project Structure for logically grouping your repositories. Installed on your own network, administrators have full control over how Stash fits into their environment. It supports Atlassian’s plugin framework plus a full, open REST API for customized integrations. Key features include simple administration, easy permissions around Git repositories, LDAP (Active Directory) integration, JIRA issue tracker integration, cloning, and more.
YUMRepoManager is a YUM configuration manager. It allows users to easily manage repository configurations, use most of YUM's options, enable and disable YUM plugins, and edit configuration files. It supports drag-and-drop of .repo files from and to your file manager, the option to change the createrepo arguments, and creation of a local repository from a directory which contains .rpm files or a YUM cache in a directory specified by the user. When finished, the YUM cache will be linked to the place where the repository has been created, unifying the YUM cache into a single folder, so that the packages installed after this point will be placed in this new path instead of the YUM cache.
STB microservices are a set of workhorse tools for maintaining scientific digital image repositories. The tools implement photo renumbering, metadata harvesting (OAI-PMH), use of GLite for very large batch processing, Web-based high-resolution viewers, processing, long-term preservation, and more.
While the OSS community converges to Git, with the Python bunch branching to Mercurial, the typical workplace is stuck with Subversion. The author's DVCS of choice is Fossil. These are all fine projects, with their own pros and cons, but what you usually want is just a tool to store your code tree snapshot in a safe place. They can all do that, but their language differs a tiny bit. repo brings them all down to the common root. It works by detecting which VCS are you using right now and calling that, applying necessary subcommand translation if needed.