3

I started to contribute to open source again to improve as a dev and to break away from web stuff, on top of that I want to improve my professional imagine with a rebuilt personal website, decent LinkedIn posting and a more curated GH profile (starting from the name, I’ll replace the childish “edgy” name I’m using with actual name + surname).
The only issue I have is that on my current GH profile there are a couple of issue on random OSS projects which I offered to fix but then I’ve not maintained the promise for mental health or work issues which deprived me of any willpower towards evening programming. Do you think it’s better for me to create a new profile to get rid of these or I can still use my current profile without risking significant reputation damage?

Comments
  • 3
    If the product is live, you should leave them. If it's dead, archive the repo and comment that the project is abandoned. This is especially important with libraries that will get irreversibly lodged in dependency graphs otherwise.
  • 4
    I don't think anyone checks the open issues on your repos, but either way this isn't a personal failure, it's just how unpaid work is. Sometimes projects end, whether they're done or not. Sometimes the author's pet feature gets prioritized over someone else's showstopper. An issue is a request for free labour, you're allowed to turn it down. I'd be much more concerned about open PRs because then you're turning down someone else's work, but even these are often perfectly fine.
Add Comment