What is the best and right way to open-source packages from a company monorepo?

栏目: IT技术 · 发布时间: 5年前

内容简介:There are a few tools to split commits from sub-dirs to a branch which you can then push to a public repo/monorepo.E.g. `git subtree`, https://github.com/facebook/fbshipit, https://github.com/splitsh/lite, https://github.com/ingydotnet/git-subrepo.A lot of

There are a few tools to split commits from sub-dirs to a branch which you can then push to a public repo/monorepo.

E.g. `git subtree`, https://github.com/facebook/fbshipit, https://github.com/splitsh/lite, https://github.com/ingydotnet/git-subrepo.

A lot of these approaches though rely on the source-of-truth being the internal company monorepo. PRs are synced internally, merged, and then pushed out. It means that someone outside the organization cannot be a maintainer, and the speed of PR merges is dictated by the available resources inside the company. So I'd argue this is not the right OSS way of doing things.

Even if there are two public monorepos out in the open you can have similar problems trying to collaborate, because to modify one line of a package, you may need to pull a huge monorepo and its tooling down.

Does anyone have a solution or an example of an OSS-friendly approach to monorepo open-sourcing?


以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网

查看所有标签

猜你喜欢:

本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们

集创思维设计矩阵

集创思维设计矩阵

慈思远 / 电子工业出版社 / 2017-4 / 72.00元

《集创思维设计矩阵——写给互联网人的设计指南》总结了作者从业7年以来的设计经历,在大量企业所面对的设计问题基础上,提出了枪型思维,即如何给产品更准确的定位。 在定位准确的基础上加以设计,提出了设计中高维度融合低维度的设计思维,即设计者可以从商业逻辑推演到设计逻辑,让设计更加精确;又提出了设计和计算的博弈,指出在每一步创新的基础上,设计者一定要清晰地评判设计的代价。这样设计后的产品才是可以和企......一起来看看 《集创思维设计矩阵》 这本书的介绍吧!

图片转BASE64编码
图片转BASE64编码

在线图片转Base64编码工具

HTML 编码/解码
HTML 编码/解码

HTML 编码/解码

html转js在线工具
html转js在线工具

html转js在线工具