Re: [ceph-users] Ceph Developer Summit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ross,

It works like a charm :

http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/Erasure_encoding_as_a_storage_backend#Coding_tasks

Thanks :-)

On 04/22/2013 07:40 PM, Ross David Turk wrote:
> 
> Hi Loic!
> 
> I totally agree.  I've actually set up an etherpad, but haven't had a 
> chance to tell anyone yet!  We should add one to each blueprint before 
> the summit begins.  You can find the etherpad here:
> 
> http://pad.ceph.com
> 
> I wrote a quick dekiscript plugin that embeds an etherpad inside a 
> wiki page.  If you include this tag in your wiki page, it will embed a 
> pad with the same name as the Wiki page ID:
> 
>   {{ etherpad{} }}
> 
> If you want to specify a pad name, use this instead:
> 
>   {{ etherpad{ name: "foo" } }}
> 
> Let me know if it works for you!
> 
> Cheers,
> Ross
> 
>  
> On Apr 20, 2013, at 10:22 PM, Loic Dachary <loic@xxxxxxxxxxx> wrote:
> 
>> Hi Ross,
>>
>> It would be convenient to discuss the implementation of blueprints using and etherpad during the summit. I'm thinking
>>
>> http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/Erasure_encoding_as_a_storage_backend#Coding_tasks
>>
>> for instance. Although a wiki is convenient for discussing before the summit, an etherpad is better during the summit, IMHO. 
>>
>> What do you think ?
>>
>> On 04/12/2013 03:27 AM, Ross David Turk wrote:
>>>
>>> Hi, everyone!
>>>
>>> I'm pleased to announce that we have begun preparations for the first 
>>> Ceph Developer Summit. This summit is where planning for the upcoming 
>>> Dumpling release will happen, and attendance is open to all. It will be 
>>> virtual (IRC, etherpad, video conference), so you won't even have to 
>>> get on an airplane! We're targeting May 6.
>>>
>>> Between now and then, we're gathering blueprints for new Ceph features! 
>>> A blueprint is a document that describes work someone intends to do, 
>>> usually reserved for larger features that require discussion. If 
>>> there's a feature you think Ceph should have, we encourage you to write 
>>> your thoughts and plans in a blueprint. Then make sure to attend the 
>>> summit to discuss its implementation with others in the Ceph community.
>>>
>>> For more details, take a look at Patrick's blog post on ceph.com:
>>>
>>> http://ceph.com/events/ceph-developer-summit/
>>>
>>> Blueprints are currently being accepted at the Ceph wiki. On the front 
>>> page, at the bottom, there's a button to create a new one.
>>>
>>> Oh! Yeah! There's a wiki now. It's kind of bare-bones at the moment, as 
>>> most wikis are when they first enter the world, but it anxiously awaits 
>>> your content. Log in with your OpenID credentials and pick a username 
>>> to get started. If you're having trouble, or have feedback, your words 
>>> are always welcome at community@xxxxxxxx.
>>>
>>> http://wiki.ceph.com
>>>
>>> Best,
>>> Ross
>>>
>>> --
>>> Ross Turk
>>> Community, Inktank
>>>
>>> @rossturk @inktank @ceph
>>>
>>> _______________________________________________
>>> ceph-users mailing list
>>> ceph-users@xxxxxxxxxxxxxx
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>
>> -- 
>> Loïc Dachary, Artisan Logiciel Libre
>>
> 
> 
> --
> Ross Turk
> Community, Inktank
> 
> @rossturk @inktank @ceph
> 

-- 
Loïc Dachary, Artisan Logiciel Libre

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux