public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Twitter account
Date: Thu, 11 May 2017 17:02:58 +0100	[thread overview]
Message-ID: <59148B32.2080308@codethink.co.uk> (raw)
In-Reply-To: <d39a8292-6c33-4c15-a4f2-17adc13e5e98@siemens.com>

Hi,

On 31/03/17 12:05, Wolfgang Mauerer wrote:
> Hi all,
>
> On 31.03.2017 12:51, Agustin Benito Bethencourt wrote:
>> On 31/03/17 11:26, Wolfgang Mauerer wrote:
>>> On 30.03.2017 15:33, Noriaki Fukuyasu wrote:
>>>>
>>>> I think this is a great idea.
>>>> The challenge is how to manage the posts (who, what and how often etc).
>>>> Anyway, let me think over this.
>>>
>>> marketing and creating public awareness of our endeavour is
>>> of course good -- keeping up regular activity is going to be the
>>> hard thing. But if we publish
>>>
>>> * new software releases (board at desk, kernel)
>>> * member presentations at conferences
>>
>> The above will allow us to have one tweet per month which is not a bad
>> start. I prefer less tweets but relevant than a lot of noise.
>>
>>>
>>> we should at least have some base activity. I'm wondering, though,
>>> what we intend to achieve with the account? (except that everybody
>>> needs to have a Twitter account these days, as it seems :))
>>
>> This is always a good question.
>>
>> We can focus on:
>> 1.- Increase the number of developers subscribed to our mailing list.
>> 2.- increase the number of developers subscribed to our #IRC channel.
>> Currently we have around 20 people.
>> 3.- Increase the number of downloads of our materials: VM images
>> (tools), slides from conferences.
>> 4.- Increase the viewers of the videos of our conferences.
>>
>> All the above objectives can be measurable together with the influence
>> that twitter has on them so we can determine goals for 2018 based on the
>> numbers we get in this first 2017.
> ... which suggests that we should also do after-conference tweets once
> any materials (slides, videos) have been published.
>
> Thanks, Wolfgang
>>
>>>
>>> Thanks, Wolfgang
>>>>
>>>> regards
>>>>
>>>> Nori
>>>>
>>>>
>>>> On Wed, Mar 29, 2017 at 10:53 PM, Agustin Benito Bethencourt
>>>> <agustin.benito@codethink.co.uk
>>>> <mailto:agustin.benito@codethink.co.uk>>
>>>> wrote:
>>>>
>>>>     Hi,
>>>>
>>>>     maybe we can start the support of our promo efforts with a Twitter
>>>>     account. I would also think about a hashtag

I would like to bring back this topic now that the B at D release is coming 
and we will have a strong presence at OSSJ.

Possible names:
* @lfcip (taken)
* @civilip
* @civilOS (taken)
* @OScip (taken)
* @projectcip


Suggestions?

>>>>
>>>>     Best Regards
>>>>
>>>>     --
>>>>     Agustin Benito Bethencourt
>>>>     Principal Consultant - FOSS at Codethink
>>>>     agustin.benito at codethink.co.uk
>>>> <mailto:agustin.benito@codethink.co.uk>
>>>>     _______________________________________________
>>>>     cip-dev mailing list
>>>>     cip-dev at lists.cip-project.org
>>>> <mailto:cip-dev@lists.cip-project.org>
>>>>     https://lists.cip-project.org/mailman/listinfo/cip-dev
>>>>     <https://lists.cip-project.org/mailman/listinfo/cip-dev>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Noriaki Fukuyasu
>>>>
>>>> The Linux Foundation
>>>> Mail: fukuyasu at linuxfoundation.org
>>>> <mailto:fukuyasu@linuxfoundation.org>
>>>> Tel: +81-80-4350-1133
>>>> Twitter: nori_fukuyasu
>>>> Facebook: linuxfoundationjp
>>>>
>>>> Please visit our web sites:
>>>> http://www.linuxfoundation.jp
>>>> http://events.linuxfoundation.jp
>>>> http://jp.linux.com
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cip-dev mailing list
>>>> cip-dev at lists.cip-project.org
>>>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>>>>
>>> _______________________________________________
>>> cip-dev mailing list
>>> cip-dev at lists.cip-project.org
>>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>>>
>>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

  reply	other threads:[~2017-05-11 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 13:53 [cip-dev] Twitter account Agustin Benito Bethencourt
2017-03-30 13:33 ` Noriaki Fukuyasu
2017-03-31  9:26   ` Wolfgang Mauerer
2017-03-31 10:51     ` Agustin Benito Bethencourt
2017-03-31 11:05       ` Wolfgang Mauerer
2017-05-11 16:02         ` Agustin Benito Bethencourt [this message]
2017-05-12  2:54           ` KOBAYASHI Yoshitake
2017-05-12  8:05             ` Chris Paterson
2017-05-12  8:43               ` Agustin Benito Bethencourt
2017-05-12  9:41                 ` KOBAYASHI Yoshitake

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=59148B32.2080308@codethink.co.uk \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox