At a glance
The Common Council held its regular monthly meeting on April 28, 2026. The Council paid its bills and passed a long slate of routine resolutions, but the evening was dominated by two neighborhood fights: residents near the redeveloped Pocketbook Factory pressed the Council over constant noise from the building's rooftop machinery, and a series of speakers urged the Council to adopt a long-debated code clarification limiting industrial activity on the Hudson waterfront. Three local laws, on short-term rentals, video conferencing, and the waterfront code, were formally distributed for a vote next month. The Council also weighed a Minneapolis affordable-housing idea and an early, contested move toward charter revision.
Opening & Roll Call
The Council opened its regular April meeting, took roll, and placed the month's minutes, committee reports, and communications on file.
Key points
- Roll was called and the meeting opened; minutes from the March 24 regular meeting, committee reports, and communications were accepted and placed on file.
- Two of the communications concerned the Pocketbook Factory, a resident petition and a written response from the building's operator, setting up the meeting's first major discussion.
This page is built from YouTube's automatic captions of the meeting. That transcript has no speaker labels and garbles many names, so this summary describes who spoke by role rather than by name. Check anything important against the city's official minutes.
Pocketbook Factory: neighbors' noise and parking complaints
Residents living near the redeveloped Pocketbook Factory pressed the Council over constant noise from the building's rooftop machinery and over parking pressure in the surrounding streets.
Key points
- A resident who organized a neighborhood petition said the building's rooftop mechanical units, HVAC and restaurant exhaust, produce near-constant noise that he has documented with a decibel meter, and that readings sometimes exceed the city's nighttime limit, especially for homes in the corridor between Prospect and Washington Streets.
- A representative of the Pocketbook Factory said the project is in full compliance with city code, was fully permitted, and was overseen by city code enforcement, the State Historic Preservation Office, and the National Park Service. He said the operator wants to be a good neighbor and is negotiating a long-term lease of a nearby parking lot.
- Residents also called for residential parking permits, arguing homeowners who pay high taxes should be able to park near their homes.
- The Council President said noise and parking are not matters the Council can act on directly, and referred the petition to the Council's Safety committee, urging residents, code enforcement, police, and the mayor's office to verify that what was built matches what the Planning Board approved.
The petition goes to the Council's Safety committee. The Council President asked that residents, code enforcement, the police, and the mayor's office work together to check the building against its Planning Board approval.
Bills and a slate of resolutions
The Council paid its monthly bills and passed a long list of resolutions by roll-call vote. One resolution, an honorary street naming, was tabled.
Key points
- The monthly bills were approved.
- Resolutions passed included: appointing commissioners of deeds; a Climate Smart Community task force appointment; accepting senior center donations; the 2025 firefighter service-award program; license agreements (including one with the Hudson River Historic Boat Restoration & Sailing Society); DPW fund transfers for street lighting; training for Planning Board members; EV-charging-station contracts; the 2026 events awards; authorizing a public hearing on a federal Community Development Block Grant project; and a transfer to a capital fund for parking-kiosk installation.
- An honorary street-naming designation was tabled: city code requires a unanimous Council vote to name a street after a living person, and two members were absent. It returns next month.
Resolution titles here are drawn from a rough automatic transcript; check the city's official agenda for exact wording.
Three local laws head toward a vote
The Council formally distributed three local laws for a vote next month, after discovering it had never adopted a protocol for sending legislation to members electronically.
Key points
- The Council President explained that laws had been shared electronically, but the Council had never formally adopted electronic transmission as its official method, so printed copies were physically placed on members' desks to satisfy the legal notice requirement.
- The three laws: a short-term-rental (STR) local law; a cleanup of the city's video-conferencing rules; and a clarification of the waterfront zoning code (Chapter 325).
- The waterfront code clarification is not ready for a vote. The Council President said it needs more research into litigation risk and an updated preamble before it can be sent to the county and the local planning board for the required review.
The short-term-rental and video-conferencing laws are expected to be voted on at next month's regular meeting. The waterfront code clarification needs more work before it can advance.
Public comment: residents push to limit industry on the waterfront
A series of speakers urged the Council to adopt the waterfront code clarification, framing it as protecting limits on industrial activity that Hudson set in 2010.
Key points
- A resident urged adoption, citing guidance from the New York State attorney who helped Hudson develop its Local Waterfront Revitalization Program (LWRP). She argued that a dock permit without clear caps on intensity of use is more valuable to an owner, and that the city should not be deterred by threats of litigation.
- A local business owner recounted Hudson's 2010 defeat of a multinational company's proposed industrial expansion on the waterfront, after which the city updated its zoning to cap industrial operations. He described the proposed law as a clarification that reaffirms those existing 2010 limits, not a new restriction.
- Residents living near the waterfront described a sharp increase in gravel-truck traffic, safety concerns crossing the railroad tracks, and dust and air-quality concerns from uncovered trucks.
This thread connects to Hudson's Local Waterfront Revitalization Program (LWRP), the 2010 zoning changes that followed a contested industrial proposal, and a 2020 truck study. A fully built Hudson AI would follow the waterfront across every meeting and board where it surfaces.
New business: an affordable-housing idea, and a debate over charter revision
Council members raised a Minneapolis affordable-housing program and the early steps toward a Hudson charter revision, the latter drawing pushback that it is moving too fast.
Key points
- A council member described Minneapolis's "4d" program, which gives small landlords a tax incentive to keep units affordable, with limits on rent increases. The city attorney cautioned that New York municipalities can only do what state law specifically authorizes, so a local tax incentive would face legal hurdles. The Council agreed to obtain and review the program details.
- A council member said they are assembling a committee and collecting letters of interest from residents, connected to a possible charter revision.
- In public comment, a resident argued the charter-revision invitations are premature, the Council should first study the options for forming a charter revision commission under state municipal home rule law, ideally with a presentation from counsel. Another speaker warned, from experience with New York City charter change, that the process can cause unintended harm and should be approached carefully.
- Hudson's last major charter revision was in 1973; speakers urged a slow, transparent process with strong public participation.
About this page
FUTURE HUDSON is an experiment in civic engagement: every public meeting of the City of Hudson since January 2026, transcribed and made readable, so any resident can follow what the city is deciding without attending every meeting. This page covers one meeting; see the full archive.
How it was made
The meeting video was transcribed automatically; the transcript was then organized into sections and summarized. The raw transcript is above, every claim can be checked against it.
What to be skeptical of
The transcript is automated and contains speech-recognition errors; names and numbers may be wrong. This page has not been reviewed by a human. Nothing here is an official record, the city's official minutes are authoritative.