Yep, I don't think that's a problem to trim it!

Just one thing I noticed, the Facebook post didn't seem to tag "Google Summer of Code". You might need to edit the post, and type "@Google Summer of Code" manually until it pops up as a selection.

--
Cheers,
Justin W. Flory
[email protected]

On 04/27/2016 08:30 AM, Ryan Lerch wrote:
done!

had to trim the twitter one down a bit though. hope that is ok.

cheers,
ryanlerch

On Wed, Apr 27, 2016 at 10:20 PM, Ryan Lerch <[email protected]
<mailto:[email protected]>> wrote:

    i'm on it, posting now

    On Wed, Apr 27, 2016 at 9:55 PM, Justin W. Flory <[email protected]
    <mailto:[email protected]>> wrote:

        Hey all,

        Today, we made our own announcement about Google Summer of Code
        2016 and the students who will be participating in Fedora over
        the summer.


        
https://communityblog.fedoraproject.org/fedora-google-summer-of-code-2016/

        Here are some social media blurbs to go along with them:

        *Facebook / Google+*: Fedora is pleased to announce the Class of
        2016 for @Google Summer of Code! We have ten students who will
        be working on various parts of Fedora this summer.
        
https://communityblog.fedoraproject.org/fedora-google-summer-of-code-2016/

        *Twitter*: Introducing the @gsoc Class of 2016 for Fedora! Meet
        our students who will be working on Fedora over the summer.
        
https://communityblog.fedoraproject.org/fedora-google-summer-of-code-2016/

        --
        Cheers,
        Justin W. Flory
        [email protected] <mailto:[email protected]>


        --
        marketing mailing list
        [email protected]
        <mailto:[email protected]>
        
http://lists.fedoraproject.org/admin/lists/[email protected]





--
marketing mailing list
[email protected]
http://lists.fedoraproject.org/admin/lists/[email protected]


Attachment: signature.asc
Description: OpenPGP digital signature

--
marketing mailing list
[email protected]
http://lists.fedoraproject.org/admin/lists/[email protected]

Reply via email to