I'm working on a library to read and write PPM (portable pixmap) images with a simple to use C API. We have two out of three issues that prevented the first version of the library from being released fixed. Only one more issue needs to be resolved before version 1.0 is released.
Another project I've been working on is a C++ implementation of Rust's Enum Type Result. Not all methods found on Result are currently implemented and because of the language differences between C++ and Rust, not everything maps perfectly. If you would like to help me with this project it would be much appreciated.
Hi Noah! libpixmap looks interesting, but I don't see any open issues on the github repo. I understand that you have mentioned them in your README, but for better tracking, you could open issue(s) so that people can get more clarity on the task at hand.
They were placed in the README.md as the three issues blocking the first release of the library. Issues after the release of this library will be placed in the Issues tab.
I haven't thought about adding a Contribution Guide since the project is so small. If someone did create a pull request, I would format their code to my liking.
Hi all!
I'm working on a library to read and write PPM (portable pixmap) images with a simple to use C API. We have two out of three issues that prevented the first version of the library from being released fixed. Only one more issue needs to be resolved before version 1.0 is released.
Link to Github repository: github.com/Noah11012/libpixmap
Another project I've been working on is a C++ implementation of Rust's Enum Type Result. Not all methods found on Result are currently implemented and because of the language differences between C++ and Rust, not everything maps perfectly. If you would like to help me with this project it would be much appreciated.
Link to Github repository: github.com/Noah11012/result-for-cpp
Hi Noah! libpixmap looks interesting, but I don't see any open issues on the github repo. I understand that you have mentioned them in your README, but for better tracking, you could open issue(s) so that people can get more clarity on the task at hand.
They were placed in the README.md as the three issues blocking the first release of the library. Issues after the release of this library will be placed in the Issues tab.
I still don't understand as to how contributors can get more clarity on the issue. At least add a Contribution Guide, indicating -
I haven't thought about adding a Contribution Guide since the project is so small. If someone did create a pull request, I would format their code to my liking.
Cool.