PythonIreland / PythonIreland/2026.pycon.ie

Add visa support information and letter-of-invitation process

Open
#133 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1
Forks
0
Avg merge
10m
Merged PRs (30d)
1

Description

Summary

Add clear information for attendees who need a visa to enter Ireland, especially those travelling from outside the Schengen Area (or outside the EU/EEA). This should include a process for requesting an official letter of invitation.

Motivation

Ireland is not in the Schengen Area. Travellers from many countries require a short-stay (C) visa from the Irish Naturalisation and Immigration Service (INIS). Without a letter of invitation from the conference, visa applications can be refused or delayed. Providing this proactively removes a significant barrier to international attendance.

Scope

  • Confirm with organisers who can sign/issue official letters of invitation
  • Create a visa information section — either a dedicated page (/visa/) or a section on an existing travel/FAQ page
  • Content should cover:
    • Whether a visa is required (link to INIS visa checker)
    • How to request a letter of invitation (email address or form, required information to provide)
    • Expected turnaround time for the letter
    • Disclaimer (letter supports the application but does not guarantee a visa)
    • Useful external links: INIS, Irish embassy/consulate finder
  • Consider adding a simple request form or a dedicated email alias (e.g. visa@pycon.ie)
  • Link the page from the registration/tickets flow and the CFP page (speakers also need visas)

Notes

  • Ireland operates its own visa regime; the Schengen visa does not cover Ireland
  • The letter of invitation should state the event name, dates, venue, and that the person is registered/accepted as a speaker or attendee
  • Process should be in place before ticket sales open (#21)

References

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by confirming with organisers who can issue invitation letters and inspect the existing travel/FAQ, registration/tickets, and CFP pages. Decide whether the information belongs at /visa/ or an existing page, then cover visa eligibility, the request process, turnaround, disclaimer, and official links. Done means the page is linked from registration and CFP and the process is agreed before ticket sales.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, web-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.