This library has been officially incubated in the Scala Platform, congratulations! This means the following:
- Library authors have complete access to Scala Platform's infrastructure.
- Automatic release process.
Drone integration with caching and several customization features.
- Official group ids are at maintainers' disposal. They can release under them if they desire so.
- Library authors will take part into future decisions regarding Scala Platform Process's rules.
- There will be a final vote to accept this proposal into the Scala Platform. This final vote will be done whenever library maintainers feel it's the right moment to end the incubation.
More information in the official Scala Platform Process.
The incubation period is the perfect moment for gathering developers around your library, creating a community, cleaning up APIs (note that changes in public APIs cause binary incompatibility and are done every year and a half), accepting PRs, creating well-documented issues that people can work on, et cetera.
- Library maintainers accept Scala Center's Code of Conduct and use it in their projects.
- Library maintainers decide the license they will use (they can stay with the same they have).
- Library maintainers decide whether they endorse C4 or not.
- Libraries have Gitter channels and pertinent CONTRIBUTION guidelines for people to submit paches/PRs!
Remember that taking decisions on these issues is extremely important for creating a community around the modules -- our end goal! You can also participate in the current open debates to abstain from recommending C4 / MPLv2 or changing the major cycle to one year instead of 18 months; your opinion is highly valuable, so please comment.
At the Scala Center, we're planning to run a series of hackathon in well-known Scala conferences to encourage people to hack on open issues of Scala Platform modules and join their community. Our goal is to boost the success of the Platform and help us get to a point where we can all benefit from a high-quality collection of modules. This is why having CONTRIBUTION guidelines, tips to developers and a getting started guide is important -- consider writing them.
In the case of this proposal, there have been several recommendations by the Scala Platform Committee:
- Change name (@pathikrit has already agreed this is a good idea). Does someone have any idea for alternative names to Better files?
- Clean up the API, especifically the extreme use of symbols. /cc Eugene Yokota and @Ichoran can probably be more specific in an issue about what they'd like to be polished.
Also, in this conversation we've been discussing new ideas that would be worth to be implemented in the Incubation period. @mdedetrich has already open an issue to discuss ways to make Better files cross-compatible with Scalajs. Please, if you're interested in this, get in touch with him!
@larsrh or @tpolecat: Do you know of something that would be interested in creating a pure API based on better-files?
Regarding infrastructure, I'll contact library maintainers to make the transition in the next days. Thank you very much for getting involved in this collaborative effort to improve the experience of Scala developers all around the world.