Index

Subject : [lug] Digest (2 messages)

From : lug-owner@lists.ncsu.[redacted]

Date : Mon, 25 Jul 2016 13:41:58 -0400


The Lug Digest
Volume 1 : Issue 379 : "text" Format

Messages in this Issue:
201607/3 : Re: Char has been upgraded
Quentin Young <qlyoung@ncsu.[redacted]>
201607/4 : Re: Char has been upgraded
Neill Robson <nlrobson@ncsu.[redacted]>

----------------------------------------------------------------------

Date: Fri, 22 Jul 2016 11:00:36 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Char has been upgraded
Message-ID: <CANhSzx2UK1aRy8cYawKtpYreNusKseiru8pcCmojFrgYPpqBzQ@mail.gmail.[redacted]>

Not sure what you mean by access for web hosting. All it takes is a running
server and optionally a DNS record to set up a website. For email
addresses, we own the @lug.ncsu.edu domain, but this is still a subdomain
of ncsu.edu, and there are certainly implications there that need to be
taken into account. We could presumably set up multiple DNS records to
point at our email server and configure it for multiple domains but I think
at that point we may start running into regulatory / security issues. I
have never configured an email server.

Additionally, Carlos Benavente, with CSC IT, has informed me of some recent
changes regarding email servers that we will need to comply with. It's not
quite as easy as 'throw up an email server', so if we want to pursue this
route seriously I'd like to see some solid interest by more than a few
members.

On Fri, Jul 22, 2016 at 9:52 AM, Antonious Iskander <amiskand@ncsu.[redacted]>
wrote:

