gitter-badger / lagerta

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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.

Lathgertha

...is a project supporting light snapshots creation and management for in-memory data grids and fabrics.

Immediately Get Started with Deployment and Smoke Testing of BigTop

Quick overview of source code directories

Contributing

There are lots of ways to contribute. People with different expertise can help with various subprojects:

• core : Core functionality of the replicator, where most of the value of the project sits
• cassandra : Reference implmentation of the long-term storage layer
• documentation : We are always in need of a better documentation!
• giving feedback : Tell us how you use Lathgertha, what was great and what was not so great. Also, what are you expecting from it and what would you like to see in the future?

Also, reporting new issues and getting started by posting on the mailing list is helpful.

RTC model

Lathgertha is developed under Review-Then-Commit (RTC) model. The following rules will be used for the RTC process:

• a committer or a contributor should proactively seek a code review and feedback from other contributors. To speed up the review process the common sense quality criteria are expected to be met (e.g. reasonable testing has been done locally; all compilations pass; RAT check is passed; the patch follows coding guidelines)
• a committer should keep an eye on the official CI builds at to make sure that committed changes haven't break anything. In which case the committer should take a timely effort to resolve the issues and unblock the others in the community
• any non-document patch needs to address all the comment and reach consensus before it gets committed without a +1 from other committers

What do people use Lathgertha for?

Getting Started

For Developers: Running the tests.

For Developers: Building the project

For Developers: Building a component from Git repository

Contact us

You can get in touch with us on