Refactoring for upgrading to gup version 1.0.0.

[nao1215]

The gup command has been used by more people than expected. However, the implementation and design of the gup command have a very low level of completion for the following three reasons:

1. It was implemented by developers who were unfamiliar with golang at the time.
2. There was a major forced change from the initial design.
3. Functionality was added without limitations.

Due to these reasons, the gup command has become difficult to maintain, especially in terms of writing test code.Therefore, a complete refactoring will be performed before upgrading to version 1.0.0.

[aqyuki]

If you would like, I would like to help.

[nao1215]

@aqyuki
Thank you for your kind offer. Unfortunately, there are no plans to update the gup command to v1.0.0 this year. The reason is that I am focusing on developing an end-to-end testing framework called go-spectest/spectest.

I feel that there is a need to increase the unit tests before updating the gup command to v1.0.0. This task is challenging and not very exciting.

If you are an engineer who enjoys development, there is a project that could use your help. It's a sub-project of spectest called go-spectest/naraku. It's a project where you are free to create APIs. The purpose of Naraku is to test the APIs created using Spectest and evaluate the usability of the Spectest framework. Currently, we don't have any API ideas, and we're in a challenging situation.

If you enjoy creating APIs, I would be delighted if you could assist with naraku.

[aqyuki]

Of course, I would like to help you!

[nao1215]

@aqyuki
Really? That's good news! I'm glad to hear that you'll be helping with the development. I've added the development instructions to the naraku repository. The repository is newly created and doesn't have many features yet.

I would be delighted if you could propose ideas for small-scale APIs to start with. For example, APIs that return the version and codename of Linux distributions, or APIs that provide information about holidays. Once you have API ideas, please write the details in an Issue (you can write it in Japanese as well).

Once I approve the idea in the Issue, I'd like you to proceed with the implementation. If you prefer to focus solely on implementation, after I create an API proposal in the Issue, I'll mention you and ask you to implement it.

P.S.
無理のない範囲で手伝っていただければ良いです。飽きたら、すぐ止めていただいても大丈夫です。
コントローラ層にロジックを書いても問題ない程度の小さいAPIを作るところから始めるつもりです。