From c2a144078618c786b49569523ae6b4572fa5c041 Mon Sep 17 00:00:00 2001 From: lkcl Date: Sun, 30 Apr 2023 11:06:06 +0100 Subject: [PATCH] --- openpower/sv/rfc.mdwn | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/openpower/sv/rfc.mdwn b/openpower/sv/rfc.mdwn index 484d178ce..cf55bde09 100644 --- a/openpower/sv/rfc.mdwn +++ b/openpower/sv/rfc.mdwn @@ -7,14 +7,17 @@ written and submitted to the [OpenPOWER Foundation ISA TWG](https://openpower.foundation/groups/isa/). They are not part of the official Power ISA unless ratified by the OPF ISA TWG. -[Power ISA is Trademarked](https://trademarks.justia.com/789/79/power-78979814.html). +[Power ISA is Trademarked](https://trademarks.justia.com/789/79/power-78979814.html) +and use of the ISA covered by an +[Open EULA](https://openpowerfoundation.org/blog/final-draft-of-the-power-isa-eula-released/) Draft unofficial proposals in PDF form may be found on the [Libre-SOC FTP site](https://ftp.libre-soc.org/opf_ext_rfc) -Constructive Feedback on Draft Proposals is best discussed on the +Constructive Feedback on Libre-SOC Draft Proposals is best discussed on the [Libre-SOC ISA mailing list](http://lists.libre-soc.org/mailman/listinfo/libre-soc-isa). Note that once RFCs are formally submitted, involvement in their discussion within the OPF ISA TWG first requires OPF Membership, and once joined a request to be submitted to join the ISA TWG. +Actual submission of an External RFC however does **not** require OPF Membership. To add a new RFC, take a copy of an existing RFC and use it as a template, ensure to keep the '''opf_rfc''' tagging so that the RFC appears -- 2.30.2