Re: [Discuss] Installation instructions for GNU make?

[Lex Nederbragt]

Thanks, Michael!

Lex

> On 11 Oct 2016, at 10:29, Michael J Jackson  wrote:
> 
> Hi Lex,
> 
> Quoting Lex Nederbragt  on Tue, 11 Oct 2016 
> 09:38:04 +0200:
> 
>> We will be teaching the SWC ‘make’ lesson for the first time in a couple of 
>> weeks. Do we need to provide the learners with instructions for installing 
>> make, or is it a default part of all platforms? If not, are there any 
>> more-or-less curated installation instructions available somewhere?
>> 
>> Thanks in advance,
>> 
>>  Lex Nederbragt
> 
> You'll need to provide installation instructions. Putting them into the 
> workshop template [1] was recently dropped in favour of putting them into 
> their lesson template [2], which hasn't yet happened. I use my own, copying 
> and pasting from [3] (which renders as [4]). Though, as the SWC installer [5] 
> installs GNU Make onto GitBash I'd change the Windows instructions to be [6].
> 
> cheers,
> mike
> 
> [1] https://github.com/swcarpentry/workshop-template/issues/228
> [2] https://github.com/swcarpentry/make-novice
> [3] 
> https://github.com/hpcarcher/2014-12-03-edinburgh/blob/gh-pages/_includes/setup.html
> [4] http://hpcarcher.github.io/2014-12-03-edinburgh/
> [5] https://github.com/swcarpentry/windows-installer
> [6]
> 
> 
> The Software Carpentry Windows installer installs Make.
> 
> 
> To test, open a Git Bash window, type make, and press Enter.
> 
> 
> You should see the following message
> make: *** No targets specified and no makefile found. Stop.
> This means that Make was successfully installed.
> Otherwise, you'll see this error message:
> bash: make: command not found
> 
> 
> 
> 
> 
>> 
>> --
>> Lex Nederbragt
>> Centre for Ecological and Evolutionary Synthesis (CEES)
>> Dept. of Biosciences, University of Oslo
>> P.O. Box 1066 Blindern 0316 Oslo, Norway
>> Ph. +47 22844132 +47 48028722 Fax. +47 22854001
>> Email lex.nederbr...@ibv.uio.no
>> http://flxlex.flavors.me/
>> 
>> 
> 
> 
> 
> 
> Dr. Michael (Mike) Jackson m.jack...@epcc.ed.ac.uk
> Software Architect Tel: +44 (0)131 650 5141
> EPCC, The University of Edinburgh  http://www.epcc.ed.ac.uk
> Software Sustainability Institute  http://www.software.ac.uk
> 
> 
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 
> 

___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/listinfo/discuss

Re: [Discuss] Installation instructions for GNU make?

[Michael J Jackson]

Hi Lex,

Quoting Lex Nederbragt  on Tue, 11 Oct 2016  
09:38:04 +0200:


We will be teaching the SWC ‘make’ lesson for the first time in a  
couple of weeks. Do we need to provide the learners with  
instructions for installing make, or is it a default part of all  
platforms? If not, are there any more-or-less curated installation  
instructions available somewhere?


Thanks in advance,

Lex Nederbragt


You'll need to provide installation instructions. Putting them into  
the workshop template [1] was recently dropped in favour of putting  
them into their lesson template [2], which hasn't yet happened. I use  
my own, copying and pasting from [3] (which renders as [4]). Though,  
as the SWC installer [5] installs GNU Make onto GitBash I'd change the  
Windows instructions to be [6].


cheers,
mike

[1] https://github.com/swcarpentry/workshop-template/issues/228
[2] https://github.com/swcarpentry/make-novice
[3]  
https://github.com/hpcarcher/2014-12-03-edinburgh/blob/gh-pages/_includes/setup.html

[4] http://hpcarcher.github.io/2014-12-03-edinburgh/
[5] https://github.com/swcarpentry/windows-installer
[6]


The Software Carpentry Windows installer installs Make.


To test, open a Git Bash window, type make, and press Enter.


You should see the following message
make: *** No targets specified and no makefile found. Stop.
This means that Make was successfully installed.
Otherwise, you'll see this error message:
bash: make: command not found







--
Lex Nederbragt
Centre for Ecological and Evolutionary Synthesis (CEES)
Dept. of Biosciences, University of Oslo
P.O. Box 1066 Blindern 0316 Oslo, Norway
Ph. +47 22844132 +47 48028722 Fax. +47 22854001
Email lex.nederbr...@ibv.uio.no
http://flxlex.flavors.me/







Dr. Michael (Mike) Jackson m.jack...@epcc.ed.ac.uk
Software Architect Tel: +44 (0)131 650 5141
EPCC, The University of Edinburgh  http://www.epcc.ed.ac.uk
Software Sustainability Institute  http://www.software.ac.uk


--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/listinfo/discuss

[Discuss] Installation instructions for GNU make?

[Lex Nederbragt]

Hi,

We will be teaching the SWC ‘make’ lesson for the first time in a couple of 
weeks. Do we need to provide the learners with instructions for installing 
make, or is it a default part of all platforms? If not, are there any 
more-or-less curated installation instructions available somewhere?

Thanks in advance,

Lex Nederbragt

--
Lex Nederbragt
Centre for Ecological and Evolutionary Synthesis (CEES)
Dept. of Biosciences, University of Oslo
P.O. Box 1066 Blindern 0316 Oslo, Norway
Ph. +47 22844132 +47 48028722 Fax. +47 22854001
Email lex.nederbr...@ibv.uio.no
http://flxlex.flavors.me/

___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/listinfo/discuss

Re: [Discuss] installation instructions

[Jonah Duckles]

An "Installation Lesson" and the right configuration for a workshop are two 
different concerns. A workshop could be comprised of Bash, Git & Python, or 
Bash, Mercurial and Matlab, or or or... So I really do like the approach we use 
now to leave configuration directives in the hands of the instructor of a 
specific workshop.

That being said, each lesson itself could have an `install.md` that the lessons 
references with instructions on how to get dependencies necessary for the 
lesson on a Mac, Windows or Linux. This solves the web-only learner issue that 
started the thread. It also scales gracefully.

As the number of contributed lessons grow, I worry that an uber installation 
guide for all-the-things is not on a track to solve a novice learner's 
problems. It becomes yet another place to change configuration directives and 
unless it is actively maintained by all the maintainers, it will fall out of 
step with the preferred config.

Greg, can you bring this to the Lesson Developers/Maintainers with a request to 
come up with a way forward for install instructions for web-based learners?

Regards,
---
Jonah Duckles
Software Carpentry, Executive Director
http://software-carpentry.org

From: Christina Koch <cko...@wisc.edu>
Reply: Christina Koch <cko...@wisc.edu>
Date: February 22, 2016 at 8:20:28 AM
To: Andrew Walker [EAR] <a.wal...@leeds.ac.uk>
CC: discuss@lists.software-carpentry.org <discuss@lists.software-carpentry.org>
Subject:  Re: [Discuss] installation instructions  

To add something completely different to the mix - Sarah Stevens and I are in 
the process of making "how to" installation videos for both windows/mac.  They 
could go on the main SWC lessons page, on individual lesson pages, or in a new 
"installation" lesson.  

Christina

On Sat, Feb 20, 2016 at 11:58 AM, Andrew Walker [EAR] <a.wal...@leeds.ac.uk> 
wrote:
Hi all,

I suspect the best way to do this would be to create 'special workshop'
from the template that includes all installation instructions and some
generic background information rather than information about a particular
workshop. Call it something like 'installation' in the swcarpentry
organisation and we would get a useful site
(swcarpentry.github.io/installation) and hopefully have something we can
keep in sync with the instructions we present to workshop participants.

There are a few important points that I think we should keep in mind:

* We should keep a set of installation instructions in the workshop
webpages (and thus in the template). Workshop organisers / lead
instructors need to taylor these both for content (avoid telling
participants at a R-based workshop to install python) and "level" (if you
know you have absolute beginners the python test scripts seem to be more
trouble than they are worth, but they seem to work well with more advanced
groups).

* Any central instructions need be kept in sync with the per-workshop
instructions. Fixes like the problem with nano last summer need to
propagate everywhere and we should avoid telling participants to do two
different things depending on where they look.

* It should be possible to arrange this with a bit of careful thought and
git-foo. It would need reasonable communication between the
workshop-template maintainer and whoever looks after the installation
instructions repository and a clear idea about the direction that patches
to installation instructions should travel (they could go from the
installation instructions repository to the workshop-template or the other
way; I suspect mixing directions would result in a mess).

Ultimately this discussion probably belongs in an issue in a repository
somewhere.

Best wishes,

Andrew

‹
Dr Andrew Walker
NERC Independent Research Fellow
School of Earth and Environment
University of Leeds




On 19/02/2016, 18:14, "Discuss on behalf of Cam Macdonell"
<discuss-boun...@lists.software-carpentry.org on behalf of
macdonel...@macewan.ca> wrote:

>May I suggest that an admin on the SWC github site create a repo named
>"install-docs" (or something better) that we can begin to work on?
>
>Cam
>
>Quoting Karin Lagesen <karin.lage...@gmail.com>:
>> I have for some time wanted a "Resources" section on our website, with
>>stuff
>> that our community can use. IMO, this section would include a SWC pitch,
>> logos, other advertising material, install instructions, debug install
>> stuff, and other mostly static things that we, the community, would need
>> rapid access to.
>>
>> Karin
>>
>>
>> On 18.02.2016 02:26, Bennet Fauber wrote:
>> >I think that separting the installation instructions is good idea.
>> >That might make them easier for people trying to use the published
>> >material but who are not attending a specific workshop.
>> >
>> >In

Re: [Discuss] installation instructions

[Christina Koch]