> That's cool. How do we have access to do web hosting? Also, for email
> addresses @lug is fine but can we also customize our own? Thanks.
>
> On Thu, Jul 21, 2016 at 10:53 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>
>> For email addresses I believe we would need to configure an email server.
>> I think that is an option, we can probably offer @lug.ncsu.edu
>> addresses. Will have to check.
>>
>> I'm fine allowing club members web hosting (as we presently do,
>> http://nilbus.com/ is hosted on short).
>>
>> Quentin
>>
>> On Wed, Jun 29, 2016 at 6:13 AM, Antonious Iskander <amiskand@ncsu.[redacted]>
>> wrote:
>>
>>> what about web hosting? or private email addresses?
>>>
>>> On Tue, Jun 28, 2016 at 6:19 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>>
>>>> I think if we hosted a VPN or anonymous web proxy on a University rack
>>>> terminating inside the University network the University would be very
>>>> upset with us. Not an option, I'm afraid.
>>>> On Jun 28, 2016 6:08 PM, "Antonious Iskander" <amiskand@ncsu.[redacted]>
>>>> wrote:
>>>>
>>>>> how about a vpn or an anonomous web proxy?
>>>>>
>>>>> On Mon, Jun 27, 2016 at 10:49 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>> wrote:
>>>>>
>>>>>> I am wrong, students retain IP over their code. However the FAQ does
>>>>>> indeed note:
>>>>>>
>>>>>> *"NCSU GitHub is specifically designed to not compete with Github.com
>>>>>> as far as public offering. “Public” inside of NCSU GitHub is public to the
>>>>>> institution, not the world. If a given project is truly open source, then
>>>>>> it may be more appropriate to host it at GitHub.com with a personal
>>>>>> account."*
>>>>>>
>>>>>> ...or on your friendly neighborhood Linux User Group's hosted git
>>>>>> service :-)
>>>>>>
>>>>>> On Mon, Jun 27, 2016 at 10:03 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>>> wrote:
>>>>>>
>>>>>>> Additionally, I may be wrong on this front, but I recall reading
>>>>>>> somewhere that the University retains many privileges and some form of
>>>>>>> copyright over any code hosted there. If anyone has further information on
>>>>>>> this I'd love to know more, but that's my understanding.
>>>>>>>
>>>>>>> On Mon, Jun 27, 2016 at 10:01 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> NCSU's GitHub Enterprise instance is fully private and requires
>>>>>>>> LDAP authentication with your Unity credentials. Repositories are not
>>>>>>>> world-readable. My vote is still with a hosted Git service.
>>>>>>>>
>>>>>>>> On Sun, Jun 19, 2016 at 6:03 PM, Neill Robson <nlrobson@ncsu.[redacted]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Ah, I had not thought of that! Well, a hosted git service was the
>>>>>>>>> only idea I had, unfortunately.
>>>>>>>>>
>>>>>>>>> On 06/16/2016 08:31 AM, Antonious Iskander wrote:
>>>>>>>>>
>>>>>>>>> since ncsu has GitHub already then it would just be a redundant
>>>>>>>>> service to have gitlab or gogs.
>>>>>>>>>
>>>>>>>>> On Wed, Jun 15, 2016 at 10:45 AM, Brian Cottingham <
>>>>>>>>> <spiffytech@gmail.[redacted]>spiffytech@gmail.[redacted]> wrote:
>>>>>>>>>
>>>>>>>>>> My previous employer tried very hard to use GitLab and had to
>>>>>>>>>> switch to GitHub because GitLab's performance just wasn't there.
>>>>>>>>>>
>>>>>>>>>> On Wed, Jun 15, 2016 at 10:41 AM, Todd Edwards < <todd@mtn.[redacted]>
>>>>>>>>>> todd@mtn.[redacted]> wrote:
>>>>>>>>>>
>>>>>>>>>>> Might I suggest something like Gogs (https://gogs.io/) instead
>>>>>>>>>>> of Gitlab? In my experience the performance/hardware requirements of Gitlab
>>>>>>>>>>> in comparison is night and day.
>>>>>>>>>>>
>>>>>>>>>>> Sorry, I just needed to get that out.
>>>>>>>>>>>
>>>>>>>>>>> -- Todd
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jun 14, 2016 at 8:25 PM, Neill Robson <
>>>>>>>>>>> <nlrobson@ncsu.[redacted]>nlrobson@ncsu.[redacted]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> My vote is also still for a GitLab instance, since it leaves
>>>>>>>>>>>> possibilities open for both personal and club-wide projects wherever
>>>>>>>>>>>> programming is necessary (which is, of course, nearly everywhere).
>>>>>>>>>>>>
>>>>>>>>>>>> My apologies for the radio silence on my end; I've been in
>>>>>>>>>>>> China since the beginning of May and haven't had consistent access to email.
>>>>>>>>>>>>
>>>>>>>>>>>> Hope everybody's summer is going well!
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 06/15/2016 08:15 AM, Quentin Young wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi again!
>>>>>>>>>>>>
>>>>>>>>>>>> Looks like I made a typo in the last email; we upgraded *char*,
>>>>>>>>>>>> not short, to Xenial.
>>>>>>>>>>>>
>>>>>>>>>>>> Still haven't gotten any suggestions about what to use it for
>>>>>>>>>>>> though! Let thy voice be heard!
>>>>>>>>>>>>
>>>>>>>>>>>> Yours,
>>>>>>>>>>>> Quentin
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Jun 12, 2016 at 3:04 AM, Quentin Young <
>>>>>>>>>>>> <qlyoung@ncsu.[redacted]>qlyoung@ncsu.[redacted]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm happy to announce that myself and our Vice President, Tony
>>>>>>>>>>>>> Iskander,
>>>>>>>>>>>>> successfully upgraded short to Ubuntu 16.04 (Xenial Xerus) on
>>>>>>>>>>>>> Friday.
>>>>>>>>>>>>> Installation went without a hitch, and you can expect some
>>>>>>>>>>>>> more details on our
>>>>>>>>>>>>> website soon.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As of now there are no user accounts (except for myself)
>>>>>>>>>>>>> because we haven't yet
>>>>>>>>>>>>> decided what to do with this particular piece of hardware.
>>>>>>>>>>>>> Suggestions I have
>>>>>>>>>>>>> heard so far are:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - seti@home
>>>>>>>>>>>>> - folding@home
>>>>>>>>>>>>> - others that I forgot
>>>>>>>>>>>>>
>>>>>>>>>>>>> I would love to hear suggestions from members as to what we
>>>>>>>>>>>>> want to use this
>>>>>>>>>>>>> server for. Keep in mind it is an old server and its specs are
>>>>>>>>>>>>> not quite as
>>>>>>>>>>>>> beefy as Short:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - 2.8 GHz Intel Xeon, quadcore
>>>>>>>>>>>>> - 3 GB memory (lol)
>>>>>>>>>>>>> - 1 TB HDD
>>>>>>>>>>>>>
>>>>>>>>>>>>> My personal vote is for a GitLab instance. I've also been
>>>>>>>>>>>>> thinking about
>>>>>>>>>>>>> whether it might be prudent to simply move all of our hosted
>>>>>>>>>>>>> services onto this
>>>>>>>>>>>>> lower power server (currently those are the website and ZNC)
>>>>>>>>>>>>> and keep short as
>>>>>>>>>>>>> a higher performance server for use by club members. Anyway,
>>>>>>>>>>>>> reply and let me
>>>>>>>>>>>>> know what you think!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Enjoy the rest of your weekend,
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Quentin Young
>>>>>>>>>>>>> President, LUG @ NC State
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Quentin Young
>>>>>>>>>>>> President, LUG @ NC State
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Quentin Young
>>>>>>>> President, LUG @ NC State
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Quentin Young
>>>>>>> President, LUG @ NC State
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Quentin Young
>>>>>> President, LUG @ NC State
>>>>>>
>>>>>
>>>>>
>>>
>>
>>
>> --
>> Quentin Young
>> President, LUG @ NC State
>>
>
>


--
Quentin Young
President, LUG @ NC State


[Attachment of type text/html removed.]

------------------------------

Date: Fri, 22 Jul 2016 12:23:15 -0400
From: Neill Robson <nlrobson@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Char has been upgraded
Message-ID: <CAA+z_ttGN+MOO+dQpr--Xrr-ho4C9J9g-EmqZTF_9GfeeodoFg@mail.gmail.[redacted]>

Another idea: Currently our IRC room is on Freenode. Could we host our own
IRC server on this server?

Neill R.

On Jul 22, 2016 8:01 AM, "Quentin Young" <qlyoung@ncsu.[redacted]> wrote:

> Not sure what you mean by access for web hosting. All it takes is a
> running server and optionally a DNS record to set up a website. For email
> addresses, we own the @lug.ncsu.edu domain, but this is still a subdomain
> of ncsu.edu, and there are certainly implications there that need to be
> taken into account. We could presumably set up multiple DNS records to
> point at our email server and configure it for multiple domains but I think
> at that point we may start running into regulatory / security issues. I
> have never configured an email server.
>
> Additionally, Carlos Benavente, with CSC IT, has informed me of some
> recent changes regarding email servers that we will need to comply with.
> It's not quite as easy as 'throw up an email server', so if we want to
> pursue this route seriously I'd like to see some solid interest by more
> than a few members.
>
> On Fri, Jul 22, 2016 at 9:52 AM, Antonious Iskander <amiskand@ncsu.[redacted]>
> wrote:
>
>> That's cool. How do we have access to do web hosting? Also, for email
>> addresses @lug is fine but can we also customize our own? Thanks.
>>
>> On Thu, Jul 21, 2016 at 10:53 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>
>>> For email addresses I believe we would need to configure an email
>>> server. I think that is an option, we can probably offer @lug.ncsu.edu
>>> addresses. Will have to check.
>>>
>>> I'm fine allowing club members web hosting (as we presently do,
>>> http://nilbus.com/ is hosted on short).
>>>
>>> Quentin
>>>
>>> On Wed, Jun 29, 2016 at 6:13 AM, Antonious Iskander <amiskand@ncsu.[redacted]>
>>> wrote:
>>>
>>>> what about web hosting? or private email addresses?
>>>>
>>>> On Tue, Jun 28, 2016 at 6:19 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>> wrote:
>>>>
>>>>> I think if we hosted a VPN or anonymous web proxy on a University rack
>>>>> terminating inside the University network the University would be very
>>>>> upset with us. Not an option, I'm afraid.
>>>>> On Jun 28, 2016 6:08 PM, "Antonious Iskander" <amiskand@ncsu.[redacted]>
>>>>> wrote:
>>>>>
>>>>>> how about a vpn or an anonomous web proxy?
>>>>>>
>>>>>> On Mon, Jun 27, 2016 at 10:49 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>>> wrote:
>>>>>>
>>>>>>> I am wrong, students retain IP over their code. However the FAQ does
>>>>>>> indeed note:
>>>>>>>
>>>>>>> *"NCSU GitHub is specifically designed to not compete with
>>>>>>> Github.com as far as public offering. “Public” inside of NCSU GitHub is
>>>>>>> public to the institution, not the world. If a given project is truly open
>>>>>>> source, then it may be more appropriate to host it at GitHub.com with a
>>>>>>> personal account."*
>>>>>>>
>>>>>>> ...or on your friendly neighborhood Linux User Group's hosted git
>>>>>>> service :-)
>>>>>>>
>>>>>>> On Mon, Jun 27, 2016 at 10:03 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Additionally, I may be wrong on this front, but I recall reading
>>>>>>>> somewhere that the University retains many privileges and some form of
>>>>>>>> copyright over any code hosted there. If anyone has further information on
>>>>>>>> this I'd love to know more, but that's my understanding.
>>>>>>>>
>>>>>>>> On Mon, Jun 27, 2016 at 10:01 PM, Quentin Young <qlyoung@ncsu.[redacted]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> NCSU's GitHub Enterprise instance is fully private and requires
>>>>>>>>> LDAP authentication with your Unity credentials. Repositories are not
>>>>>>>>> world-readable. My vote is still with a hosted Git service.
>>>>>>>>>
>>>>>>>>> On Sun, Jun 19, 2016 at 6:03 PM, Neill Robson <nlrobson@ncsu.[redacted]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Ah, I had not thought of that! Well, a hosted git service was the
>>>>>>>>>> only idea I had, unfortunately.
>>>>>>>>>>
>>>>>>>>>> On 06/16/2016 08:31 AM, Antonious Iskander wrote:
>>>>>>>>>>
>>>>>>>>>> since ncsu has GitHub already then it would just be a redundant
>>>>>>>>>> service to have gitlab or gogs.
>>>>>>>>>>
>>>>>>>>>> On Wed, Jun 15, 2016 at 10:45 AM, Brian Cottingham <
>>>>>>>>>> <spiffytech@gmail.[redacted]>spiffytech@gmail.[redacted]> wrote:
>>>>>>>>>>
>>>>>>>>>>> My previous employer tried very hard to use GitLab and had to
>>>>>>>>>>> switch to GitHub because GitLab's performance just wasn't there.
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jun 15, 2016 at 10:41 AM, Todd Edwards < <todd@mtn.[redacted]>
>>>>>>>>>>> todd@mtn.[redacted]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Might I suggest something like Gogs (https://gogs.io/) instead
>>>>>>>>>>>> of Gitlab? In my experience the performance/hardware requirements of Gitlab
>>>>>>>>>>>> in comparison is night and day.
>>>>>>>>>>>>
>>>>>>>>>>>> Sorry, I just needed to get that out.
>>>>>>>>>>>>
>>>>>>>>>>>> -- Todd
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jun 14, 2016 at 8:25 PM, Neill Robson <
>>>>>>>>>>>> <nlrobson@ncsu.[redacted]>nlrobson@ncsu.[redacted]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> My vote is also still for a GitLab instance, since it leaves
>>>>>>>>>>>>> possibilities open for both personal and club-wide projects wherever
>>>>>>>>>>>>> programming is necessary (which is, of course, nearly everywhere).
>>>>>>>>>>>>>
>>>>>>>>>>>>> My apologies for the radio silence on my end; I've been in
>>>>>>>>>>>>> China since the beginning of May and haven't had consistent access to email.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hope everybody's summer is going well!
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 06/15/2016 08:15 AM, Quentin Young wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi again!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Looks like I made a typo in the last email; we upgraded *char*,
>>>>>>>>>>>>> not short, to Xenial.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Still haven't gotten any suggestions about what to use it for
>>>>>>>>>>>>> though! Let thy voice be heard!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Yours,
>>>>>>>>>>>>> Quentin
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Jun 12, 2016 at 3:04 AM, Quentin Young <
>>>>>>>>>>>>> <qlyoung@ncsu.[redacted]>qlyoung@ncsu.[redacted]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm happy to announce that myself and our Vice President,
>>>>>>>>>>>>>> Tony Iskander,
>>>>>>>>>>>>>> successfully upgraded short to Ubuntu 16.04 (Xenial Xerus) on
>>>>>>>>>>>>>> Friday.
>>>>>>>>>>>>>> Installation went without a hitch, and you can expect some
>>>>>>>>>>>>>> more details on our
>>>>>>>>>>>>>> website soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As of now there are no user accounts (except for myself)
>>>>>>>>>>>>>> because we haven't yet
>>>>>>>>>>>>>> decided what to do with this particular piece of hardware.
>>>>>>>>>>>>>> Suggestions I have
>>>>>>>>>>>>>> heard so far are:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - seti@home
>>>>>>>>>>>>>> - folding@home
>>>>>>>>>>>>>> - others that I forgot
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I would love to hear suggestions from members as to what we
>>>>>>>>>>>>>> want to use this
>>>>>>>>>>>>>> server for. Keep in mind it is an old server and its specs
>>>>>>>>>>>>>> are not quite as
>>>>>>>>>>>>>> beefy as Short:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - 2.8 GHz Intel Xeon, quadcore
>>>>>>>>>>>>>> - 3 GB memory (lol)
>>>>>>>>>>>>>> - 1 TB HDD
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> My personal vote is for a GitLab instance. I've also been
>>>>>>>>>>>>>> thinking about
>>>>>>>>>>>>>> whether it might be prudent to simply move all of our hosted
>>>>>>>>>>>>>> services onto this
>>>>>>>>>>>>>> lower power server (currently those are the website and ZNC)
>>>>>>>>>>>>>> and keep short as
>>>>>>>>>>>>>> a higher performance server for use by club members. Anyway,
>>>>>>>>>>>>>> reply and let me
>>>>>>>>>>>>>> know what you think!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Enjoy the rest of your weekend,
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Quentin Young
>>>>>>>>>>>>>> President, LUG @ NC State
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Quentin Young
>>>>>>>>>>>>> President, LUG @ NC State
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Quentin Young
>>>>>>>>> President, LUG @ NC State
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Quentin Young
>>>>>>>> President, LUG @ NC State
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Quentin Young
>>>>>>> President, LUG @ NC State
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>> --
>>> Quentin Young
>>> President, LUG @ NC State
>>>
>>
>>
>
>
> --
> Quentin Young
> President, LUG @ NC State
>


[Attachment of type text/html removed.]

------------------------------

End of [lug] Digest (2 messages)
**********