If you don't trust your machine to build release packages, that's fine. It quite clearly doesn't prohibit you from contributing like you have already been doing, by providing patches and updates, which are then built on other machines.
The change would just mean you provide these patches in a more official position as a member of the team, and we can mark your contributions as such by having you be the one to commit them to the repository, and/or signing off the commits. -A On Mon, Nov 25, 2019 at 11:55:11AM +0000, grizzlyuser wrote: > On Saturday, November 23, 2019 7:04 PM, bill-auger > <[email protected]> wrote: > > > i had the same thought recently too - grizzlyuser has also been > > very helpful > > It's very pleasant to see myself mentioned in this thread! Seing > dedication of Parabola hackers to the project inspired me to do > my small contributions. I'd be happy to be more involved. > > However I'm not sure if it'd be appropriate for me to package > anything, because my laptop contains Intel Management Engine. > It's not clear if there's any practical need for IME to mess > with built binaries / packages. Although manufacturer (Dell) > claims ME is disabled in my configuration, intelmetool utility > says otherwise, and I haven't yet taken the risk of bricking my > only computer by using me_cleaner to neutralize IME. > _______________________________________________ > Dev mailing list > [email protected] > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ my GPG Public Key: https://files.grapentin.org/.gpg/public.key ------------------------------------------------------------------------------
signature.asc
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] https://lists.parabola.nu/mailman/listinfo/dev
