Moe

Make Open Easy

Note: This is a separately maintained fork of Google's MOE. Given that Google's MOE is now unmaintained, little to no effort will be made to keep in sync, and I expect the code to stray from the original substantially in detail.

Introduction

MOE is a system for synchronizing, translating, and scrubbing source code repositories. Often, a project needs to exist in two forms, typically because it is released in open-source, which may use a different build system, only be a subset of the wider project, etc. Maintaining code in two repositories is burdensome. MOE allows users to:

synchronize (in either or both directions) between two source code repositories
use different types of repositories (svn, hg, git) in combinations
maintain "scrubbed" content in an internal or private repository.
transform project paths to support different layouts/structures in different repositories
propagate or hide individual commits, commit-authorship, and other metadata between repositories while syncing.

Project Status

MOE was created around 2011, by a Dan Bentley at Google. Google teams that maintain open-source releases (guava, dagger, auto, etc.) used it regularly, and dusted it off to share fixes, improvements, and help folks who used it outside of Google. Many Google projects shifted to Copybara, leaving MOE lingering, though it satisfied some projects' use-cases which were not handled by Copybara.

Given that I, Christian Gruber, a later maintainer, continue to use it outside of Google, I've forked the project so I can evolve it to suit my needs, without putting a burden on Googlers to sync changes internally.

The project is currently undergoing a fair bit of re-factoring and needs better documentation, which i'm working on.

Usage

Building MOE

Install Bazelisk
Checkout the Java-MOE source git clone git@github.com:google/MOE.git
In the top level directory that contains the WORKSPACE file, run:
- bazel build //client:moe
The moe client binary should be created at bazel-bin/client/moe
(optionally) install the client somewhere in your $PATH

Running MOE

Once you have the moe binary, you should be able to simply run: moe <arguments for MOE>

Configuring MOE

To configure your project for moe, check out the wiki

Contributing

Contributing to MOE is subject to the guidelines in the CONTRIBUTING.md file

License

  Copyright 2011 The Moe Authors. All Rights Reserved.
  Copyright 2011 Google, Inc. All Rights Reserved.

  Licensed under the Apache License, Version 2.0 (the "License");
  you may not use this file except in compliance with the License.
  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.

cgruber/MOE

Moe