March meeting summary
Hi!
Thanks to all participants of our monthly LTP meeting. A short summary on what we talked about:
- we have ~300 tests to refactor into the new LTP API, which 2/3 of them are really low to slightly mid complexity
- in order to attract more developers and reviewers, we need to provide more documentation about the LTP project. This can be achieved by sharing workshops, blogs and documentation that can help junior developers to start working on small LTP tests. In short, to simplify documentation reachability
- to improve our documentation we can try "readthedocs.io" that is similar to what kernel devs are using (check https://korg.docs.kernel.org/docs.html). In this way we can also provide a more readable LTP website
- to introduce a special flag to communicate with tests runner (kirk) when we need to reboot the machine during tests
- we discussed about some tooling, AI, reviewing tools, bots
Thanks for all the suggestions and improvements.
Have a good day and see you the next month!
Best regards,
Andrea Cervesato
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Hi Andrea,
Nice summary.
I guess it would be good to copy it into the meeting pad, and then we can easily recap the history recording when necessary.
https://docs.google.com/document/d/1KjwAyRV8Xe0jdQ1aWCpQlWT4bKKMbumQ2CHQVEZHsAk/edit
Quoted 36 lines · Andrea Cervesato via ltp
Hi!
Thanks to all participants of our monthly LTP meeting. A short summary on what we talked about:
- we have ~300 tests to refactor into the new LTP API, which 2/3 of them are really low to slightly mid complexity
- in order to attract more developers and reviewers, we need to provide more documentation about the LTP project. This can be achieved by sharing workshops, blogs and documentation that can help junior developers to start working on small LTP tests. In short, to simplify documentation reachability
- to improve our documentation we can try "readthedocs.io" that is similar to what kernel devs are using (check
https://korg.docs.kernel.org/docs.html). In this way we can also provide a more readable LTP website- to introduce a special flag to communicate with tests runner (kirk) when we need to reboot the machine during tests
- we discussed about some tooling, AI, reviewing tools, bots
Thanks for all the suggestions and improvements.
Have a good day and see you the next month!Best regards,
Andrea Cervesato--
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 6 lines
Regards, Li Wang -- Mailing list info: https://lists.linux.it/listinfo/ltp
I'd like to just say that I find this summary of the meeting very useful. Thanks for providing it!
-- Tim
Quoted 36 lines
-----Original Message-----
From: ltp <[email protected]> On Behalf Of Andrea Cervesato via ltp Hi!Thanks to all participants of our monthly LTP meeting. A short summary on what we talked about:
- we have ~300 tests to refactor into the new LTP API, which 2/3 of them are really low to slightly mid complexity
- in order to attract more developers and reviewers, we need to provide more documentation about the LTP project. This can be achieved by sharing workshops, blogs and documentation that can help junior developers to start working on small LTP tests. In short, to simplify documentation reachability
- to improve our documentation we can try "readthedocs.io" that is similar to what kernel devs are using (check
https://korg.docs.kernel.org/docs.html). In this way we can also provide a more readable LTP website- to introduce a special flag to communicate with tests runner (kirk) when we need to reboot the machine during tests
- we discussed about some tooling, AI, reviewing tools, bots
Thanks for all the suggestions and improvements.
Have a good day and see you the next month!Best regards,
Andrea Cervesato--
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp