Re: BuildStream Twitter account

[Agustín Benito Bethencourt <agustin benito codethink co uk>]

Hi,

On Wednesday, 9 May 2018 14:19:43 CEST Sander Striker wrote:
> On Wed, May 9, 2018 at 2:07 PM Agustín Benito Bethencourt <
>
> agustin benito codethink co uk> wrote:
> > Hi,
> >
> > On Wednesday, 9 May 2018 13:57:10 CEST Sander Striker wrote:
> > > Not a fan of the _prj.
> > >
> > > How about reserving the bst.build domain and also securing the
> > > @bst.build
> > > Twitter account?
> >
> > * We cannot include a dot in the user name. Please check: https://
> > help.twitter.com/en/managing-your-account/twitter-username-rules
>
> Then lets leave out the dot.
>
> There is some precedence here:
> @bazelbuild, @pantsbuild

The equivalent would be then buildstreambuild which has 16 characters so it 
won't work.

It is the usage of bst instead of buildstream what I think is a mistake from 
the branding perspective. I prefer to dedicate some extra time to find a 
solution including buildstream than going for bst.

> > * bst is only relevant to us, developers/contributors. The Twitter
> > audience
> > goes beyond ourselves.
>
> Right, having the build part doesn't hurt in that respect.  It's certainly
> not worse
> than prj.

You are comparing _prj with build. I agree with you that build is better.

> > * Having the word buildstream in the user name significantly helps when
> > searching for the account. I would use the word in the domain too.
>
> Searching is all about relevance.  If bst.build and @bstbuild are
> sufficiently linked
> together BuildStream will pop up and vice versa.

True but in all cases, having buildstream in the name would be better, which 
is what I think we should aim for.

<snip>

Best Regards


-- 
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd