-
Notifications
You must be signed in to change notification settings - Fork 0
Initial review of the code #1
Comments
Sorry for the delay. I finally had time to work on the preparation work. Preparation workFirst of all, I want to say one thing. Sympa::API seems to wrap Sympa::Request, but I don't agree with this development approach. Because it increases complexity and reduces maintainability (the code of current Sympa is/was severely unmaintainable, largely due to similar approaches in the past). If you think there is a problem with current Sympa::Request, please suggest a solution first --- instead of leaving the problem and building another one. If you don't have any suggestions, I'll try to find a solution. The following are the requests for the preparation work I mentioned above. 1. Obvious fixes of bugs and so on in the main project (sympa-community/sympa)@yent, please submit these things as the issues with PR on the main project.
src/lib/Sympa/Config.pm
src/lib/Sympa/Request/Handler/viewmod.pm
src/lib/Sympa/Request/Handler/post_message.pm
src/lib/Sympa/Spindle.pm
src/lib/Sympa/Spindle/AuthorizeRequest.pm
src/lib/Sympa/Spindle/ToAuth.pm
src/lib/Sympa/Spindle/ToAuth.pm
src/lib/Sympa/Request/Handler/create_list.pm
default/scenari/add.closed 2. Additions or extensions of Sympa's internal API (Sympa::Request::Hander modules) or the other functionalities added into the main project:@yent, these commits are a mix of changes to the main project and those that are not. The former should be submitted as issues or PRs in the main project. The latter are mentioned first.
src/lib/Sympa/Request/Handler/distribute.pm
t/rest/reject.t
t/rest/get_pending_message.t
t/rest/get_pending_messages.t
src/lib/Sympa/Request/Handler/post_message.pm
t/rest/post_message.t
t/rest/post_message.t |
@yent, Could you please answer? |
@yent, if we do not receive any response in one month, i.e. by December 25th, it may be assumed that you have no intention to contribute to the Sympa Community, and this repository will be closed. |
No response. Close. |
This article describes the process of initial code review on a contribution to the Sympa community.
What we will do
We will carry out the process by which people who read the code give their opinions and criticisms, and the author modifies the code accordingly.
Place of work
The code base should be placed in a separate project (repository) from the main project, sympa-community/sympa-rest.
See also "Preparation work" below.
Duration
At least six months is necessary. In addition, several months are needed to revise the code based on the results of the review.
Method
The review will be carried out in public. In practice, the GitHub issue page is used.
Preparation work
Prior to the review process, preparation work will be performed.
=> Submitted as the issues with PR on the main project.
=> Submited as the issues (possiblly with PR) on the main project.
=> Put in the place of work above.
Preparation work is expected to take for one to two months.
After a week or so, we would like to start the preparation work.
The text was updated successfully, but these errors were encountered: