Looking for new maintainer(s) #911
Comments
I would love to contribute! |
This makes me so sad. Unfortunately, I have neither the time or experience to contribute. For the longest time, |
@joefitzgerald I assume no maintainers have been found? |
@james-lawrence not yet, sadly. |
@joefitzgerald how much work do you estimate to bring it up to speed with latest gomodules stuff using the langauge package? I might be willing to at least maintain it to that point in the interim |
@james-lawrence we actually did a fair amount of work preparing for the Go language server (which is where you'll get most of the modules support) by leveraging atom-ide-ui for most of our functionality. You could rip out a lot of code and simply rely on the language server integration instead. The challenge is that atom-ide-ui is no longer maintained, so when you hit limits to what it supports, you'll find yourself either trying to revive a dead project, looking for alternatives, or reimplementing your own. |
Anyone noticed this issue has number #911? (Sorry for non-constructive comment). I love(d) Atom and the go-plus duo, I'm sorry to see it fade away. Indeed, having no code completion for modules is a big handicap, and it costs developers a lot of time having to check the docs all the time.. Thanks for all your work over the years. |
go-plus
has been a tremendously enjoyable experience for me and it has led me to meet wonderful people (hat tip to @zmb3, @lloiser and many others).I no longer have the time to effectively maintain the project. I spend most of my time now working in another editor. I believe it is important to allow people who work with
go
in Atom to have the best experience they can possibly have.As a result we are looking for additional maintainers. If you love working with
go
in Atom, and want to continue the evolution of this package, please let us know.In the meantime, this package will not be updated. Thank you so much for using the package over the course of the past 5 years 🙏.
The text was updated successfully, but these errors were encountered: