Hello Loic and Koleos, Do we have any wiki page documenting the progress and report of this effort? We are very interested in such as well. Thanks, Guang On May 8, 2014, at 1:19 AM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > > Hi, > > On 07/05/2014 18:43, Koleos Fuskus wrote:> Hi Loic, >> >> What do you mean by action plan? if is the schedule, it is published on my proposal in melange site. Indeed, the details of my proposal are private, if is that what you mean, I can added on the wiki. If you want this part to be public no problem. > > Yes, that's what I meant :-) You could collect snippets from the proposal posted on melange and present them on a subpage https://wiki.ceph.com/Development and we can use this as the "home page" of your work ? > >> Actually I am using some of my free time on reading ceph documentation (web and papers). Do you have any specific document to recommend me? Maybe we can discuss again about the durability model on Friday/Monday. I need some more understanding about the ceph architecture. > > I'm connected on irc.oftc.net#ceph-devel today and tomorrow if you'd like to chat during this "community bonding" phase (I don't remember how google calls this for GSoC participants ;-) > > Cheers > >> >> Cheers, >> Verónica >> On Wednesday, May 7, 2014 8:12 AM, Loic Dachary <loic@xxxxxxxxxxx> wrote: >> Hi Veronica, >> >> I was really happy to hear you're going to work on the erasure code reliability model. Unless I'm mistaken your action plan was not published. Would you mind adding it to the wiki so I can comment on it ? Someone else might be interested to contribute too. I've had a discussion yesterday about durability models (internally) and it is not well understood. Your insight would be precious. >> >> Cheers >> >> -- >> Loïc Dachary, Artisan Logiciel Libre >> >> > > -- > Loïc Dachary, Artisan Logiciel Libre > -- 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
