OASIS PKCS 11 TC

 View Only

  • 1.  Please read: Fwd: [TC Admin] Question re: GitHub

    Posted 20 days ago
    Hi folks

    I reached out to TC Admin regarding PRs from non-TC members.  Note: we should reject these PRs and redirect non-TC members to submit feedback in other ways (comment list). Please see full response below.

    Valerie
    PKCS#11 Co-Chair

    Begin forwarded message:

    From: "Claudia Rauch (OASIS)" <claudia.rauch@oasis-open.org>
    Subject: Re: [TC Admin] Question re: GitHub
    Date: October 29, 2025 at 3:31:47 AM MST
    Cc: Robert Relyea <rrelyea@redhat.com>, Dieter Bong <Dieter.Bong@utimaco.com>, Kelly Cullinane <kelly.cullinane@oasis-open.org>

    Hi Valerie,

    Apologies for the late response.

    The type of GitHub repo you cite is the "Github for TC" type, intended only to accept PRs from TC members, as it says in its CONTRIBUTING.md file.  We have a members-only rule for PRs into those repos because the repo is intended not as a comment facility, but as an alternate place for the TC itself to do its work.  All such repo contents can "safely" be included in a spec draft, because all are protected by the IPR license promises that the TC members already have made.  

    As the CONTRIBUTING.md file says, non-TC-members should be asked to re-submit any specific material changes through either our Feedback License system, so that OASIS and the TC acquire adequate rights to use the contribution, or as a Github Issue, which does not assert any licensure.

    As a practical matter:   
    • Nonmembers who send in a PR might be politely directed to the CONTRIBUTING.md file, or to the Github Issue facility (which offers ideas to our TC, but does not get directly merged into a spec draft).  
    • A maintainer might look at such an Issue, do whatever consultation or issue voting is needed, and then reply:  Dear issue submitter, we like this idea, please send any text or details that you wish to offer into our Feedback License portal, so we have the rights to use it. 

    The mailing list address for comments is:  OASIS-pkcs11-comment@ConnectedCommunity.org

    Hope this helps. Kind regards,
    Claudia

    On Mon, Oct 20, 2025 at 11:50 PM 'Valerie Fenwick' via TC Administration <tc-admin@oasis-open.org> wrote:
    HI Folks!


    Which does cover non-TC members raising GH Issues, but I do not see any coverage for non-TC members raising PR (Pull Requests).

    We are starting to receive PRs from non-TC members, and would like official guidance from OASIS to be sure we are complying with policies.

    Thank you!

    Valerie


    --

    Claudia Rauch

    Open Projects Program Manager
    OASIS Open
    		   
    Pronouns:
    		She/Her
    Timezone:
    		GMT+1
    Website:
    		www.oasis-open.org



  • 2.  RE: Please read: Fwd: [TC Admin] Question re: GitHub

    Posted 20 days ago

    Perhaps we should create PR and Issues templates that clearly state this policy, so that it is very clear if someone tries to create a PR that it will end up being closed ?



    ------------------------------
    Simo Sorce
    Red Hat
    ------------------------------

    Original Message


  • 3.  RE: Please read: Fwd: [TC Admin] Question re: GitHub

    Posted 20 days ago
    Simo 

    I think that is a great idea. Would someone like to propose language for the template?   Note, this is also covered in our Contributing file (https://github.com/oasis-tcs/pkcs11/blob/master/CONTRIBUTING.md) (not that everyone reads that, lol)

    Valerie

    On Nov 4, 2025, at 11:16 AM, Simo Sorce via OASIS <Mail@mail.groups.oasis-open.org> wrote:





    Original Message


  • 4.  RE: Please read: Fwd: [TC Admin] Question re: GitHub

    Posted 20 days ago
    I think a template would be good I have created two now for issue #19 external Mu sign and Mu generation probably not up to scratch even as a member.

    Hamish

    Sent from Outlook for iOS



    Original Message


Related Content