Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organize TCVM, TC API Java and Litebase in different repositories on github #2

Closed
VaneskaSousa opened this issue Apr 16, 2020 · 4 comments
Assignees
Labels
feature

Comments

@VaneskaSousa
Copy link
Collaborator

VaneskaSousa commented Apr 16, 2020

From version 6 TotalCross SDK is open source. Our goal is to make contributing the simplest, facilitating the understanding of what makes up the TC SDK.

But we have some difficulties because if we separate the repositories will cause cyclic dependencies between them.

Please, feel free to contribute with your help and questions!

@jeffque
Copy link
Collaborator

jeffque commented Jun 26, 2020

There is little to no use of doing it in different repositories.

Have you eve heard of the"monorepo" concept? It may be helpful to understanding how to get it contributable

@acmlira
Copy link
Contributor

acmlira commented Aug 4, 2020

I think the scope is still defined or this is no longer a issue. Hey @ItaloYeltsin what do you think about it?

@ItaloYeltsin
Copy link
Contributor

ItaloYeltsin commented Aug 4, 2020

We had a little discussion on Telegram, but we have not decided yet. Anyways, litebase must be removed. For now, I think we must at least rename the folders from TotalCrossSDK and TotalCrossVM to sdk and vm.

@acmlira acmlira added this to Triage in Issue tracker Sep 18, 2020
@flsobral
Copy link
Member

flsobral commented Oct 5, 2020

Splitting the SDK and the VM into separate repositories makes no sense, not to mention the extra trouble keeping both versions in sync.

Moving Litebase to its own repository does make sense and it's something I'd like to do, but it's not something we are going to do for the time being.

@flsobral flsobral closed this as completed Oct 5, 2020
@nmarquesin nmarquesin moved this from Tracked to Closed in Issue tracker Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature
Projects
Development

No branches or pull requests

6 participants