Re: go repos concerns

Drasko DRASKOVIC <drasko@...>
 

Thanks a lot Fede.

This looks very good and simple from my point of view. It's concise
and visually we can understand easily the whole system.

This approach will significantly simplify CI, testing, release
versioning and tagging, and many other things. It will also keep code
consistent, SW developers will have code from other micro-services to
look as examples and stay consistent. Technical battier will be
lowered and this will increase adoption rate.

I am definitely in flavour for this approach. As I mentioned earlier,
merging our per-service-repo into a single repo for Mainflux
(https://github.com/mainflux/mainflux) was one of the best decisions
we made for the project. It was much simpler to work on the project.

In the end, I would reccomend this video:
https://www.youtube.com/watch?v=lV8-1S28ycM, but you can also see that
Goole keeps tons of code in the single repo for the same reasons I
mentioned earlier: https://www.youtube.com/watch?v=W71BTkUbdqE

Best regards,
Drasko DRASKOVIC
Mainflux Author and Technical Advisor

www.mainflux.com | Industrial IoT Cloud
-------------------------------------------------------------------
Engineering Division | Paris, France

LinkedIn: https://www.linkedin.com/in/draskodraskovic
Twitter: @draskodraskovic


On Thu, Jan 18, 2018 at 3:00 PM, Fede Claramonte
<fclaramonte@...> wrote:
Hi all,

we just wanted to share the work we have done with the monorepo:

https://github.com/feclare/edgex-go

It is automatically generated with this script:

https://gist.github.com/feclare/8dba191e8cf77864fe5eed38b380f13a

Regards,
Fede

On 19/12/17 17:18, Drasko DRASKOVIC wrote:

Hi Fede,

On Tue, Dec 19, 2017 at 4:12 PM, <James.White2@...> wrote:

Sounds good Fede. I too am just starting to get familiar with Go Lang
and
the issues associated my self.

Let me add a bit of time for us to discuss this issue at the Face - to -
Face meeting. This will also give us a chance for Jeremy to get some of
the
dev ops work done to produce the Go Lang artifacts and containers and
provide additional feedback.

This will still allow us time to react/change prior to the California
release in June.
If you have some time (and would like to learn), I would also suggest
setting-up a PoC GitHub repo (for example in your private GitHub
account) and doing integration of existing core repos. I can help you
with this. This way on F2F meting in Orlando we can present something
that works and then the advantages would be more tangeable, IMHO.

Best regards,
Drasko DRASKOVIC
Mainflux Author and Technical Advisor

www.mainflux.com | Industrial IoT Cloud
-------------------------------------------------------------------
Engineering Division | Paris, France

LinkedIn: https://www.linkedin.com/in/draskodraskovic
Twitter: @draskodraskovic

Join EdgeX-GoLang@lists.edgexfoundry.org to automatically receive all group messages.