*Great to read you* and know about your interest in the project! By your
description it seems to me that you will have *many ways for contributing*.
I'm Rodrigo, my contribution to the project has been mainly as scrum
master, product owner and tester. I want to give you the* welcome* and some
* context*, even though as Peter said, the specific* answer* to your
question needs to be *explored and completed from the technical side*.
The *high level context* I'll give you is mainly updated to the first days
of *December*, when we went on a pause, and includes some of the news from
which I'm aware of. I think it will be also a good opportunity also for all
to share new information so we get the full picture.
Please also consider my words as a description of what I know and my
understanding, and not my opinion or a definition about how it should be.
Also notice that the way in which we were organized was, with lot of room
for improvements, the one we could reach for a team somehow small and
stable, and it might need specific changes for receiving newcomers in a
better way . I think that your process will help us in that way too, and
is already being *your first contribution*.
All that said, last *milestones achieved *are:
- a* controlled release* on the SayCel network 
- starting the development of the minimum *SMS-to-chat version* 
*Next milestone* is:
- *finish the minimum SMS-to-chat version*
The *tasks *related with features development where mainly represented in
this <https://github.com/saycel/webph.one/projects/1> *kanban board*. This
backlog items used to be defined, prioritized, detailed and updated
regularly, based on the priorities agreed mainly with Peter and Edwin, in
their role of representatives from the users communities. A couple of other
tasks are also represented in the kanban, such as those related with issues
with the release and the creation of environments for testing, development
and production. Other (but not all the) conversations not represented there
are related with increasing test coverage and documentation for
You might also see issues <https://github.com/saycel/webph.one/issues> that
are not in the kanban. So far the team was taking them based on their
criteria, and sometimes we took them out of there to the product backlog
keep the list clear and the focus.
As said, the specific next steps for you will be better suggested by
technical members, and I like to think about them as a *co-creation with
 As an example, I will put some of this information into the specific
files that git suggests, such as the one about *contributing*.
 SayCel guys, would be great if you can share some updates and links
about what is happening there.
 Intended to be deployed first on Rhizomatica's communities in MÃ©xico
2018-02-09 11:58 GMT-04:00 Nicolas Pace <nico@xxxxxxxx>:
Hi Emil, nice to meet you,
I'm one of the technically inclined members :)
Now in between flights, but if no-one replies will write later with what I
think is ahead of us regarding the technical side.
On February 9, 2018 9:18:16 AM CST, peter <peter@xxxxxxxxxxxxxxx> wrote:
Welcome Emil. Glad to have you interested in the project. I'm Peter, the
general coordinator of Rhizomatica, one of the organizations pushing for
the development of the app. Hopefully some of the more technically
inclined members of the group can help you get oriented and see the best
way for you to collaborate.
On 08/02/18 14:10, Emil Kroymann wrote:
I just wanted to say hello. After seeing Stefans talk about the
project at FOSDEM 2018 in Brussels, I want to introduce myself and
discuss possibilities for me to contribute.
In my day job (since 2008), I am a software engineer in the VOIP field
and I also work a lot with Kamailio on WebRTC and other telephony
related projects. I am also versed in a number of programming
What do the people on this list think, how I could contribute?
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi