New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address the "bus factor" of Buckets #320

Open
iffy opened this Issue Dec 3, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@iffy
Contributor

iffy commented Dec 3, 2018

No description provided.

@iffy iffy added the bug label Dec 3, 2018

@iffy iffy added this to the v1.0.0 milestone Dec 3, 2018

@joneshf

This comment has been minimized.

joneshf commented Dec 4, 2018

Thanks for making this issue! It makes me feel like you listen to us, and that the survey was useful to take.

Any preliminary thoughts on how you might deal with this concern?

@iffy

This comment has been minimized.

Contributor

iffy commented Dec 4, 2018

I think this is actually 2 issues:

  1. My capacity as a solo developer (i.e. throughput, bandwidth)
  2. What would happen if the bus got me (or some other life change that prevented me from continuing work on Buckets)

I've mostly given thought to the latter and plan to prepare a document for that. But I think I ought to give more thought to the former, too. Regarding the latter, my preference is to either hand it off to friends/family (who are also programmers) or open source it.

@Limezy

This comment has been minimized.

Limezy commented Dec 14, 2018

Very interesting subject. However, why did you label it as a "bug" ?

@iffy

This comment has been minimized.

Contributor

iffy commented Dec 14, 2018

@Limezy Mostly because bugs have a red label (and I have lists where bugs feature more prominently) so they're harder to forget :) But you're right that it probably isn't technically something that prevents people from doing their budget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment