Re: Architecture meeting

+1 Em sex., 26 de fev. de 2021 às 18:18, Daniel Takabayashi < daniel.takabaya...@gmail.com> escreveu: > +1 > > Em sex., 26 de fev. de 2021 às 13:00, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > Hey guys, hope you're doing well! In the next few days I'll do some PRs > >

Re: December report

+1 Em ter, 1 de dez de 2020 17:25, Daniel Takabayashi < daniel.takabaya...@gmail.com> escreveu: > +1 > > Em ter., 1 de dez. de 2020 às 12:18, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > +1 > > > > Em ter., 1 de dez. de 2020 às 16:34, Zhang Yifei > > escreveu: > > > > >

Re: Documentation improvement

+1 I suggest a Windows installation topic with docker and wsl. Em sex., 9 de out. de 2020 às 11:22, Lucas Cardoso Silva < cardosolucas61@gmail.com> escreveu: > Hi guys! As discussed in the other threads, we will improve our > documentation. > > I created an issue on ReadTheDocs setup: >

Re: Septembr Report

+1 Em ter., 1 de set. de 2020 às 20:04, Daniel Lucredio < daniel.lucre...@ufscar.br> escreveu: > +1 > > Em ter., 1 de set. de 2020 às 13:18, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > +1 > > > > Em seg., 31 de ago. de 2020 às 12:03, Zhang Yifei > > > escreveu: > > > >

Re: Moving to python 3

+1 Em qui, 6 de ago de 2020 16:02, Lucas Cardoso Silva < cardosolucas61@gmail.com> escreveu: > I made a pull request to change our components to python 3. In my opinion > it's easier to make the architectural change this way, also python 2 > reached it's end of support. I would like to know

Re: Architecture Evaluation process on Marvin-AI

+1 Em ter, 7 de jul de 2020 14:45, Daniel Takabayashi < daniel.takabaya...@gmail.com> escreveu: > +1 > > Em ter., 7 de jul. de 2020 às 10:18, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > Hello everyone. I would like to propose a more in-depth analysis of > > Marvin's

Re: MR for daemon gRPC code

Hello everyone. LGTM Lucas, +1 Em dom, 17 de mai de 2020 18:39, Zhang Yifei escreveu: > Hello Lucas, > > Lgtm. > > Em sex., 15 de mai. de 2020 às 11:09, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > Hello everyone. I created this topic to discuss how we will MR the

Re: Communication between CLI and Docker container in the new architecture.

Standardizing with gRPC seems better to me. It is a good agnostic and safe language solution. Em sex., 17 de abr. de 2020 às 14:56, Lucas Cardoso Silva < cardosolucas61@gmail.com> escreveu: > Standardize with gRPC seems like a better idea. It has all the security > features we need and

Re: Communication between CLI and Docker container in the new architecture.

LGTM +1 Em qui., 5 de mar. de 2020 às 13:31, Lucas Cardoso Silva < cardosolucas61@gmail.com> escreveu: > I think we could define better how we will make the communication CLI with > the Docker development instance in the new architecture. The container > needs a running process to stay

Re: report

LGTM +1 Em qui, 5 de mar de 2020 14:24, Daniel Takabayashi < daniel.takabaya...@gmail.com> escreveu: > +1 > > Em qua., 4 de mar. de 2020 às 14:58, Lucas Cardoso Silva < > cardosolucas61@gmail.com> escreveu: > > > Looks fine to me. > > > > Regards, > > Lucas Cardoso > > > > Em qua, 4 de mar

Re: Proposed new documentation for Apache Marvin-AI

ost the documentation at Readthedocs while > being and official Apache project. > Are there any other case like our? > Any chance to host it? Is the license compatible with Apache? > Luciano Resende do you have any other guidance? > > Em seg., 2 de dez. de 2019 às 20:48, Bruno Sette < >

Re: Proposed new documentation for Apache Marvin-AI

019 at 12:13 AM Bruno Sette > wrote: > > > Hi guys, > > > > We are proposing an improvement in the apache marvin documentation. The > > improvement is to use readthedocs.io as the basis for Marvin > > documentation. > > > > Benefits: > > *

Proposed new documentation for Apache Marvin-AI

Hi guys, We are proposing an improvement in the apache marvin documentation. The improvement is to use readthedocs.io as the basis for Marvin documentation. Benefits: * Easy community contrib to documentation (bug fixes or enhancements) * Responsive Documentation * Export documents in pdf, epub