[kdenlive] being social

[Jesse DuBord]

Hey Farid. Of course! I'll add you and Dive-o right away.

I think Twitter would be a good thing, if possible. If the kdenlive user 
was @kdenlive, that would have been nice to grab a hold of. If we can't 
get it back, there are all sorts of other variations that might work, too.

That said, regarding G+, is it alright if I create another header image 
for the G+ community with the new logo, or should I wait until the 
official release of 16.08?

On 07/27/2016 05:00 AM, kdenlive-request at kde.org wrote:
> Send kdenlive mailing list submissions to
> 	kdenlive at kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mail.kde.org/mailman/listinfo/kdenlive
> or, via email, send a message with subject or body 'help' to
> 	kdenlive-request at kde.org
>
> You can reach the person managing the list at
> 	kdenlive-owner at kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kdenlive digest..."
>
>
> Today's Topics:
>
>     1.  being social (farid abdelnour)
>     2. Re:  being social (Narcis Garcia)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 26 Jul 2016 18:59:13 -0300
> From: farid abdelnour <snd.noise at gmail.com>
> To: kdenlive <kdenlive at kde.org>
> Subject: [kdenlive] being social
> Message-ID:
> 	<CAHMxv36O=OWvbU5KYO9RFWBrSz2G=U=xuWcEfpwb8mtidHw0fA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> hello,
>
> there was recently an attempt to get the twitter account for kdenlive back
> but afaik it didn't go well... we could either try to contact twitter and
> ask to get it back or create another one.
>
> over at the g+ community jesse created a community and it is doing fairly
> well. :) i would like to ask if possible to put me and dive-o (if he
> accepts) as admins as well. is that ok?
>
> another thing that has been on my mind is if we should be on github. the
> plus side is that it might make it easier for more devs to join in probably
> the bad side (besides being proprietary) is that it would be one more thing
> to have to take care of... any thoughts on this?
>
> cheers
>
>
>