Index
Subject
: [lug] Digest (5 messages)
From
: lug-owner@lists.ncsu.[redacted]
Date
: Sat, 10 Sep 2016 21:06:14 -0400
The Lug Digest
Volume 1 : Issue 389 : "text" Format
Messages in this Issue:
201609/14 : Re: Business and Updates
Quentin Young <qlyoung@ncsu.[redacted]>
201609/15 : Re: Fwd: FW: Event with Facebook Production Engineering | Week
of 9/12?
Antonious Iskander <amiskand@ncsu.[redacted]>
201609/16 : opensource.ncsu.edu software stack
Neill Robson <nlrobson@ncsu.[redacted]>
201609/17 : Re: opensource.ncsu.edu software stack
Quentin Young <qlyoung@ncsu.[redacted]>
201609/18 : Re: opensource.ncsu.edu software stack
Vaclav Petras <vpetras@ncsu.[redacted]>
----------------------------------------------------------------------
Date: Mon, 5 Sep 2016 22:17:23 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Business and Updates
Message-ID: <CANhSzx2Vt1ye3F8N8zirAMBH+iAWtqrPO9eK8TJ1p100eMj5yA@mail.gmail.[redacted]>
Great, thank you. If we end up with this Google group I think they have
integrated calendars but until then I'll use that.
On Mon, Sep 5, 2016 at 8:51 PM, Brian Cottingham <spiffytech@gmail.[redacted]>
wrote:
> Quentin, I granted you admin access to the LUG event calendar we used on
> the old website. I didn't realize future SCs weren't passing it on.
>
> Feel free to use something else if you consider it appropriate.
>
> On Mon, Sep 5, 2016 at 2:30 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>
>> Hi LUG,
>>
>> Some updates:
>>
>> - As per Neill's announcement, tomorrow we'll be having our first
>> hack day to work on organizing char and short and get some brainstorming
>> for what we want to do with opensource.ncsu.edu. Looking forward to
>> this!
>> - I have been in communication with Facebook and we're working on
>> scheduling 9/14 at 7:00 as the date and time for their Prod. Eng. team to
>> host an event, hopefully with food :-)
>> - I'm working on putting together a Google Calendar for the group,
>> which segues into the next point:
>>
>> I propose setting up a Google Group on our NCSU Google Apps instance.
>> Someone suggested it to me recently, I looked into it, and I think it would
>> give us a much better way to manage group communications, maintain a
>> roster, a shared calendar, manage emails and the mailing list, and other
>> goodies. NCSU's Majordomo instance, to my understanding, is being phased
>> out in favor of GApps for email communication internally, and I think this
>> is a good path for us as well.
>>
>> If there are any suggestions or concerns I'd love to hear them. If anyone
>> has a better idea for a collaboration tool, I think some characteristics
>> we're looking for are:
>>
>> - Long lived -- will exist independently of the members of the group
>> and across infrastructure changes
>> - Integrates email -- people shouldn't have to make an account to
>> gain access, so we can keep in touch with LUG affiliates who may not be
>> NCSU students or faculty
>> - Easy way to manage members, preferably tied to @ncsu.edu accounts
>>
>> I thought about some self-hosted project management tools, which we could
>> absolutely host on one of our servers, as well as hosted ones like Slack
>> (which the CSEC club here uses), but I think Google Groups strikes the best
>> balance. In any case I'd love to hear your thoughts.
>>
>> Best,
>> --
>> Quentin Young
>> President, LUG @ NC State
>>
>
>
--
Quentin Young
President, LUG @ NC State
[Attachment of type text/html removed.]
------------------------------
Date: Tue, 6 Sep 2016 14:53:42 -0400
From: Antonious Iskander <amiskand@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Fwd: FW: Event with Facebook Production Engineering | Week
of 9/12?
Message-ID: <CAFAjCZOUgUhGZqx-eFZLN7kZNfe=qDr-Dn1kTTQrqNw_hPuMcQ@mail.gmail.[redacted]>
I might be able to make it to this event on the 14th.
On Sat, Sep 3, 2016 at 12:59 AM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
> Since Wednesday works for me, Neill and Stephen I guess we'll go with
> Wednesday.
>
> On Sep 2, 2016 3:39 PM, "Stephen Worley" <seworley@ncsu.[redacted]> wrote:
>
>> I can probably do either.
>>
>> On Sep 1, 2016 9:58 PM, "Quentin Young" <qlyoung@ncsu.[redacted]> wrote:
>>
>>> Regular meeting hours, 7-8.
>>>
>>> On Sep 1, 2016 9:46 PM, "Mitchell Rees-Jones" <mwreesjo@ncsu.[redacted]> wrote:
>>>
>>>> What time of day would it be?
>>>>
>>>>
>>>>
>>>> ––––
>>>>
>>>> *Mitch Rees-Jones*
>>>>
>>>>
>>>> North Carolina State University -* Class of 2018*
>>>> North Carolina School of Science and Mathematics -* Class of 2014*
>>>> reesjones.github.io
>>>> :wq
>>>>
>>>> On Thu, Sep 1, 2016 at 5:47 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>>>
>>>>> Well folks? 9/12 or 9/14? I inquired about holding the event during
>>>>> normal meeting hours, but unfortunately they're having an event at Duke
>>>>> that night.
>>>>>
>>>>> My vote is for Monday, 9/12.
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Jamie Lewis <jlew@fb.[redacted]>
>>>>> Date: Wed, Aug 31, 2016 at 12:16 AM
>>>>> Subject: FW: Event with Facebook Production Engineering | Week of 9/12?
>>>>> To: "qlyoung@ncsu.[redacted]" <qlyoung@ncsu.[redacted]>
>>>>>
>>>>>
>>>>> Hi Quentin,
>>>>>
>>>>>
>>>>>
>>>>> Great chatting with you earlier! I must admit IRC looks quite
>>>>> different from Facebook Messenger. Just let me know if *Monday, 9/12*
>>>>> or *Wednesday, 9/14* might work for your group after you have a
>>>>> chance to chat with them. I’m happy to provide dinner and would welcome
>>>>> suggestions on where get delivery from as I’m sure you get a lot of pizza
>>>>> from employers. J
>>>>>
>>>>>
>>>>>
>>>>> Looking forward to working with you…
>>>>>
>>>>>
>>>>>
>>>>> *Jamie Lewis*
>>>>>
>>>>> University Recruiter
>>>>>
>>>>> *M:* (XXX) 441-0602
>>>>>
>>>>>
>>>>>
>>>>> facebook.com/careers
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From:* Jamie Lewis
>>>>> *Sent:* Friday, August 26, 2016 10:56 PM
>>>>> *To:* 'linux-users-group@ncsu.[redacted]' <linux-users-group@ncsu.[redacted]>
>>>>> *Subject:* Event with Facebook Production Engineering | Week of 9/12?
>>>>> *Importance:* High
>>>>>
>>>>>
>>>>>
>>>>> Hi NCSU LUG,
>>>>>
>>>>>
>>>>>
>>>>> I’m a recruiter with Facebook’s Production Engineering
>>>>> <https://www.facebook.com/facebookcareers/videos/1747855735501113/>
>>>>> team and I wanted to know if your student group would be interested in
>>>>> doing an event with us during the week of 9/12? Our org has partnered with
>>>>> other LUG’s at various universities and we’ve found that there is often
>>>>> lots of synergy between your passions and areas of focus and our team. We
>>>>> have a couple different options in terms of content we could deliver that
>>>>> would include anything from tech talks to live problem solving using
>>>>> something we call a “Linux Challenge”.
>>>>>
>>>>>
>>>>>
>>>>> Please let me know if this is something you might be interested in as
>>>>> I’d love to connect with you via phone to talk through logistics and gather
>>>>> more information on your club.
>>>>>
>>>>>
>>>>>
>>>>> Cheers to future partnerships! J
>>>>>
>>>>>
>>>>>
>>>>> *Jamie Lewis*
>>>>>
>>>>> University Recruiter
>>>>>
>>>>> *M:* (XXX) 441-0602
>>>>>
>>>>>
>>>>>
>>>>> facebook.com/careers
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Quentin Young
>>>>> President, LUG @ NC State
>>>>>
>>>>
>>>>
[Attachment of type text/html removed.]
[Attachment of type image/png removed.]
------------------------------
Date: Sat, 10 Sep 2016 15:19:52 -0400
From: Neill Robson <nlrobson@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: opensource.ncsu.edu software stack
Message-ID: <2e1b6927-1c46-bd5a-88ea-f2d43a505333@ncsu.[redacted]>
Hey everyone!
For those of you who missed the last meeting, our major focus was
getting oriented for the opensource.ncsu.edu website project. Our rough
mission statement for the website is *to promote free and open-source
software through accessible online educational resources*.
Content might include, but not be limited to:
* Getting started using Linux as a student, artist, developer, young
professional, etc.
* How to contribute to an open-source community
* Aggregate list of useful FOSS for office use, home media,
programming, etc.
* Aggregate list of conventions, communities, and hackathons in which
to get involved
* Weekend project tutorials (build your own Linux distro, design and
host a resume website on an open-source stack, make an animation in
Blender...)
The general consensus was that this website would work best in a Wiki
format, with a focus on a friendly and accessible interface for
non-technical visitors.
Over the next month or so, I will be spending a bit of time designing
the structure and style of this site. To some extent, *the
implementation of the design is dependent on the technologies used to
build and serve the website*, so I wanted to bring this question up
again for discussion.
For Wiki-based content, we decided at Tuesday's meeting that *static
generation is the way to go*. There are numerous open-source solutions
to choose from (see http://www.staticgen.com/).
Our blog (http://lug.ncsu.edu/) is built on Jekyll currently. Now,
Jekyll is primarily used for blogs, but looking at recent features (such
as collections: https://jekyllrb.com/docs/collections/) and sites built
with Jekyll (such as the docs themselves!), I am led to believe that
*Jekyll could be sufficient for our goals this semester*. Furthermore,
using a single consistent tool across all (two) of our websites would
minimize the difficulty of getting new members acquainted with
contributing.
But don't just take my word for it! *What are your opinions on the best
static-site generation solution for our purposes?* Feel free to discuss
alternatives either on the mailing list or on IRC. I'll try to hop on
this evening and join in on any discussion!
Have a great weekend, everyone. See you all on Wednesday for Facebook's
recruiting event! Don't forget to bring a Linux laptop!
[Attachment of type text/html removed.]
------------------------------
Date: Sat, 10 Sep 2016 15:28:02 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: opensource.ncsu.edu software stack
Message-ID: <CANhSzx3G7X2MU+RoZ5-shRa_TJGeFw2S5rwdNTt6XwDXNnUkOg@mail.gmail.[redacted]>
My vote is also for Jekyll. I think that since Jekyll expects content in
Markdown, this allows us to make content agnostic of any particular stack,
leaving the door open for an easy port if we want to move to something else
in the future. But I believe we can go really far with Jekyll.
For those who didn't see the Google doc we're using to plan:
https://docs.google.com/a/ncsu.edu/document/d/1LxyJWX0RGabOSJnnrwOUTViDyMUPf9w1Y3eUjAO_kSE/edit?usp=sharing
Looking forward to others' input!
On Sat, Sep 10, 2016 at 3:19 PM, Neill Robson <nlrobson@ncsu.[redacted]> wrote:
> Hey everyone!
>
> For those of you who missed the last meeting, our major focus was getting
> oriented for the opensource.ncsu.edu website project. Our rough mission
> statement for the website is *to promote free and open-source software
> through accessible online educational resources*.
>
> Content might include, but not be limited to:
>
> - Getting started using Linux as a student, artist, developer, young
> professional, etc.
> - How to contribute to an open-source community
> - Aggregate list of useful FOSS for office use, home media,
> programming, etc.
> - Aggregate list of conventions, communities, and hackathons in which
> to get involved
> - Weekend project tutorials (build your own Linux distro, design and
> host a resume website on an open-source stack, make an animation in
> Blender...)
>
> The general consensus was that this website would work best in a Wiki
> format, with a focus on a friendly and accessible interface for
> non-technical visitors.
>
> Over the next month or so, I will be spending a bit of time designing the
> structure and style of this site. To some extent, *the implementation of
> the design is dependent on the technologies used to build and serve the
> website*, so I wanted to bring this question up again for discussion.
>
> For Wiki-based content, we decided at Tuesday's meeting that *static
> generation is the way to go*. There are numerous open-source solutions to
> choose from (see http://www.staticgen.com/).
>
> Our blog (http://lug.ncsu.edu/) is built on Jekyll currently. Now, Jekyll
> is primarily used for blogs, but looking at recent features (such as
> collections: https://jekyllrb.com/docs/collections/) and sites built with
> Jekyll (such as the docs themselves!), I am led to believe that *Jekyll
> could be sufficient for our goals this semester*. Furthermore, using a
> single consistent tool across all (two) of our websites would minimize the
> difficulty of getting new members acquainted with contributing.
>
> But don't just take my word for it! *What are your opinions on the best
> static-site generation solution for our purposes?* Feel free to discuss
> alternatives either on the mailing list or on IRC. I'll try to hop on this
> evening and join in on any discussion!
>
> Have a great weekend, everyone. See you all on Wednesday for Facebook's
> recruiting event! Don't forget to bring a Linux laptop!
>
--
Quentin Young
President, LUG @ NC State
[Attachment of type text/html removed.]
------------------------------
Date: Sat, 10 Sep 2016 21:05:51 -0400
From: Vaclav Petras <vpetras@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: opensource.ncsu.edu software stack
Message-ID: <CAJeX9NraYd=+KzcgaJ2-or-dh-d_n-i9UPo2eAhExKyRXMUpEw@mail.gmail.[redacted]>
For opensource.ncsu.edu, I also suggest maintaining list of groups,
websites and/or points of contacts to other groups doing open source in
some way at NCSU. Our group, NCSU GeoForAll Lab, focused on open source
geospatial software, has some list but we are not really doing that much to
keep it up to date (as you can see from the broken links):
https://geospatial.ncsu.edu/osgeorel
https://geospatial.ncsu.edu/osgeorel/about.html (at the very bottom)
[Attachment of type text/html removed.]
------------------------------
End of [lug] Digest (5 messages)
**********