[TasLUG] Hobart TasLUG Meeting: Thursday 20 September

[John Kristensen]

Hello All,

A reminder that the next Hobart TasLUG Meeting is on tomorrow evening. 
The details can be found in my previous email below.

SeeYa,
John.

On 14/9/18 12:09 am, John Kristensen wrote:
> Hello All,
> 
> It is an odd month so that must mean it is a talk month at Hobart 
> TasLUG. At the meeting this month we will be having another two talks:
> 
>    ## Julius Roberts ##
>    Using GitLabCI to build better software [1]
> 
>    ## Peter Billam ##
>    Talking about some random-distribution generators in Lua and
>    PostScript, some Markov Chains, some first steps in torch -
>    and then an unorthodox Guitar-Tablature.
> 
> The venue for this month will be Enterprize Hobart:
> 
>     When: Thursday 20 September 2018 - 6:00pm for a 6:30pm start
> 
>    Where: Enterprize - Hobart
>           5th floor, Hobart City Council Building
>           24 Davey Street
>           (map: https://goo.gl/maps/SNWs8FJcvEk)
> 
> Note: the doors inside the foyer will be locked, so you will need to use 
> the intercom to let us know to buzz you in. However, if you arrive after 
> 6:30pm, then I'll leave a note with a phone number to call as the 
> intercom isn't near where the talks will be.
> 
> Enterprize provide a selection of alcoholic/non-alcoholic drinks and 
> coffee pods for the appropriate donation, as well as free instant coffee 
> and tea. So come at 6:00pm, get a drink, and have a bit of a mingle 
> before the talks start at 6:30pm. We will also be heading out to find 
> somewhere to eat afterwards for those interested.
> 
> I would like to to extend a big thank you to Enterprize for generously 
> allowing us to use their space to hold regular meetings.
> 
> SeeYa,
> John.
> 
> ---
> 
> [1]  When used along side modern software development practices, 
> GitlabCI allows you to build better software, all in the open.
> 
> This will be a somewhat speedy practical overview of GitlabCI followed 
> by question time.
> 
>    1. gitlab issues and issue boards
>    2. issue branching and merge requests
>    3. the ci yml file (layout, stages, jobs, artifacts)
>    4. gitlab runner types (docker, daemon) and daemon execution modes
>    5. install and register runner daemon
>    6. exploring the runner filesystem layout; "where is my code", and
>       manual testing/debug
>    7. ??
>    8. possible further discussion points:
>        - gitlab deployment options (license, self hosted vs gitlab.com)
>        - semantic versioning, git tagging and gitlab download URLs
>        - conda virtual environments
> 
> Requires a working knowledge of git and branching strategies.
> Assumes a basic familiarity with gitlab.
> May assume understanding of conda python and conda virtual environments
> 
> ---
> _______________________________________________
> TasLUG mailing list
> TasLUG at lists.linux.org.au
> http://lists.linux.org.au/mailman/listinfo/taslug