Dear Waldek, as we currently do not have resources dedicated to Capstan, we support the decision to merge back into cloudius-systems/capstan repo as well as move the package repository to a different S3 bucket or even GitHub like you proposed.
Let me know how you would like to proceed. cheers, -Gregor > On 26 Mar 2019, at 04:20, Waldek Kozaczuk <[email protected]> wrote: > > Dor, > > This is actually exactly what I was pondering as well. I am adding Miha (main > contributor to Mikelangelo capstan) and Greger (both from XLab) to see what > the think about merging back https://github.com/mikelangelo-project/capstan > <https://github.com/mikelangelo-project/capstan> to > https://github.com/cloudius-systems/capstan > <https://github.com/cloudius-systems/capstan>. > > Doing that may cause even more confusion on users side but on other hand it > may make it easier to locate it and eventually make it all less confusing > :-). In addition merging back may make it easier to continue enhancing > capstan given that Mikelangelo project is completed and XLab from what I know > moved on to other things. > > All, > Thoughts? > > On Mon, Mar 25, 2019 at 2:19 AM Dor Laor <[email protected] > <mailto:[email protected]>> wrote: > IMHO the original Capstan git is the best but you're most welcome to host it > in yours too > > On Sun, Mar 24, 2019 at 6:58 AM Waldek Kozaczuk <[email protected] > <mailto:[email protected]>> wrote: > Now that we have new updated message in the old capstan repo - > https://github.com/cloudius-systems/capstan > <https://github.com/cloudius-systems/capstan> (thanks Pekka) - we are all > good :-) This obviously solved one problem but there is other one - new > Mikelangelo capstan points to the S3 repo - > https://mikelangelo-capstan.s3.amazonaws.com/ > <https://mikelangelo-capstan.s3.amazonaws.com/> - which is no longer > maintained and has old artifacts - kernel and old mpm files. What is worse > that old kernel (loader.img) and new artifacts published on github are not > compatible due to a breaking change we made to OSv app API in order to > support golang - see other email exchange with Rob. And I think it causes a > lot of frustration among any new potential OSv and capstan users. > > One alternative to solve this problem would be to make new capstan work with > artifacts published on github. I even have a "work-in-progress" branch - > https://github.com/wkozaczuk/capstan/tree/github_repo > <https://github.com/wkozaczuk/capstan/tree/github_repo> that supports it. I > might have some time to finish it. I hope that Miha from XLab will be kind > again to review my pull request and publish new version of capstan. > > Does anybody have other better ideas? > > Waldek > > -- > You received this message because you are subscribed to the Google Groups > "OSv Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
