browsh-org/browsh

Browsh's short-term future

Open

#168 opened on Aug 4, 2018

View on GitHub
 (14 comments) (19 reactions) (0 assignees)JavaScript (15,996 stars) (455 forks)batch import
help wanted

Description

So I, the creator of Browsh, have just started a full time job, that will likely last up to 6 months. Browsh still has some really big issues to face; most notably in text rendering, but also I'd really like to see the Vim mode happen soon. Unfortunately I'm just not going to have much time to take care of these problems in the short-term.

I do now however have some modest sums of donations now coming through on a regular monthly basis, so I want to honour them and try to increase them, such that I might be able to make Browsh my main "job", so to speak.

If you look at the Roadmap project, you'll get an idea of what I'm prioritising, basically it's a mix of what I think are the worst bugs and what I think I could build upon later to charge money for Browsh as a Service. However, of course contributions will still be welcome for any part of Browsh.

Contributor guide

Tech stack
javascript
Domain
None
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
This issue is a meta discussion about the maintainer's temporary unavailability and does not define a specific task. To contribute, review the roadmap project linked in the issue and consider picking up concrete issues like #31 (Vim mode) or text rendering improvements. The repository is written in Go and JavaScript, so focus on those languages. Look at the codebase for areas like terminal rendering or the web extension.