Re: Some suggestions and questions

["Mark Brown" <broonie@kernel.org>]

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

On Thu, Dec 13, 2018 at 09:29:09AM -0600, Dan Rue wrote:
> On Thu, Dec 13, 2018 at 12:34:57PM +0000, Mark Brown wrote:
> > On Thu, Dec 13, 2018 at 07:14:34AM -0500, Mike Holmes wrote:

> > It'll get passed through but clients don't know to do anything with it,
> > you either get noise characters in the subject if people hashtag words
> > that are already there (which is a common way of doing these things),
> > it's less of an issue if they just get added to the end of the subject
> > line but still looks weird.  It's like when people start randomly adding
> > @ to people's names in e-mail.

> I think we should try the hashtag - I'll make next week's meeting
> minutes thread with subject Meeting #Minutes for YYYY-MM-DD. Then, we'll
> end up with a linkable archive of meeting minutes at
> https://groups.io/g/kernelci/hashtags, which should obviate the need for
> opening up the shared google doc.

If we're going to do it could we do it with a #minutes at the end of the
subject instead so that it doesn't disrupt the actual subject?

Since people read more by pattern matching the shapes of text than by
parsing out the individual letters (particularly when reading at speed)
it's not great to have them in the middle of text, this works a lot
better in systems that support hashtags since they tend to provide
visual cues that this isn't a normal word and even there outside of
Twitter with its severe length restrictions they normally get pushed to
a separate bit after the real text (Instagram used to encourage people
to put them in comments, not even in the actual post).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]