I have moved all of these to our new development "sideboard" [1] which can be used to store blueprints that don't make major releases. Alternately, if you have an idea and want help fleshing it out, this would be a great place to drop a blueprint for community collaboration. [1] http://wiki.ceph.com/01Planning/Sideboard Best Regards, Patrick McGarry Director, Community || Inktank http://ceph.com || http://inktank.com @scuttlemonkey || @ceph || @inktank On Thu, Nov 7, 2013 at 10:05 AM, Sage Weil <sage@xxxxxxxxxxx> wrote: > There are several blueprints that were put together for emperor even > though we didn't have the developer time to actually do them. For anyone > interested in getting involved in Ceph development, these may present an > easy way to get involved in the process. If you're interested in > adopting any of these orphan blueprints, speak up and we can make sure it > gets onto the firefly CDS schedule. > > In (very) approximate order of difficulty: > > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_shared_read_cache > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_namespace_support > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_copy-on-read_for_clones > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_dumpability > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/osd%3A_clone_from_journal_on_btrfs > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_reduce_memory_consumption > > sage > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
