public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	EDK II Development <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: EDK2 documents and wiki
Date: Thu, 12 Nov 2020 04:20:55 +0000	[thread overview]
Message-ID: <BL0PR11MB32363B04597F4F9B1D0A53A5D2E70@BL0PR11MB3236.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB7PR08MB32609649B648C7B20BEDE7F090E80@DB7PR08MB3260.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]

Hi Samer,

I would prefer to see a PDF instead of a Word doc if PDF is available.

I agree that https://github.com/tianocore-docs/Docs is the right repo.

We do not use PRs on that repo.  If you create a personal fork of the Docs repo and add a branch with your new documents, you can send a review email with a link to your branch instead of patch review email with the entire document.

The markdown documents in tianocore-docs use the patch review email process.

Mike


From: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Sent: Wednesday, November 11, 2020 1:50 PM
To: EDK II Development <devel@edk2.groups.io>; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: EDK2 documents and wiki

I have a question on updating EDK2 documents and wiki.

I am trying to upload the SCT documents (contributed from UEFI Forum) to TianoCore Github and website. These are currently PDF and Word documents, so not suitable to be stand-alone markdown repos in  https://github.com/tianocore-docs<https://github.com/tianocore-docsf> yet (like what is happening wiht the other specs). It seems that, at least for now, the best location as far as I can tell is:


  1.  Add the raw PDF /Word (ZIP) documents to https://github.com/tianocore-docs/Docs/tree/master/User_Docs
  2.  Update https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-User-Documentation to point to the raw documents


For (1), should I send a patch to the list, or simply create a pull request with the files? I ask because I see a pull request pending since 2018 😊 (https://github.com/tianocore-docs/Docs/pull/1)

I assume for (2) I need to send a patch to the list, once (1) are uploaded.

Thanks,
--Samer
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 46391 bytes --]

      reply	other threads:[~2020-11-12  4:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 21:49 EDK2 documents and wiki Samer El-Haj-Mahmoud
2020-11-12  4:20 ` Michael D Kinney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BL0PR11MB32363B04597F4F9B1D0A53A5D2E70@BL0PR11MB3236.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox