BEE-L Archives

Informed Discussion of Beekeeping Issues and Bee Biology

BEE-L@COMMUNITY.LSOFT.COM
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Sender:
Informed Discussion of Beekeeping Issues and Bee Biology <[log in to unmask]>
Date:
Thu, 23 Jul 2020 10:34:54 -0400
Reply-To:
Informed Discussion of Beekeeping Issues and Bee Biology <[log in to unmask]>
Subject:
Re: beekeeper's code
Content-Transfer-Encoding:
quoted-printable
Message-ID:
<[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Type:
text/plain; charset=utf-8
From:
Przemek Skoskiewicz <[log in to unmask]>
Parts/Attachments:
text/plain (15 lines) 
It depends on the state regulations in the US. Prof. Bromenshenk drills into every participant of his UMT classes that Montana was the first state with regulations for beekeepers. Depending on the type of apiary, there’s a proscribed buffer requirement: https://agr.mt.gov/Honeybees <https://agr.mt.gov/Honeybees>. In NY, with voluntary apiary registration, it’s a free for all.

Przemek

> On Jul 23, 2020, at 6:15 AM, Peter Armitage <[log in to unmask]> wrote:
> 
> […]
> What do you make of this notion of a “beekeeper’s code”?  Do you have one in your part of the beekeeping world, and what does it mean?  What is the content of this code?


             ***********************************************
The BEE-L mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software.  For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html

ATOM RSS1 RSS2