What is the relation to https://pigeons.computer/ ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, shell
- Domain
- documentation
Research direction
Inspect README.md, the GitHub About section, and the pigeons.computer Open source and installation sections. Align the project links and installation URLs across GitHub and the landing page; it is done when both sites link to each other and present the same installation link.
Written by the indexing model from the issue text.
Description
https://pigeons.computer/ seems to be the landing page of this project, but right now neither the landing page links the GitHub page, nor the GitHub page links the landing page, which puts me off as a new user.
What I expect:
- The About section of GitHub to link to https://pigeons.computer/ (or in README.md, or in both)
- https://pigeons.computer/ links to GitHub page (pigeons.computer already has the appropriate "Open source" section)
- Right now, installation instructions use different domains (
curl -fSsL https://vorc.s3.us-east-2.amazonaws.com/pigeons-install.sh | bashfor GitHub, andcurl -fSsL https://pigeons.computer/install.sh | bashfor pigeons.computer). I expect them to use the same link.
pigeons.computer is a great way to access your ssh machines behind firewalls, I am excited for the work you do at iroh. But in it's current state, pigeons makes bad first impression and just looks shady because of the mentioned reasons.
Sidenotes
Your other site https://www.iroh.computer/sendme has the same problem, and it even has already an issue raised: https://github.com/n0-computer/sendme/issues/77
https://www.dumbpipe.dev/ gets it right though (except for the installation methods which are different between the site and the GitHub page)
- Dominant language
- Rust
- Stars
- 207
- Forks
- 9
- Avg merge
- 12h 25m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from n0-computer/pigeons
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
n0-computer/pigeons#33 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
n0-computer/pigeons#27 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
n0-computer/pigeons#25 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
n0-computer/pigeons#24 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
n0-computer/pigeons#13 ·
All issues in n0-computer/pigeons
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100