Split efforts and split community is being generated

[Kronuz]

I strongly believe this should not be happening. A lot of users are already using SublimeCodeIntel and this is a fork of the same project. I do think your new additions and your efforts are great @wizza-smile, and I still don't see what is the purpose of forking an already well established project with a very large userbase instead of directly contributing to it.

It is my believe that forking a project should not happen except under plea of dire necessity and with very strong justification; i.e., only when goals are very different, when people with commit access (core developers) don't accept features or patches from contributors, if core developers themselves cannot agree in what direction to go, or if core developers reject direction or use cases the community members want. None of the above is true in this case, and stating "competition" as an argument is not enough reason to split efforts for me.

The goals and roadmap I wanted for SublimeCodeIntel can be delayed/changed and put on the table for discussion, I'm a reasonable man; and the least I want is to hurt the project or see the userbase confused about what to use. For everyone's sake, I'd rather step down the project if my efforts are no good enough for the community.

If your concerns are that you want to be able to release new versions and have a big saying in what the direction of the project is, you are more than welcome to join the SublimeCodeIntel organization as a maintainer. We need all the help we can get and someone interested as you are and with the skills you have would allow for a faster growing project with more ambitious and bigger goals.

I propose we talk and build a roadmap and join efforts to find help getting the project's goals fulfilled. I hereby formally extend an invitation to join efforts instead of diverging them.

[ghost]

@wizza-smile i think you should join to SublimeCodeIntel maintainer man. it's better and don't make people confusing what to use.

[wizza-smile]

Hold on, I'm working on an answer!

[wizza-smile]

@Kronuz I appreciate the invitation to join SublimeCodeIntel organization, but I am still a bit reserved about the substance of your (admittedly) wise and friendly words. There hadn't been one commit from you between 2013 and recently. I want to be sure that your concerns are really about the community (the people you mostly ignored for quite some time) and not about keeping your reputation as Mr CodeIntel.

You are not indispensable, but extremely valuable to the future of Sublime CodeIntel, so we will all like you to continue caring about the project! I am open to put the CodeComplice under the hoods of the organization, once I have finished making it in every respect the best version of the plugin yet (which I think is close enough but not there yet).

To finish this job I will need help in form of users who are willing to test features that are not completely stable yet. Certainly not every user is such a user! What I think would be best for the project is downgrading SublimeCodeIntel to version 2.0.6, the one people have been using satisfactorily for the last two years. A lot of users will not mind, and the ones who are minding have the choice to switch to CodeComplice. Those switching will be that kind of users I desperatly need, naturally! Also this will free you from issues that are not obviously connected to pre or post 2.0.6 code.

What I would like you to do (since you are the perfect choice for that) is to give support to those people, where SublimeCodeIntel is not working at all. I am talking mostly about this issue of course:
SublimeCodeIntel/SublimeCodeIntel#286
This has been around for long and it is time to find a solution.

Also there is this problem that the package crashes SublimeText if added to ignoredPackages while in use. You could also investigate that!

We could exchange our insight on open issues and discuss if how to serve the community best.

If everything is working out fine, I'll be honored to join SublimeCodeIntel organization as a maintainer.

Thanx for reading!

[pschneider]

+1 thanks for the effort.

CodeIntel is something that's really great for sublime text and needs a great plugin!

[oktayacikalin]

+1 for joining forces! Maybe this little competition-play will bring some fresh fruits to us nevertheless. But plz stop forking around soon :)

[anentropic]

please work together, this forking seems premature

[cweagans]

👍 for working together.

[meigallodixital]

+1 to work together

[telephone]

I'm happy with a forked version, as I'll install whatever version @wizza-smile is working on. 👍 man, you've done a great job so far!

@Kronuz I don't mean to be rude, but why are you only offering a maintainer spot now that wizza-smile started contributing to a new fork/project? He's the reason why development started again after the long slump...

P.S. I'm one of those users who was left high and dry for >2 years with the 100% CPU usage bug. If wizza-smile wasn't here, SublimeCodeIntel would still be on my shit list.