>Thinking about the problem from the perspective of a novice learner,
> >>their
> >> >>first instinct will be to check the website. After coming up short,
> >>some
> >> >>people will become frustrated and abandon the search. Here¹s where an
> >>expert
> >> >>might say ³Why didn¹t you just* google for {program needed}?² Because
> >>the
> >> >>novice learner lacks the mental models of an expert, they may not
> >>know what
> >> >>search terms to use. The Shell lessons suffer from this problem more
> >>than
> >> >>most:
> >> >>
> >> >>·Nowhere on the lesson landing page
> >> >>(http://swcarpentry.github.io/shell-novice/) do we mention the term
> >>³Bash²
> >> >>
> >> >>·The ³Introducing the Shell² page
> >> >>(http://swcarpentry.github.io/shell-novice/00-intro.html) does not
> >>use the
> >> >>term ³Bash² until the seventh paragraph
> >> >>
> >> >>·The intro page does not directly tell a novice learner that
> >>the
> >> >>standard Git for Windows installation includes Bash.
> >> >>
> >> >>·The intro page does mention that the Bash shell is the
> >>default
> >> >>shell on many modern UNIX implementations. A novice learner may not
> >>know
> >> >>that Mac OS now uses a UNIX engine and uses Bash for its command line
> >> >>terminal. They also may not know how to access the terminal.
> >> >>
> >> >>·If a Linux user doesn¹t know about the Unix command line, I
> >>really
> >> >>want to ask them how they got Linux on their machine in the first
> >>place.
> >> >>
> >> >>
> >> >>
> >> >>For these reasons, I suggest that we should add installation
> >>instructions to
> >> >>either the lesson pages or as a separate ³lesson². Before Greg (or
> >>anyone
> >> >>else) says it, yes, I know ³Pull requests are always welcome². Let me
> >>ask
> >> >>the community -  Would you rather have:
> >> >>
> >> >>A separate install ³lesson² and links from the other lessons to that
> >>install
> >> >>page
> >> >>
> >> >>-OR-
> >> >>Installation information within each separate lesson?
> >> >>
> >> >>
> >> >>
> >> >>John Moreau
> >> >>
> >> >>* http://swcarpentry.github.io/instructor-training/05-expertise.html
> >> >>
> >> >>
> >> >>
> >> >>From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org]
> On
> >> >>Behalf Of Matt Davis
> >> >>Sent: Wednesday, February 17, 2016 5:05 PM
> >> >>To: Markus Mueller <muell...@landcareresearch.co.nz>;
> >> >>discuss@lists.software-carpentry.org
> >> >>Subject: Re: [Discuss] installation instructions
> >> >>
> >> >>
> >> >>
> >> >>Hi Markus,
> >> >>
> >> >>
> >> >>
> >> >>Our workshop webpages have software installation instructions. We
> >>used to
> >> >>have those on software-carpentry.org, but I couldn't find them so
> >>here's the
> >> >>website of an upcoming workshop:
> >> >>https://joshwaterfall.github.io/2016-02-16-NIH/
> >> >>
> >> >>
> >> >>
> >> >>Best,
> >> >>
> >> >>Matt
> >> >>
> >> >>
> >> >>
> >> >>On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller
> >> >><muell...@landcareresearch.co.nz> wrote:
> >> >>
> >> >>Dear listers,
> >> >>
> >> >>
> >> >>
> >> >>I am a new instructor (or soon to be one) and started having a closer
> >>look
> >> >>at the software carpentry lesson material. I first had a look at the
> >> >>instructor guide
> >> >>(http://swcarpentry.github.io/shell-novice/instructors.html) and only
> >>found
> >> >>some general tips and hints about which tools to use and how to
> >>install them
> >> >>(my interested would here apparently be how to get a unix shell to
> &

Re: [Discuss] installation instructions

[Andrew Walker [EAR]]

he Shell² page
>> >>(http://swcarpentry.github.io/shell-novice/00-intro.html) does not
>>use the
>> >>term ³Bash² until the seventh paragraph
>> >>
>> >>·The intro page does not directly tell a novice learner that
>>the
>> >>standard Git for Windows installation includes Bash.
>> >>
>> >>·The intro page does mention that the Bash shell is the
>>default
>> >>shell on many modern UNIX implementations. A novice learner may not
>>know
>> >>that Mac OS now uses a UNIX engine and uses Bash for its command line
>> >>terminal. They also may not know how to access the terminal.
>> >>
>> >>·If a Linux user doesn¹t know about the Unix command line, I
>>really
>> >>want to ask them how they got Linux on their machine in the first
>>place.
>> >>
>> >>
>> >>
>> >>For these reasons, I suggest that we should add installation
>>instructions to
>> >>either the lesson pages or as a separate ³lesson². Before Greg (or
>>anyone
>> >>else) says it, yes, I know ³Pull requests are always welcome². Let me
>>ask
>> >>the community -  Would you rather have:
>> >>
>> >>A separate install ³lesson² and links from the other lessons to that
>>install
>> >>page
>> >>
>> >>-OR-
>> >>Installation information within each separate lesson?
>> >>
>> >>
>> >>
>> >>John Moreau
>> >>
>> >>* http://swcarpentry.github.io/instructor-training/05-expertise.html
>> >>
>> >>
>> >>
>> >>From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
>> >>Behalf Of Matt Davis
>> >>Sent: Wednesday, February 17, 2016 5:05 PM
>> >>To: Markus Mueller <muell...@landcareresearch.co.nz>;
>> >>discuss@lists.software-carpentry.org
>> >>Subject: Re: [Discuss] installation instructions
>> >>
>> >>
>> >>
>> >>Hi Markus,
>> >>
>> >>
>> >>
>> >>Our workshop webpages have software installation instructions. We
>>used to
>> >>have those on software-carpentry.org, but I couldn't find them so
>>here's the
>> >>website of an upcoming workshop:
>> >>https://joshwaterfall.github.io/2016-02-16-NIH/
>> >>
>> >>
>> >>
>> >>Best,
>> >>
>> >>Matt
>> >>
>> >>
>> >>
>> >>On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller
>> >><muell...@landcareresearch.co.nz> wrote:
>> >>
>> >>Dear listers,
>> >>
>> >>
>> >>
>> >>I am a new instructor (or soon to be one) and started having a closer
>>look
>> >>at the software carpentry lesson material. I first had a look at the
>> >>instructor guide
>> >>(http://swcarpentry.github.io/shell-novice/instructors.html) and only
>>found
>> >>some general tips and hints about which tools to use and how to
>>install them
>> >>(my interested would here apparently be how to get a unix shell to
>>run on
>> >>windows).
>> >>
>> >>
>> >>
>> >>I apologize if I missed something, but otherwise would be glad if
>>somebody
>> >>could point me to the installation guidelines (that the page above
>>somehow
>> >>hints at).
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>Cheers,
>> >>
>> >>
>> >>
>> >>Markus
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>Please consider the environment before printing this email
>> >>Warning: This electronic message together with any attachments is
>> >>confidential. If you receive it in error: (i) you must not read, use,
>> >>disclose, copy or retain it; (ii) please contact the sender
>>immediately by
>> >>reply email and then delete the emails.
>> >>The views expressed in this email may not be those of Landcare
>>Research New
>> >>Zealand Limited. http://www.landcareresearch.co.nz
>> >>
>> >>___
>> >>Discuss mailing list
>> >>Discuss@lists.software-carpentry.org
>> 
>>>>http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.soft
>>>>ware-carpentry.org
>> >>
>> >>
>> >>___
>> >>Discuss mailing list
>> >>Discuss@lists.software-carpentry.org
>> 
>>>>http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.soft
>>>>ware-carpentry.org
>> >
>> >___
>> >Discuss mailing list
>> >Discuss@lists.software-carpentry.org
>> 
>>>http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.softw
>>>are-carpentry.org
>> >
>> 
>> 
>> ___
>> Discuss mailing list
>> Discuss@lists.software-carpentry.org
>> 
>>http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.softwa
>>re-carpentry.org
>
>___
>Discuss mailing list
>Discuss@lists.software-carpentry.org
>http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.softwar
>e-carpentry.org


___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org

Re: [Discuss] installation instructions

[Jan Kim]

 lesson landing page
> >> > (http://swcarpentry.github.io/shell-novice/)
> >> > do we mention the term ???Bash???
> >> >
> >> > ?? The ???Introducing the Shell??? page
> >> > (http://swcarpentry.github.io/shell-novice/00-intro.html)
> >> > does not use the term ???Bash??? until the seventh paragraph
> >> >
> >> > ?? The intro page does not directly tell a novice learner that the
> >> > standard Git for Windows
> >> > installation includes Bash.
> >> >
> >> > ?? The intro page does mention that the Bash shell is the default shell
> >> > on many modern UNIX
> >> > implementations. A novice learner may not know that Mac OS now uses a
> >> > UNIX engine and uses
> >> > Bash for its command line terminal. They also may not know how to access
> >> > the terminal.
> >> >
> >> > ?? If a Linux user doesn???t know about the Unix command line, I really
> >> > want to ask them how
> >> > they got Linux on their machine in the first place.
> >> >
> >> > For these reasons, I suggest that we should add installation
> >> > instructions to either
> >> > the lesson pages or as a separate ???lesson???. Before Greg (or anyone 
> >> > else)
> >> > says it, yes,
> >> > I know ???Pull requests are always welcome???. Let me ask the community -
> >> > Would you rather
> >> > have:
> >> > A separate install ???lesson??? and links from the other lessons to that
> >> > install page
> >> > -OR-
> >> > Installation information within each separate lesson?
> >> >
> >> > John Moreau
> >> > * http://swcarpentry.github.io/instructor-training/05-expertise.html
> >> >
> >> > From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
> >> > Behalf
> >> > Of Matt Davis
> >> > Sent: Wednesday, February 17, 2016 5:05 PM
> >> > To: Markus Mueller ; discuss@lists.software-carpentry.org
> >> > Subject: Re: [Discuss] installation instructions
> >> >
> >> > Hi Markus,
> >> >
> >> > Our workshop webpages have software installation instructions. We used
> >> > to have those
> >> > on software-carpentry.org, but I couldn't find
> >> > them so here's the website of an upcoming workshop:
> >> > https://joshwaterfall.github.io/2016-02-16-NIH/
> >> >
> >> > Best,
> >> > Matt
> >> >
> >> > On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller >
> >> > wrote:
> >> > Dear listers,
> >> >
> >> > I am a new instructor (or soon to be one) and started having a closer
> >> > look at the software
> >> > carpentry lesson material. I first had a look at the instructor guide
> >> > (http://swcarpentry.github.io/shell-novice/instructors.html)
> >> > and only found some general tips and hints about which tools to use and
> >> > how to install them
> >> > (my interested would here apparently be how to get a unix shell to run
> >> > on windows).
> >> >
> >> > I apologize if I missed something, but otherwise would be glad if
> >> > somebody could point
> >> > me to the installation guidelines (that the page above somehow hints
> >> > at).
> >> >
> >> >
> >> > Cheers,
> >> >
> >> > Markus
> >> >
> >> > 
> >> >
> >> > Please consider the environment before printing this email
> >> > Warning: This electronic message together with any attachments is
> >> > confidential. If
> >> > you receive it in error: (i) you must not read, use, disclose, copy or
> >> > retain it; (ii) please
> >> > contact the sender immediately by reply email and then delete the
> >> > emails.
> >> > The views expressed in this email may not be those of Landcare Research
> >> > New Zealand Limited.
> >> > http://www.landcareresearch.co.nz
> >> > ___
> >> > Discuss mailing list
> >> > Discuss@lists.software-carpentry.org
> >> >
> >> > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
> >> > ___
> >> > Discuss mailing list
> >> > Discuss@lists.software-carpentry.org
> >> >
> >> > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
> >>
> >>
> >> ___
> >> Discuss mailing list
> >> Discuss@lists.software-carpentry.org
> >>
> >> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
> >
> >
> > ___
> > Discuss mailing list
> > Discuss@lists.software-carpentry.org
> > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
> 
> ___
> Discuss mailing list
> Discuss@lists.software-carpentry.org
> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org

-- 
 +- Jan T. Kim ---+
 | email: jtt...@gmail.com|
 | WWW:   http://www.jtkim.dreamhosters.com/  |
 *-=<  hierarchical systems are for files, not for humans  >=-*

___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org

Re: [Discuss] installation instructions

[Karin Lagesen]

I have for some time wanted a "Resources" section on our website, with 
stuff that our community can use. IMO, this section would include a SWC 
pitch, logos, other advertising material, install instructions, debug 
install stuff, and other mostly static things that we, the community, 
would need rapid access to.


Karin


On 18.02.2016 02:26, Bennet Fauber wrote:

I think that separting the installation instructions is good idea.
That might make them easier for people trying to use the published
material but who are not attending a specific workshop.

In the spirit of writing functions and calling them from larger
scripts, wouldn't we want to write a function for each installation:
bash, git, python, et al., and then refer to the ones pertinent to the
workshop from the workshop site?  Then the same installation
instructions could be used for an Intro Python and an Intermediate
Python.



On Wed, Feb 17, 2016 at 7:15 PM, Moreau, John (UMKC-Student)
<john.r.mor...@mail.umkc.edu> wrote:

Matt et al:

Perhaps this is the crux of the problem. We no longer have installation
instructions outside of the workshop pages. More experienced instructors may
know to check the workshop template on GitHub. However, for newer
instructors, potential workshop hosts, and drive-by site visitors, there’s
no clear directions.

Thinking about the problem from the perspective of a novice learner, their
first instinct will be to check the website. After coming up short, some
people will become frustrated and abandon the search. Here’s where an expert
might say “Why didn’t you just* google for {program needed}?” Because the
novice learner lacks the mental models of an expert, they may not know what
search terms to use. The Shell lessons suffer from this problem more than
most:

·Nowhere on the lesson landing page
(http://swcarpentry.github.io/shell-novice/) do we mention the term “Bash”

·The “Introducing the Shell” page
(http://swcarpentry.github.io/shell-novice/00-intro.html) does not use the
term “Bash” until the seventh paragraph

·The intro page does not directly tell a novice learner that the
standard Git for Windows installation includes Bash.

·The intro page does mention that the Bash shell is the default
shell on many modern UNIX implementations. A novice learner may not know
that Mac OS now uses a UNIX engine and uses Bash for its command line
terminal. They also may not know how to access the terminal.

·If a Linux user doesn’t know about the Unix command line, I really
want to ask them how they got Linux on their machine in the first place.



For these reasons, I suggest that we should add installation instructions to
either the lesson pages or as a separate “lesson”. Before Greg (or anyone
else) says it, yes, I know “Pull requests are always welcome”. Let me ask
the community -  Would you rather have:

A separate install “lesson” and links from the other lessons to that install
page

-OR-
Installation information within each separate lesson?



John Moreau

* http://swcarpentry.github.io/instructor-training/05-expertise.html



From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
Behalf Of Matt Davis
Sent: Wednesday, February 17, 2016 5:05 PM
To: Markus Mueller <muell...@landcareresearch.co.nz>;
discuss@lists.software-carpentry.org
Subject: Re: [Discuss] installation instructions



Hi Markus,



Our workshop webpages have software installation instructions. We used to
have those on software-carpentry.org, but I couldn't find them so here's the
website of an upcoming workshop:
https://joshwaterfall.github.io/2016-02-16-NIH/



Best,

Matt



On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller
<muell...@landcareresearch.co.nz> wrote:

Dear listers,



I am a new instructor (or soon to be one) and started having a closer look
at the software carpentry lesson material. I first had a look at the
instructor guide
(http://swcarpentry.github.io/shell-novice/instructors.html) and only found
some general tips and hints about which tools to use and how to install them
(my interested would here apparently be how to get a unix shell to run on
windows).



I apologize if I missed something, but otherwise would be glad if somebody
could point me to the installation guidelines (that the page above somehow
hints at).





Cheers,



Markus






Please consider the environment before printing this email
Warning: This electronic message together with any attachments is
confidential. If you receive it in error: (i) you must not read, use,
disclose, copy or retain it; (ii) please contact the sender immediately by
reply email and then delete the emails.
The views expressed in this email may not be those of Landcare Research New
Zealand Limited. http://www.landcareresearch.co.nz

___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-ca

Re: [Discuss] installation instructions

[Ivan Gonzalez]

Hi,

I've opened an issue last week regarding the lack of "readable"
instructions on how to set up a workshop [1].

Also regarding John's comment and this discussion on this other issue [2],
I make a first try on a open-a-terminal repo [3] that we could link to any
time we need to tell people how to open a terminal. Please PR with your
instructions to your OS, so we can try it at some point.

[1] https://github.com/swcarpentry/workshop-template/issues/299
[2] https://github.com/swcarpentry/workshop-template/issues/291
[3] https://github.com/iglpdc/open-a-terminal/

Best,

Ivan

[1] https://github.com/swcarpentry/workshop-template/issues/299

On Wed, Feb 17, 2016 at 7:34 PM, Matt Davis <jiffyc...@gmail.com> wrote:

> The idea of an installation lesson sounds good to me.
>
> On Wed, Feb 17, 2016 at 4:28 PM Darya Vanichkina <d.vanichk...@gmail.com>
> wrote:
>
>> A separate install lesson, because the lessons are already rather
>> content-heavy, and searching within them for install instructions to email
>> to students to have a go before coming in is confusing.
>>
>>
>> On 18 February 2016 at 11:16:34, Moreau, John (UMKC-Student) (
>> john.r.mor...@mail.umkc.edu) wrote:
>> > Matt et al:
>> > Perhaps this is the crux of the problem. We no longer have installation
>> instructions
>> > outside of the workshop pages. More experienced instructors may know to
>> check the workshop
>> > template on GitHub. However, for newer instructors, potential workshop
>> hosts, and
>> > drive-by site visitors, there’s no clear directions.
>> > Thinking about the problem from the perspective of a novice learner,
>> their first instinct
>> > will be to check the website. After coming up short, some people will
>> become frustrated
>> > and abandon the search. Here’s where an expert might say “Why didn’t
>> you just* google
>> > for {program needed}?” Because the novice learner lacks the mental
>> models of an expert,
>> > they may not know what search terms to use. The Shell lessons suffer
>> from this problem
>> > more than most:
>> >
>> > · Nowhere on the lesson landing page (
>> http://swcarpentry.github.io/shell-novice/)
>> > do we mention the term “Bash”
>> >
>> > · The “Introducing the Shell” page (
>> http://swcarpentry.github.io/shell-novice/00-intro.html)
>> > does not use the term “Bash” until the seventh paragraph
>> >
>> > · The intro page does not directly tell a novice learner that the
>> standard Git for Windows
>> > installation includes Bash.
>> >
>> > · The intro page does mention that the Bash shell is the default shell
>> on many modern UNIX
>> > implementations. A novice learner may not know that Mac OS now uses a
>> UNIX engine and uses
>> > Bash for its command line terminal. They also may not know how to
>> access the terminal.
>> >
>> > · If a Linux user doesn’t know about the Unix command line, I really
>> want to ask them how
>> > they got Linux on their machine in the first place.
>> >
>> > For these reasons, I suggest that we should add installation
>> instructions to either
>> > the lesson pages or as a separate “lesson”. Before Greg (or anyone
>> else) says it, yes,
>> > I know “Pull requests are always welcome”. Let me ask the community -
>> Would you rather
>> > have:
>> > A separate install “lesson” and links from the other lessons to that
>> install page
>> > -OR-
>> > Installation information within each separate lesson?
>> >
>> > John Moreau
>> > * http://swcarpentry.github.io/instructor-training/05-expertise.html
>> >
>> > From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
>> Behalf
>> > Of Matt Davis
>> > Sent: Wednesday, February 17, 2016 5:05 PM
>> > To: Markus Mueller ; discuss@lists.software-carpentry.org
>> > Subject: Re: [Discuss] installation instructions
>> >
>> > Hi Markus,
>> >
>> > Our workshop webpages have software installation instructions. We used
>> to have those
>> > on software-carpentry.org, but I couldn't find
>> > them so here's the website of an upcoming workshop:
>> https://joshwaterfall.github.io/2016-02-16-NIH/
>> >
>> > Best,
>> > Matt
>> >
>> > On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller >
>> > wrote:
>> > Dear listers,
>> >
>> > I am a new instructor (or soon to be one) and started having a closer
>> loo

Re: [Discuss] installation instructions

[Davide Del Vento]

Yes, separate install lesson, linked from all the relevant ones seems
the best of both worlds

On Wed, Feb 17, 2016 at 5:48 PM, Noam Ross <noam.r...@gmail.com> wrote:
> It would make sense for each lesson to have a link to the install lesson,
> though.
>
> On Wed, Feb 17, 2016 at 7:35 PM Matt Davis <jiffyc...@gmail.com> wrote:
>>
>> The idea of an installation lesson sounds good to me.
>>
>> On Wed, Feb 17, 2016 at 4:28 PM Darya Vanichkina <d.vanichk...@gmail.com>
>> wrote:
>>>
>>> A separate install lesson, because the lessons are already rather
>>> content-heavy, and searching within them for install instructions to email
>>> to students to have a go before coming in is confusing.
>>>
>>>
>>> On 18 February 2016 at 11:16:34, Moreau, John (UMKC-Student)
>>> (john.r.mor...@mail.umkc.edu) wrote:
>>> > Matt et al:
>>> > Perhaps this is the crux of the problem. We no longer have installation
>>> > instructions
>>> > outside of the workshop pages. More experienced instructors may know to
>>> > check the workshop
>>> > template on GitHub. However, for newer instructors, potential workshop
>>> > hosts, and
>>> > drive-by site visitors, there’s no clear directions.
>>> > Thinking about the problem from the perspective of a novice learner,
>>> > their first instinct
>>> > will be to check the website. After coming up short, some people will
>>> > become frustrated
>>> > and abandon the search. Here’s where an expert might say “Why didn’t
>>> > you just* google
>>> > for {program needed}?” Because the novice learner lacks the mental
>>> > models of an expert,
>>> > they may not know what search terms to use. The Shell lessons suffer
>>> > from this problem
>>> > more than most:
>>> >
>>> > · Nowhere on the lesson landing page
>>> > (http://swcarpentry.github.io/shell-novice/)
>>> > do we mention the term “Bash”
>>> >
>>> > · The “Introducing the Shell” page
>>> > (http://swcarpentry.github.io/shell-novice/00-intro.html)
>>> > does not use the term “Bash” until the seventh paragraph
>>> >
>>> > · The intro page does not directly tell a novice learner that the
>>> > standard Git for Windows
>>> > installation includes Bash.
>>> >
>>> > · The intro page does mention that the Bash shell is the default shell
>>> > on many modern UNIX
>>> > implementations. A novice learner may not know that Mac OS now uses a
>>> > UNIX engine and uses
>>> > Bash for its command line terminal. They also may not know how to
>>> > access the terminal.
>>> >
>>> > · If a Linux user doesn’t know about the Unix command line, I really
>>> > want to ask them how
>>> > they got Linux on their machine in the first place.
>>> >
>>> > For these reasons, I suggest that we should add installation
>>> > instructions to either
>>> > the lesson pages or as a separate “lesson”. Before Greg (or anyone
>>> > else) says it, yes,
>>> > I know “Pull requests are always welcome”. Let me ask the community -
>>> > Would you rather
>>> > have:
>>> > A separate install “lesson” and links from the other lessons to that
>>> > install page
>>> > -OR-
>>> > Installation information within each separate lesson?
>>> >
>>> > John Moreau
>>> > * http://swcarpentry.github.io/instructor-training/05-expertise.html
>>> >
>>> > From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
>>> > Behalf
>>> > Of Matt Davis
>>> > Sent: Wednesday, February 17, 2016 5:05 PM
>>> > To: Markus Mueller ; discuss@lists.software-carpentry.org
>>> > Subject: Re: [Discuss] installation instructions
>>> >
>>> > Hi Markus,
>>> >
>>> > Our workshop webpages have software installation instructions. We used
>>> > to have those
>>> > on software-carpentry.org, but I couldn't find
>>> > them so here's the website of an upcoming workshop:
>>> > https://joshwaterfall.github.io/2016-02-16-NIH/
>>> >
>>> > Best,
>>> > Matt
>>> >
>>> > On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller >
>>> > wrote:
>>> > Dear listers,
>&g

Re: [Discuss] installation instructions

[Bennet Fauber]

I think that separting the installation instructions is good idea.
That might make them easier for people trying to use the published
material but who are not attending a specific workshop.

In the spirit of writing functions and calling them from larger
scripts, wouldn't we want to write a function for each installation:
bash, git, python, et al., and then refer to the ones pertinent to the
workshop from the workshop site?  Then the same installation
instructions could be used for an Intro Python and an Intermediate
Python.



On Wed, Feb 17, 2016 at 7:15 PM, Moreau, John (UMKC-Student)
<john.r.mor...@mail.umkc.edu> wrote:
> Matt et al:
>
> Perhaps this is the crux of the problem. We no longer have installation
> instructions outside of the workshop pages. More experienced instructors may
> know to check the workshop template on GitHub. However, for newer
> instructors, potential workshop hosts, and drive-by site visitors, there’s
> no clear directions.
>
> Thinking about the problem from the perspective of a novice learner, their
> first instinct will be to check the website. After coming up short, some
> people will become frustrated and abandon the search. Here’s where an expert
> might say “Why didn’t you just* google for {program needed}?” Because the
> novice learner lacks the mental models of an expert, they may not know what
> search terms to use. The Shell lessons suffer from this problem more than
> most:
>
> ·Nowhere on the lesson landing page
> (http://swcarpentry.github.io/shell-novice/) do we mention the term “Bash”
>
> ·The “Introducing the Shell” page
> (http://swcarpentry.github.io/shell-novice/00-intro.html) does not use the
> term “Bash” until the seventh paragraph
>
> ·The intro page does not directly tell a novice learner that the
> standard Git for Windows installation includes Bash.
>
> ·The intro page does mention that the Bash shell is the default
> shell on many modern UNIX implementations. A novice learner may not know
> that Mac OS now uses a UNIX engine and uses Bash for its command line
> terminal. They also may not know how to access the terminal.
>
> ·If a Linux user doesn’t know about the Unix command line, I really
> want to ask them how they got Linux on their machine in the first place.
>
>
>
> For these reasons, I suggest that we should add installation instructions to
> either the lesson pages or as a separate “lesson”. Before Greg (or anyone
> else) says it, yes, I know “Pull requests are always welcome”. Let me ask
> the community -  Would you rather have:
>
> A separate install “lesson” and links from the other lessons to that install
> page
>
> -OR-
> Installation information within each separate lesson?
>
>
>
> John Moreau
>
> * http://swcarpentry.github.io/instructor-training/05-expertise.html
>
>
>
> From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
> Behalf Of Matt Davis
> Sent: Wednesday, February 17, 2016 5:05 PM
> To: Markus Mueller <muell...@landcareresearch.co.nz>;
> discuss@lists.software-carpentry.org
> Subject: Re: [Discuss] installation instructions
>
>
>
> Hi Markus,
>
>
>
> Our workshop webpages have software installation instructions. We used to
> have those on software-carpentry.org, but I couldn't find them so here's the
> website of an upcoming workshop:
> https://joshwaterfall.github.io/2016-02-16-NIH/
>
>
>
> Best,
>
> Matt
>
>
>
> On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller
> <muell...@landcareresearch.co.nz> wrote:
>
> Dear listers,
>
>
>
> I am a new instructor (or soon to be one) and started having a closer look
> at the software carpentry lesson material. I first had a look at the
> instructor guide
> (http://swcarpentry.github.io/shell-novice/instructors.html) and only found
> some general tips and hints about which tools to use and how to install them
> (my interested would here apparently be how to get a unix shell to run on
> windows).
>
>
>
> I apologize if I missed something, but otherwise would be glad if somebody
> could point me to the installation guidelines (that the page above somehow
> hints at).
>
>
>
>
>
> Cheers,
>
>
>
> Markus
>
>
>
> 
>
>
> Please consider the environment before printing this email
> Warning: This electronic message together with any attachments is
> confidential. If you receive it in error: (i) you must not read, use,
> disclose, copy or retain it; (ii) please contact the sender immediately by
> reply email and then delete the emails.
> The views expressed in this email may not be those of Landcare Research New
> Zealan

Re: [Discuss] installation instructions

[Noam Ross]

It would make sense for each lesson to have a link to the install lesson,
though.

On Wed, Feb 17, 2016 at 7:35 PM Matt Davis <jiffyc...@gmail.com> wrote:

> The idea of an installation lesson sounds good to me.
>
> On Wed, Feb 17, 2016 at 4:28 PM Darya Vanichkina <d.vanichk...@gmail.com>
> wrote:
>
>> A separate install lesson, because the lessons are already rather
>> content-heavy, and searching within them for install instructions to email
>> to students to have a go before coming in is confusing.
>>
>>
>> On 18 February 2016 at 11:16:34, Moreau, John (UMKC-Student) (
>> john.r.mor...@mail.umkc.edu) wrote:
>> > Matt et al:
>> > Perhaps this is the crux of the problem. We no longer have installation
>> instructions
>> > outside of the workshop pages. More experienced instructors may know to
>> check the workshop
>> > template on GitHub. However, for newer instructors, potential workshop
>> hosts, and
>> > drive-by site visitors, there’s no clear directions.
>> > Thinking about the problem from the perspective of a novice learner,
>> their first instinct
>> > will be to check the website. After coming up short, some people will
>> become frustrated
>> > and abandon the search. Here’s where an expert might say “Why didn’t
>> you just* google
>> > for {program needed}?” Because the novice learner lacks the mental
>> models of an expert,
>> > they may not know what search terms to use. The Shell lessons suffer
>> from this problem
>> > more than most:
>> >
>> > · Nowhere on the lesson landing page (
>> http://swcarpentry.github.io/shell-novice/)
>> > do we mention the term “Bash”
>> >
>> > · The “Introducing the Shell” page (
>> http://swcarpentry.github.io/shell-novice/00-intro.html)
>> > does not use the term “Bash” until the seventh paragraph
>> >
>> > · The intro page does not directly tell a novice learner that the
>> standard Git for Windows
>> > installation includes Bash.
>> >
>> > · The intro page does mention that the Bash shell is the default shell
>> on many modern UNIX
>> > implementations. A novice learner may not know that Mac OS now uses a
>> UNIX engine and uses
>> > Bash for its command line terminal. They also may not know how to
>> access the terminal.
>> >
>> > · If a Linux user doesn’t know about the Unix command line, I really
>> want to ask them how
>> > they got Linux on their machine in the first place.
>> >
>> > For these reasons, I suggest that we should add installation
>> instructions to either
>> > the lesson pages or as a separate “lesson”. Before Greg (or anyone
>> else) says it, yes,
>> > I know “Pull requests are always welcome”. Let me ask the community -
>> Would you rather
>> > have:
>> > A separate install “lesson” and links from the other lessons to that
>> install page
>> > -OR-
>> > Installation information within each separate lesson?
>> >
>> > John Moreau
>> > * http://swcarpentry.github.io/instructor-training/05-expertise.html
>> >
>> > From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On
>> Behalf
>> > Of Matt Davis
>> > Sent: Wednesday, February 17, 2016 5:05 PM
>> > To: Markus Mueller ; discuss@lists.software-carpentry.org
>> > Subject: Re: [Discuss] installation instructions
>> >
>> > Hi Markus,
>> >
>> > Our workshop webpages have software installation instructions. We used
>> to have those
>> > on software-carpentry.org, but I couldn't find
>> > them so here's the website of an upcoming workshop:
>> https://joshwaterfall.github.io/2016-02-16-NIH/
>> >
>> > Best,
>> > Matt
>> >
>> > On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller >
>> > wrote:
>> > Dear listers,
>> >
>> > I am a new instructor (or soon to be one) and started having a closer
>> look at the software
>> > carpentry lesson material. I first had a look at the instructor guide (
>> http://swcarpentry.github.io/shell-novice/instructors.html)
>> > and only found some general tips and hints about which tools to use and
>> how to install them
>> > (my interested would here apparently be how to get a unix shell to run
>> on windows).
>> >
>> > I apologize if I missed something, but otherwise would be glad if
>> somebody could point
>> > me to the installation guidelines (that the

Re: [Discuss] installation instructions

[Darya Vanichkina]

A separate install lesson, because the lessons are already rather 
content-heavy, and searching within them for install instructions to email to 
students to have a go before coming in is confusing. 


On 18 February 2016 at 11:16:34, Moreau, John (UMKC-Student) 
(john.r.mor...@mail.umkc.edu) wrote:
> Matt et al:
> Perhaps this is the crux of the problem. We no longer have installation 
> instructions  
> outside of the workshop pages. More experienced instructors may know to check 
> the workshop  
> template on GitHub. However, for newer instructors, potential workshop hosts, 
> and  
> drive-by site visitors, there’s no clear directions.
> Thinking about the problem from the perspective of a novice learner, their 
> first instinct  
> will be to check the website. After coming up short, some people will become 
> frustrated  
> and abandon the search. Here’s where an expert might say “Why didn’t you 
> just* google  
> for {program needed}?” Because the novice learner lacks the mental models of 
> an expert,  
> they may not know what search terms to use. The Shell lessons suffer from 
> this problem  
> more than most:
>  
> · Nowhere on the lesson landing page 
> (http://swcarpentry.github.io/shell-novice/)  
> do we mention the term “Bash”
>  
> · The “Introducing the Shell” page 
> (http://swcarpentry.github.io/shell-novice/00-intro.html)  
> does not use the term “Bash” until the seventh paragraph
>  
> · The intro page does not directly tell a novice learner that the standard 
> Git for Windows  
> installation includes Bash.
>  
> · The intro page does mention that the Bash shell is the default shell on 
> many modern UNIX  
> implementations. A novice learner may not know that Mac OS now uses a UNIX 
> engine and uses  
> Bash for its command line terminal. They also may not know how to access the 
> terminal.  
>  
> · If a Linux user doesn’t know about the Unix command line, I really want to 
> ask them how  
> they got Linux on their machine in the first place.
>  
> For these reasons, I suggest that we should add installation instructions to 
> either  
> the lesson pages or as a separate “lesson”. Before Greg (or anyone else) says 
> it, yes,  
> I know “Pull requests are always welcome”. Let me ask the community - Would 
> you rather  
> have:
> A separate install “lesson” and links from the other lessons to that install 
> page
> -OR-
> Installation information within each separate lesson?
>  
> John Moreau
> * http://swcarpentry.github.io/instructor-training/05-expertise.html
>  
> From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On Behalf 
>  
> Of Matt Davis
> Sent: Wednesday, February 17, 2016 5:05 PM
> To: Markus Mueller ; discuss@lists.software-carpentry.org  
> Subject: Re: [Discuss] installation instructions
>  
> Hi Markus,
>  
> Our workshop webpages have software installation instructions. We used to 
> have those  
> on software-carpentry.org, but I couldn't find  
> them so here's the website of an upcoming workshop: 
> https://joshwaterfall.github.io/2016-02-16-NIH/  
>  
> Best,
> Matt
>  
> On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller >  
> wrote:
> Dear listers,
>  
> I am a new instructor (or soon to be one) and started having a closer look at 
> the software  
> carpentry lesson material. I first had a look at the instructor guide 
> (http://swcarpentry.github.io/shell-novice/instructors.html)  
> and only found some general tips and hints about which tools to use and how 
> to install them  
> (my interested would here apparently be how to get a unix shell to run on 
> windows).
>  
> I apologize if I missed something, but otherwise would be glad if somebody 
> could point  
> me to the installation guidelines (that the page above somehow hints at).
>  
>  
> Cheers,
>  
> Markus
>  
> 
>  
> Please consider the environment before printing this email
> Warning: This electronic message together with any attachments is 
> confidential. If  
> you receive it in error: (i) you must not read, use, disclose, copy or retain 
> it; (ii) please  
> contact the sender immediately by reply email and then delete the emails.
> The views expressed in this email may not be those of Landcare Research New 
> Zealand Limited.  
> http://www.landcareresearch.co.nz
> ___
> Discuss mailing list
> Discuss@lists.software-carpentry.org  
> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
>   
> ___
> Discuss mailing list
> Discuss@lists.software-carpentry.org
> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
>   


___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org

Re: [Discuss] installation instructions

[Moreau, John (UMKC-Student)]

Matt et al:
Perhaps this is the crux of the problem. We no longer have installation 
instructions outside of the workshop pages. More experienced instructors may 
know to check the workshop template on GitHub. However, for newer instructors, 
potential workshop hosts, and drive-by site visitors, there’s no clear 
directions.
Thinking about the problem from the perspective of a novice learner, their 
first instinct will be to check the website. After coming up short, some people 
will become frustrated and abandon the search. Here’s where an expert might say 
“Why didn’t you just* google for {program needed}?” Because the novice learner 
lacks the mental models of an expert, they may not know what search terms to 
use. The Shell lessons suffer from this problem more than most:

·Nowhere on the lesson landing page 
(http://swcarpentry.github.io/shell-novice/) do we mention the term “Bash”

·The “Introducing the Shell” page 
(http://swcarpentry.github.io/shell-novice/00-intro.html) does not use the term 
“Bash” until the seventh paragraph

·The intro page does not directly tell a novice learner that the 
standard Git for Windows installation includes Bash.

·The intro page does mention that the Bash shell is the default shell 
on many modern UNIX implementations. A novice learner may not know that Mac OS 
now uses a UNIX engine and uses Bash for its command line terminal. They also 
may not know how to access the terminal.

·If a Linux user doesn’t know about the Unix command line, I really 
want to ask them how they got Linux on their machine in the first place.

For these reasons, I suggest that we should add installation instructions to 
either the lesson pages or as a separate “lesson”. Before Greg (or anyone else) 
says it, yes, I know “Pull requests are always welcome”. Let me ask the 
community -  Would you rather have:
A separate install “lesson” and links from the other lessons to that install 
page
-OR-
Installation information within each separate lesson?

John Moreau
* http://swcarpentry.github.io/instructor-training/05-expertise.html

From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] On Behalf 
Of Matt Davis
Sent: Wednesday, February 17, 2016 5:05 PM
To: Markus Mueller <muell...@landcareresearch.co.nz>; 
discuss@lists.software-carpentry.org
Subject: Re: [Discuss] installation instructions

Hi Markus,

Our workshop webpages have software installation instructions. We used to have 
those on software-carpentry.org<http://software-carpentry.org>, but I couldn't 
find them so here's the website of an upcoming workshop: 
https://joshwaterfall.github.io/2016-02-16-NIH/

Best,
Matt

On Wed, Feb 17, 2016 at 2:53 PM Markus Mueller 
<muell...@landcareresearch.co.nz<mailto:muell...@landcareresearch.co.nz>> wrote:
Dear listers,

I am a new instructor (or soon to be one) and started having a closer look at 
the software carpentry lesson material. I first had a look at the instructor 
guide (http://swcarpentry.github.io/shell-novice/instructors.html) and only 
found some general tips and hints about which tools to use and how to install 
them (my interested would here apparently be how to get a unix shell to run on 
windows).

I apologize if I missed something, but otherwise would be glad if somebody 
could point me to the installation guidelines (that the page above somehow 
hints at).


Cheers,

Markus



Please consider the environment before printing this email
Warning: This electronic message together with any attachments is confidential. 
If you receive it in error: (i) you must not read, use, disclose, copy or 
retain it; (ii) please contact the sender immediately by reply email and then 
delete the emails.
The views expressed in this email may not be those of Landcare Research New 
Zealand Limited. http://www.landcareresearch.co.nz
___
Discuss mailing list
Discuss@lists.software-carpentry.org<mailto:Discuss@lists.software-carpentry.org>
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
___
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org