Yansongsongsong commented on issue #1250: URL: https://github.com/apache/incubator-opendal/issues/1250#issuecomment-1526949248
> Hello, @Yansongsongsong. Thank you for your interest! However, we have already submitted this issue as an OSPP project. Would you be interested in taking on this project as a student? > > More details could be found at https://summer-ospp.ac.cn/org/orgdetail/111e2fe9-025b-46da-a6c5-1b0de297abdd?lang=en i dont really care about which role i am to make a contribution. but i am not a student any more. if it is acceptable. i am okay actually. BTW the link you give here is not open for application. Here is my plan for this issue: 1. make one pull request for [oss-fuzz](https://github.com/google/oss-fuzz/) 2. cuz the previous title is `ObjectReader`, i read a bit about behavior testing in `tests` folder. I plan to give some documentation for this part. 3. Then fuzz target related. There are two ways: - maintain the fuzz target on [oss-fuzz](https://github.com/google/oss-fuzz/) side. just like [`redis-rs` ](https://github.com/google/oss-fuzz/blob/master/projects/redis-rs/fuzz/fuzz_targets/parser.rs). - pros & cons: no need to pull the whole `opendal`. but the code is maintained seperatedly. - maintain the fuzz target in `openadal` project, just like [flate2-rs](https://github.com/rust-lang/flate2-rs/blob/main/fuzz/fuzz_targets/fuzz_gz_roundtrip.rs). - pros & cons: easy to maintain it for us. but during the building, it may need to pull all opendal. some stroage and network cost happens here. 4. Then make the whole workflow work. There are some problems for the whole workflow integration: - Contact for oss-fuzz org. AFAIK, oss-fuzz side needs one contact who is really charge of this project. I think it should be the problem for communication and collaboration. let us see how to resolve it. - issue tracking. As oss-fuzz said, finally they will create one issue like JIRA ticket staff for us to reminder that we need to fix related problem. We may need to design one proper workflow to track these issues. - issue fixing. Same to above, we may give one proper workflow to know the issue, fix the issue and remind oss-fuzz side we have finished issue. i just review the process roughly, so the plan may not be correct. Feel free to correct me and let me know your concern if you have. For me i am free to seek the another issue is suitable for me to work with if this issue has been assigned to someone from OSPP activity. thank you again for your help. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
