Re: Next steps?

I have created a Doodle poll to find a suitable time for our first
conference call after the holidays:
http://doodle.com/poll/rnuf4uuzfn9asdye

There is a quite a range of options to find both a day and a slot that
works for our very diverse and globally distributed group.

Please take the time to indicate all of the slots that you'd be available
to have a call.

The agenda has started on the wiki here:
https://github.com/interledger/five-bells-demo/wiki/Meeting-I

Unless we flesh this out a bit before January I propose that we use the
call to simply introduce ourselves and work on a road map and some
operating procedures going forward.


On 19 December 2015 at 17:57, Rafael Pereira <rafael@rippex.net> wrote:

> LGTM, thanks Adrian.
>
> Em qui, 10 de dez de 2015 às 20:11, Adrian Hope-Bailie <
> adrian@hopebailie.com> escreveu:
>
>> I have started putting a framework together for us to work on this here:
>> https://github.com/interledger/five-bells-demo/wiki
>>
>> My plan is to flesh these topics out over the next few days, feel free to
>> step in and add to them too.
>>
>> You'll see a link to the beginnings of an agenda for a first call for the
>> group.
>>
>> I expect that if we do this it will mostly be taken up by intros and
>> logistics for the future but let's get an agenda down here and we can begin
>> prioritizing what the group is keen to discuss.
>>
>> On 25 November 2015 at 00:10, Rafael Pereira <rafael@rippex.net> wrote:
>>
>>> I think that exchanging info related to the payment (messaging) should
>>> be a topic. Maybe "Messaging algorithms and architectures".
>>> And I agree with all the suggested topics.
>>>
>>> Em ter, 24 de nov de 2015 às 19:35, Ryan Fugger <arv@ryanfugger.com>
>>> escreveu:
>>>
>>>> Sounds good to me, Adrian.
>>>>
>>>> On Mon, Nov 23, 2015 at 6:05 AM, Adrian Hope-Bailie <
>>>> adrian@hopebailie.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> It feels like time to start creating some structure. How does the
>>>>> group feel about identifying a few key topics and starting to put a plan
>>>>> together on how to address these.
>>>>>
>>>>> Off the top of my head it looks like there is a lot of interest in:
>>>>>
>>>>>    - Pathfinding algorithms and architectures
>>>>>    - Querying and Validating Connectors (and possibly a registry of
>>>>>    trusted connectors)
>>>>>    - Standardising the format of the receipt that instructs a ledger
>>>>>    to release an escrow
>>>>>    - The ledger interface for reserving and then releasing funds
>>>>>
>>>>> Does this sound about right?
>>>>>
>>>>> I'm happy to get a wiki up and running on the GitHub repo to start
>>>>> documenting these.
>>>>>
>>>>> Once we have a some consensus on the topics of interest lets have a
>>>>> conference call to discuss further and pick some people who are going to
>>>>> drive each topic.
>>>>>
>>>>> Adrian
>>>>>
>>>>>
>>>>>
>>>> --
>>>
>>> Obrigado,
>>> Rafael
>>>
>>> *Rafael Olaio - CEO*
>>> tel +55 11 2337.2225
>>> cel +55 11 99522.7572
>>> rippex.net
>>>
>>> Esta mensagem pode conter informação confidencial e/ou privilegiada. Se
>>> você não for o destinatário ou a pessoa autorizada a receber esta mensagem,
>>> não poderá usar, copiar ou divulgar as informações nela contidas ou tomar
>>> qualquer ação baseada nessas informações. Se você recebeu esta mensagem por
>>> engano, por favor avise imediatamente o remetente, respondendo o e-mail
>>> e em seguida apague-o.This message may contain confidential and/or
>>> privileged information. If you are not the addressee or authorized to
>>> receive this for the addressee, you must not use, copy, disclose or take
>>> any action based on this message or any information here in. If you have
>>> received this message in error, please advise the sender immediately by
>>> reply e-mail and delete this message.
>>>
>>
>> --
>
> Obrigado,
> Rafael
>
> *Rafael Olaio - CEO*
> tel +55 11 2337.2225
> cel +55 11 99522.7572
> rippex.net
>
> Esta mensagem pode conter informação confidencial e/ou privilegiada. Se
> você não for o destinatário ou a pessoa autorizada a receber esta mensagem,
> não poderá usar, copiar ou divulgar as informações nela contidas ou tomar
> qualquer ação baseada nessas informações. Se você recebeu esta mensagem por
> engano, por favor avise imediatamente o remetente, respondendo o e-mail e
> em seguida apague-o.This message may contain confidential and/or
> privileged information. If you are not the addressee or authorized to
> receive this for the addressee, you must not use, copy, disclose or take
> any action based on this message or any information here in. If you have
> received this message in error, please advise the sender immediately by
> reply e-mail and delete this message.
>