-
Notifications
You must be signed in to change notification settings - Fork 22
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
Can I experiment with this repository? #41
Comments
@lrytz already got Lightbend and customer go-ahead to open-source:
so I think in the short term you can proceed with confidence that this will be open source. I'll take care of actually making it happen. (I'm personally interested in seeing it open-sourced, for multiple reasons.) generally we are choosing Apache 2.0 rather than BSD these days. |
we'll need to chose some wording about maintenance/support status. basically saying "we're putting this out there as-is, we're not sure how much maintenance it will get (if any)" |
Yeah. Also, i see this is quite old (2 years ago) and some changes have happened in Zinc regarding type dependencies that may be need to be duplicated here (i haven't dug into the code yet). In that case I can do that.
I guess that something along the lines of what Paradox has in its README would be great.
Ok, you may be interested in changing that in the repository and the github metadata then 😄. |
Thank you guys, for open-sourcing. |
I've verified that there's nothing inappropriate in the commit history, pull requests, or issues (I only had to edit one comment on one issue), so we'll be able to flip the switch from private to public, without having to make a fresh repo. (I think we always assumed this would become open eventually and so were careful about what we said.) |
maintenance status notice: d677f9c |
repo is public now |
This repository is useful for analysing code at large scale. I'd like to experiment with it to find the best way to split a big project in small repositories that are faster to build. This is the first step to have a nice automatic process that migrates monolitic codebases to smaller pieces that can be efficiently compiled by Bazel.
I'd like to do this for fun, on my free time, and for that I'd like this company to be open-source to ensure that I can share my findings. It goes without saying that the BSD 3-way license will not be violated.
The text was updated successfully, but these errors were encountered: