Looking for new contributors

[maxcnunes]

I guess I have not been using SQL databases for the last 2 years, which means no Sqlectron as well. I tried to maintain this project as much as I could but I have lost the interest spending my personal time on something I don’t use anymore. That is why I'm formally pausing my work on its maintenance 😢

If you use it and you are interested in keeping this project alive. Please, contact me over here and I will make sure to help you out with anything you need for a smooth maintainer transition.

Overall, thanks to all users and contributors ❤️

[jamieweb]

Thanks for your work, I have found this tool very useful! :)

[logavanc]

Beautiful program, bummed to hear you are dropping it.

[artrz]

Thank you very much for all your work on this. On Linux, Sqlectron is invaluable!

[sscholle]

@maxcnunes I use it! Interested in becoming maintainer.

[vinceramcesoliveros]

Thank you for developing a Wonderful Application. We will wait until someone will volunteer to improve the development of SQLElectron.

[workguy66]

The best one on linux for mysql, mysql workbench is awful

[jacob-israel-turner]

I just came across this project a couple of weeks ago and I love it. Not sure I have the time to take point, but I'd be happy to help maintain it.

[arjunkesava]

I hope, people will fork it and develop on it,
(I did one just now)

[sscholle]

I guess all we need to do is submit PRs back to @maxcnunes ? I'm keen, Ive already found a bug that I just need to fix asap :D

[BakirRabiaSalma]

thank you maxcnunes ,i'm working to improve it so if i'd ask for something , i hope you 'll help me.

[BornaP]

Max, thanks again for all the help and advices you gave to us, contributors. I completely understand you've lost interest maintaining something that you don't use. I can relate to that 😅

I'd just like to point out to future maintainer, that UI code may use some good refactoring. Max is world class engineer, but I think lot of contributions to GUI repo were from people (including myself) that were getting started with React couple of years ago. I think the same was with Max, it was learn-new-technology-make-something-useful kind of project, if I'm not wrong :) Backend part should be good, Max got that covered well.

All in all, what was supposed to be learn&fun project turned into something really useful and that's true beauty of open source. I know people will mostly see the value in the app they use (Sqlectron), but there's additional value to that. Max helped me, and many others, to get started with Open Source, and technologies there were new to us. Speaking on my behalf, he was very patient teacher and OSS maintainer. I've never felt a bit of annoyance in his replies, no matter how dull my question was. That guy is true Open Source Hero if you ask me. @github you hear me? :D

Ps. For future maintainer(s): Maybe you could use Open Collective platform for covering part of your expenses?

[tjbarber]

I would love to be a part of Sqlectron's future, but would definitely want to be working with a few others.

I came to Sqlectron just today while looking for a good relational database GUI that isn't absolute trash on Linux. Not only is it good, it's really good. I don't have time to be the sole maintainer of it, but if there are at least a couple others that would like to spend some time making this project even more awesome I would love to be a part of it.

[joereynolds]

Since this is not maintained anymore, I'd like to recommend dbeaver as an alternative.
It's not as pleasing to the eye but it's very featureful and well used.

[mahongquan]

i fork it,and change a lot on it.
https://github.com/mahongquan/sqlectron-gui

[fuzzy76]

Since several people have expressed interest, this shouldn't really be a problem. @mahongquan did you try to contanct @maxcnunes as he said in the issue? Or @sscholle ?

[sscholle]

just fork it @fuzzy76 - maybe link your fork in this issue - and update your README to the changes you make

[maxcnunes]

I was contacted by mahongquan weeks ago. But I didn't agree with the way the changes were driven on his fork (mostly commit messages and the way changes were done). I spent a long time building this app and I hope to pass the ownership to someone who shares few common guides:

