Supporting MUI v4 Packages?

[kajirikajiri]

Supporting MUI v4 Packages?

[kajirikajiri]

First of all, thank you for the issue.

Will reply later. It will probably be over the weekend.
This is a project I am working on in my spare time.

Reply at the moment.

• I had not thought deeply about the licence.
• I was aware of the version issue, but had not yet thought about how to deal with it. For example, what if next version comes out.

[kajirikajiri]

There are three issues, listed in order of priority, as follows

1. about the licence of this package
2. about forking the repository and making changes
3. support for v4

I do not expect this to be completed immediately. If you are patient, please wait a while.

Firstly, if the licensing issue is not clear, we are giving it a higher priority because we thought it would be a bigger issue than the other issues.

Secondly, about forking this repository and making changes. At this point, from what I can gather, cloning and modifying packages with unclear licences may cause problems in the future. So it would be better to create it as a new package for your reference.

Finally, support for v4, I am thinking of adding it, but the two above are my priority, so I will think about it as soon as that is done.

以下、日本語

問題は３つあり優先度順に並べてみたところ以下のようになりました。

1. このパッケージのライセンスについて
2. リポジトリをフォークして、変更を加えることについて
3. v4のサポート

すぐに完了するとは思っていません。気長に待っていただけるようでしたら、しばらくお待ちください。

まず、ライセンスの問題がはっきりしない場合、他の問題よりも多きな問題になると思ったため優先度を上げて対応しています。

次に、このリポジトリをフォークして、変更を加えることについてです。現時点で私が調べた範囲ではライセンスがはっきりしないパッケージをクローンし、変更を加えることは将来的に問題が起こる可能性があると思われます。なので、参考にしていただいて新しいパッケージとして作成した方が良さそうです。

最後にv4のサポートですが、追加しようとは思っていますが、上の２つが優先なので、それが終わり次第考えます。

[awanlin]

Thanks for your reply, much appreciated.

I agree with your listed priority, that seems a reasonable path forward. Without the license question decided the other questions can't be answer yet.

For the v4 support I am willing to submit a PR for the needed changes.

If you have any questions for me or need any more information feel free to reach out

[awanlin]

Just wanted to follow up to see if there was any updates?

I'm honestly happy to just get the license question cleared away. I've been doing some investigation on our side and it seems we may need to customize things a fair amount to handle our use case. My struggle is that I've looked at your code often so I'm not totally working on this from a blank slate.

Thanks in advance for any reply.

[kajirikajiri]

Sorry for the late reply.

Just wanted to follow up to see if there were any updates?

Sorry, we have not received any updates. No progress has been made.
I have had a lot of personal problems recently and I don't have enough time. That's why I haven't been able to look into the licence.

My struggle is that I've looked at your code often so I'm not totally working on this from a blank slate.

This package must be difficult to understand because it is a complex process. Can you tell me which part you are having trouble with?

---

From this point onwards, the information is given in Japanese. My notes.

返答が遅れてすみません。

Just wanted to follow up to see if there was any updates?

申し訳ありません。進捗はないです。
最近、個人的な問題が多いため時間が足りません。そのためライセンスのことを調べられていないです。

My struggle is that I've looked at your code often so I'm not totally working on this from a blank slate.

このパッケージは複雑な処理をしているため理解しづらいはずです。どの箇所が困っているか教えていただけますか？

[awanlin]

My turn to be sorry, life got busy and I did not get a chance to read your reply till now.

First, thanks for the reply, it is appreciated. Second, I can understand life getting in the way, that is reasonable to me.

Actually, your code is really well done! My problem is that I'm hitting some of the same things you have and I'm pulling some of my solutions from having seen your code which without a license I worry about that. I'm trying to build mine in TypeScript as that is what Backstage itself is written in. I have basic validation in place but need to get the fixer working. Once I have that done I think I will just crate a personal repo and you can look at it to see if you have any issues with what I've done

[kajirikajiri]

#39

I did a lot of research and could not come up with an idea of what to do about the licensing of this package.
I am not sure if this is the right response, but I have decided to deprecate this package.
In the future, when I create software like OSS, I would like to think more about the license.

---

いろいろ調べたのですが、このパッケージのライセンスについてどうしたら良いか考えがまとまりませんでした。
この対応で良いのかわかっていませんが、このパッケージを非推奨とさせていただきました。
今後、OSSのようなソフトウェアを作成するときにはライセンスについてもっと考えて作成したいと思います。