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

Can I experiment with this repository? #41

Closed
jvican opened this issue Jan 18, 2018 · 9 comments
Closed

Can I experiment with this repository? #41

jvican opened this issue Jan 18, 2018 · 9 comments
Assignees

Comments

@jvican
Copy link

jvican commented Jan 18, 2018

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.

@SethTisue
Copy link
Contributor

SethTisue commented Jan 18, 2018

@lrytz already got Lightbend and customer go-ahead to open-source:

lukas [2:00 AM]
@jvican I got permission to open-source scala-sculpt, the dependency extraction project we did for (company) a while ago. For now I gave you read permission to the repo https://github.com/typesafehub/scala-sculpt
Before making it public we need to make sure everything is in order (license, no references to (company) anywhere).

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.

@SethTisue SethTisue self-assigned this Jan 18, 2018
@SethTisue
Copy link
Contributor

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)"

@jvican
Copy link
Author

jvican commented Jan 18, 2018

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.

basically saying "we're putting this out there as-is, we're not sure how much maintenance it will get (if any)"

I guess that something along the lines of what Paradox has in its README would be great.

generally we are choosing Apache 2.0 rather than BSD these days.

Ok, you may be interested in changing that in the repository and the github metadata then 😄.

@SethTisue
Copy link
Contributor

spun off #42 (license change), #43 (out-of-date-ness)

@jvican
Copy link
Author

jvican commented Jan 18, 2018

Thank you guys, for open-sourcing.

@SethTisue
Copy link
Contributor

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.)

@SethTisue
Copy link
Contributor

maintenance status notice: d677f9c

@SethTisue
Copy link
Contributor

repo is public now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants