Release, documentation and so on #3
Description
Like the other projects, an issue template would be required to point people mostly torwards the "server" repository, as the number of issues here are very likely to oncurr, same would be for a PR template if any.
A CI would definitly be a good use to allow:
- Check if it does compile with both the configurations
- A simple CI that performs tagged releases of the offline proxy (in Release mode) to further simplify patch installation for end users.
NOTE as always: decompfrontier will not produce a valid .appx in this place, perhaps a separate repo or a strategy like that MUST be investigated for producing .appx, knowing well that in Microsoft scheme a Custom APPX signed by us can potentially be a security violation of the end user (eg: If our private key gets leaked malicious people can produce APPX malwares that can be accepted as trusted by the system), something like this would also put us in line to be responsable for securely holding the APPX certificate and inform all our users about ceritifcate leaks and so on, which is something I definitly want to refrain from doing.
I would much rather have a "place" where a script would generate the required steps to patch the APPX certificate and generate a local cert in the user machine, of course a project like this would never get an official MsStore certificate by Ms itself as we are not approved/endorsed by gumi