All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Bart Van Assche <bvanassche@acm.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: Meeting about the UFS driver
Date: Tue, 12 Oct 2021 18:59:10 -0400	[thread overview]
Message-ID: <YWYTPnEBGatnfmO4@mit.edu> (raw)
In-Reply-To: <bb051910-43cd-9007-9267-3579765137cb@acm.org>

On Tue, Oct 12, 2021 at 11:05:55AM -0700, Bart Van Assche wrote:
> That document has been created using my work account. Recently my employer
> changed the settings for work documents such that even read-only access has
> to be granted explicitly. Making a document viewable without authentication
> is no longer supported. I am considering next time I use Google Docs to
> prepare a meeting to use my personal gmail account since making documents
> public from a personal account is still supported.

Yeah, that would be my strong recommendation.  My employer has the
same restriction and I similarly will make sure that I create such
documents using my personal gmail account and then share Editor status
with my work account so I can more easily edit it from my work account
if necessary.

If you have a document that was created with your work account, the
procedure to "transfer" it over to your personal account is:

* If necessary, remove any work-proprietary information from the
  document; you can revert that change at the end of this procedure
  if you want the work version of the document to have internal
  information in it
* share the document with your personal account
* open the document with your personal account
* select File->Make a copy to make a copy of that document
  which is owned by your personal account
* Rename the copy so that it has something thing like (PUBLIC)
  in the the name so you can easily disambiguate the public
  version from the work version.
  OR, delete the work version of the document so you don't end
  up confusing yourself.
* Enable link sharing on the public version of the document

If you've ever wondered why the document which you can reach via the
URL https://thunk.org/gce-xfstests has "(public)" in the title, that's
why....

It's a bit more work for you, but it makes much life much easier for
everyone else trying to access the document.

Cheers,

					- Ted

  parent reply	other threads:[~2021-10-12 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 17:29 Meeting about the UFS driver Bart Van Assche
2021-10-12 17:42 ` James Bottomley
2021-10-12 18:05   ` Bart Van Assche
2021-10-12 18:16     ` James Bottomley
2021-10-12 22:59     ` Theodore Ts'o [this message]
2021-10-12 23:17       ` Bart Van Assche

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-all 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=YWYTPnEBGatnfmO4@mit.edu \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bvanassche@acm.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.