Re: Twitter account


Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 12/05/17 09:05, Chris Paterson wrote:
Hello,

From: cip-dev-bounces@... [mailto:cip-dev-
bounces@...] On Behalf Of KOBAYASHI Yoshitake
Sent: 12 May 2017 03:55
Hi Agustin,

If LF has already acquired an account for CIP and can be shared in this project,
I think this is the best option. If not, how about @cip_project?
Sounds good to me.
Either that one or @cip-project would work. I have no strong preference.


Kind regards, Chris


Best regards,
Yoshi


On 2017/05/12 1:02, Agustin Benito Bethencourt wrote:
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@...
<mailto:agustin.benito@...>>
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@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@...
<mailto:agustin.benito@...>
_______________________________________________
cip-dev mailing list
cip-dev@...
<mailto:cip-dev@...>
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@...
<mailto:fukuyasu@...>
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@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...

Join {cip-dev@lists.cip-project.org to automatically receive all group messages.