• keep the commit history clean, so it makes easier for contributors to maintain the project (a great article about that: https://chris.beams.io/posts/git-commit/)
• keep the master branch clean, do not commit debugging stuff that should live a separated development branch

I don't want to be picky. I'm just thinking about the future of the project to keep it easy for other contributors to join and understand the project history and codebase.

[dsofeir]

@maxcnunes Have you found a new maintainer?

SQLECTRON is a very useful tool on Linux and seems to have quite the following. It would be a shame to see it fall in to decline. If you are yet to find some I would be interested in discussing it.

[maxcnunes]

@dsofeir I'm still waiting for someone to take it over :) If you prefer to discuss it in private just DM me on Twitter @maxcnunes.

[scottjbarr]

@mahongquan looks like https://github.com/mahongquan/sqlectron-gui looks quite active.

[fuzzy76]

Activity trumps purity I guess

[scottjbarr]

@fuzzy76 If no one takes over, one of the active forks will possibly become the new thing. I'm definitely not saying "busy" is good.

[iamareebjamal]

@scottjbarr Just see the commit messages and the content of those and message by @maxcnunes above and you'll understand. Standards in open source projects are very important and commits should be meaningful atomic unit of code change which have 1:1 correspondence with a feature or bugfix

[RHieger]

I am a current student at Woz U and just finished a course in ReactJS. I see that your project relies on React (at least partially). While I am in the 24-Week bootcamp program, I might not be able to contribute much, but I do like the interface of your application, and as time might allow in the near future, I would be happy to contribute and interested in doing so.

My focus has been and remains Full Stack Web Development/Design, and a tool such as sqlectron might be very useful and expedient for that work.

Thank you for your development work on this project thus far, and I wish you the best in all your future and current development work.

[dflock]

So... @barneydmedia just did a new release of SQLElectron: https://github.com/sqlectron/sqlectron-gui/releases 🎉 - so is this issue closed, then?

[barneydmedia]

There is a new build out, and I plan on taking a look at some of the other issues. I would like to see the project continue, personally.

[dsofeir]

@maxcnunes @barneydmedia I started using sqlectron has an alternative to MySQL Workbench and the lack of a comparable Atom package. Specifically there is no Atom package which offers SSH tunneling to a MySQL host.

Since this discussion is about the continuation/future of the project. Do you think packaging sqlectron as an Atom package would be a good future direction? This would expand the potential user-base and potentially attract new contributors.

[barneydmedia]

I think it would be cool, and I think it would be a good thing. I also think it would be a lot of work and could potentially split the codebase in consequential ways.

I'm not able to do it, but I also wouldn't be against someone else making an effort on a separate fork to later add/merge. I would also love to see more users and contributors here.

[maxcnunes]

Hey @barneydmedia, or anyone who comes after you, feel free to close this issue and remove the unmaintained labels from the project if you think you are ready to take over the project. 🙏 🎉

For others interested in taking over, I just answered an email to @dsofeir with details of how to do it, and it is the same for anyone else:

I'm looking for people who can improve this project or at least keep the existing quality. In my opinion, the best way to analyze it is through a PR so I can check those details. For example, @barneydmedia sent a PR #436 and I added him as a contributor. Then he merged and released a new version himself.

[JARVIS-AI]

one year passed, so its maintaining yes ?

[rathboma]

Hey! I'm on the maintainer list now. I'm just wrapping up some project work and will be able to take more of a look at the project at the end of the month and actively start moderating and contributing. Stay tuned! My first task will be bringing dependencies up to date and fixing any critical bugs.

[krolow]

thx @rathboma it's going to be great to have someone active in the project! I'd love to help as much as I can but it's not a software that I'm using nowadays (I'm not using relational db 😞) but I can for sure help in code review... I'm looking for to see yours PR'S @rathboma 💪 👏

[ferm10n]

@mahongquan why haven't you submitted a pull request yet?

[rjpcasalino]

@rathboma please ping me or whatever on certain issues - I can see what I can do

[rathboma]

Honestly folks I thought my work would be letting up, but it's not really, so I'm not sure how much time I'm going to actually have to work on the project :-(

[the94air]

@rathboma Since you don't have time a Discord server is a good idea to let anyone collaborate to bring this project back.

[the94air]

@rathboma Since you don't have time a Discord server is a good idea to let anyone collaborate to bring this project back.

cc @maxcnunes @BornaP @barneydmedia @krolow @rathboma

[maxcnunes]

Not sure if a Discord server would make much difference. There is already a Slack team but there have not been any interactions there since I announced I was stopping my contribution to the project. Anyway, the team still available if anyone wants to use it - https://sqlectron.herokuapp.com/

[DCdeBrabander]

Don't know which version is currently latest / the go to, but I am also interested to do some UX stuff if need be. Current (official) version I use, on Linux, lacks some basic features like 'in place editing'.

If Discord server is running, please send me an invite :D

[jcklpe]

This project looks cool. Anyone who has the most recently maintained fork, please let us know.

It's kind of crazy how bad pretty much all other SQL clients are, UX/UI wise.

[maniadevice]

Hope this project gets revived. But in the meantime, for those looking for a linux alternative - Tableplus just released an alpha version.
https://tableplus.com/linux

[dsofeir]

@maniadevice I believe advertising a product which is NOT open-source in this context is inappropriate and you should remove or clarify your comment.

[maniadevice]

Sure, I can clarify.
I am not advertising this product. I am not associated with them in any way, nor am I getting any benefit out of it.
Yes, it's not an open source product. I am a Linux user and a lot of people here have mentioned how helpful sqlectron was to them. I have only tried to help them by suggesting a (currently) free product, that they could use - maybe until sqlectron is back to being actively maintained.

I'll be glad to remove the comment if one of the members are also offended it. No problem at all.

[dsofeir]

Thank you @maniadevice for the clarification. I only objected because your initial comment had the appearance of an advertisement for a commercial product.

[albertotorresfoltyn]

I can be a part time mantainer

[rathboma]

Hey everyone.

I wanted to write you all with an apology and a reason for why I haven't contributed much to this GUI.

Back in 2019 when I tried to get involved in Sqlectron I totally underestimated the learning curve of Electron, Electron Builder, and React. Honestly I was totally unable to solve even simple problems.

I started playing with the SQLectron core libraries in a new Vue electron project to sort of figure out how everything should fit together.

In the end, the out of date dependencies and React-based UI was too much for me. So in collaboration with a friend I decided to build a fresh UI on top of the Sqlectron core libraries. I released the app a couple of weeks ago:

https://github.com/beekeeper-studio/beekeeper-studio

If you look at the Github the commit history the code is a fork of sqlectron-core. So in a very real way it is a continuation of Sqlectron.

I'm sure many of you might be disappointed by my actions. I understand that. Thanks for being a welcoming community either way. I plan on continuing maintenance of Beekeeper Studio and hope some of you might become part of the project.

Thanks again.

Matthew

[MasterOdin]

I chatted with @maxcnunes and will be taking over maintence of sqlectron project. A new release should be forthcoming later on this week which will have a number of fixes and features. Will leave this open for now, in case some other people are inspired to contribute.

[TomGranot]

Downloading now - let's see what gives! Been looking for a SequelPro alternative ever since coming over to Ubuntu.

[ghost]

@MasterOdin Still looking for more contributors? I use this tool daily on my linux and mac machines and I'd love to contribute some code to the project.

[albertotorresfoltyn]

@MasterOdin Still looking for more contributors? I use this tool daily on my Linux and mac machines and I'd love to contribute some code to the project.

Would you like to start a fork and work from there? I'm in a similar situation here

[MasterOdin]

More the merrier, feel free on making PRs and such. I'm looking to release 1.31.0 in a day or so as it's got a nice bit of improvements here:

1.31.0 changelog

• Add option to list connections instead of rendering cards (Can we have an option to display DB hosts styled as list, not only as card? #425) - by @barneydmedia
• Allow custom UI fonts (How to change app font and editor font? #330) - by @barneydmedia
• Single clicking table name runs a default query - by @barneydmedia
• Fix NaN error on zoomFactor label on first startup (fix NaN on zoomFactor label #445 #457) - by @barneydmedia
• Fix query results error if no custom font is set (Fixes #469 - query results error out if no custom font is set #470) - by @rathboma
• Move from Travis / appveyor to GH actions for CI (Move to GitHub actions for building project #492) - by @MasterOdin
• Update node-sass to 4.14.0 (Update appveyor build configuration #486) - by @MasterOdin
• Update axios to 0.19.2 (update axios to ^0.19.2 #489) - by @MasterOdin
• Update electron-builder to 21.2.0 (upgrade electron-builder to ^21.2.0 #491) - by @MasterOdin
• Add MariaDB to server type dropdown (functionally equivalent to selecting MySQL) - by @MasterOdin
• Update sqlectron-core to 8.1.1 (bump sqlectron-core to ^8.1.0 #484) - by @MasterOdin
  • Add cassandra authentication support
  • Support MySQL caching_sha2_password authentication (default for MySQL 8)
  • Add official support for MySQL 8
  • Add official support for PostgreSQL 12
  • Add official support for cassandra 2.x and 3.10+
  • Add official support for MariaDB 10.1+
  • Fix regression on querying information_schema tables on MySQL 8
  • Fix not being able to specify socket without a port - by @rathboma
  • Use ordinal_position to order column listing for all postgres, mysql, and sqlserver
  • Fix truncateAllTables for sqlserver not working with foreign key constraints
  • Fix sqlserver breaking if using CS collation

I've started triaging issues for a 1.32.0 release, but the focus for me is principally on upgrading electron to the newest version and adding official support for CockroachDB. The following release I plan to begin work on upgrading react to a newer version.

[jamesanto]

@MasterOdin Anything I could do to get 1.31.0 released?

[jamesanto]

Ah, never mind, it's already released.

[MasterOdin]

Yup, and progress is steadily being made to a quicker 1.32.0 follow-up. While I was somewhat planning on trying to add more official cockroach and redshift support in this version, I think I might hold off and get 1.32.0 out quicker to hopefully resolve the usage problems people were seeing with dependencies and such.