1. Achieve fence, if necessary, migrate code to java chassis master branch
I'd prefer to keep it. Maybe we can refactor this project and add
more functions soon.
2. Achieve toolkit, if necessary, migrate code to java chassis
master branch
We first need to discuss why archive it. some users still use some
of this function.
3. migrate docs to website
We first need to anylse the plan and how to. As I know, these two
projects use different way to write documents and website is quite difficult to
add new contents. And the most important
is both of these two websites are not stable and not accessble to users. Maybe
we need find better way to provide official websit and write contents.
------------------ ???????? ------------------
??????:
"dev"
<[email protected]>;
????????: 2021??2??23??(??????) ????6:48
??????: "dev"<[email protected]>;
????: Re: Disccusion about archive some of code repositories of ServiceComb
Saga-acuator is the first version of saga implementation.
This repo is archived, we don't need to do anything there.
Willem Jiang
Twitter: willemjiang
Weibo: ????willem
On Tue, Feb 23, 2021 at 6:43 PM Xiaoliang Tian <[email protected]>
wrote:
>
> Hi All,
> Please checkout
https://github.com/apache?q=servicecomb&type=&language=
> As We can see the right side of each of project, some repositories has no
> one maintains anymore. So I propose to archive 4 projects:
>
> 1. Achieve fence, if necessary, migrate code to java chassis master
branch
> 2. Achieve toolkit, if necessary, migrate code to java chassis
master
> branch
> 3. Archive saga-acuator if necessary, migrate code to pack master
branch
> 3. migrate docs to website.
>
> Please give you suggestions
