Keith Turner

After apache/incubator-fluo#773 should be able to remove some code from fluo recipes in cases where transaction interface is implemented.

After #82 I think it may make sense to drop the Encoder used by the TypeLayer and instead use the SimpleSerlializer. This will result in a more uniform and consistent...

Initially in #17 had modified an IT to ensure the transient data would be cleaned up. However I ran into fluo-io/fluo#559. I would like to look into fluo-io/fluo#559 before writing...

Need end to end documentation showing how to use Accumulo Exporter and Replicator

I am thinking we may want to make a recording transaction fail if its used after a call to get the txlog was made.

TxLog could dedupe objects. For example in the case where the TxLogs contains two different Bytes objects with equal content, it could just maintain a pointer to one. Not sure...

Add a recipe for dealing with reference counted objects

One way to do this is with Copr, which is probably the easiest way to get started. Another avenue is to make an official Fedora package and then promote that...

Maybe could create create a sharkbite team ppa on launchpad? Not sure what would be best I have only used ppa's as a consumer, I have never created a ppa....

For Fluo I created the [Fluo Tour](https://fluo.apache.org/tour/) which was inspired by the [Go Lang Tour](https://tour.golang.org/). I really liked this hands on style of documentation with each step introducing a concept....