move v-analyzer to main v organization?

[verulian]

Describe the bug

seems with v-analyzer isolated here in this project its life is a bit risky. i think everyone would feel better to see it moved to v's main project hierarchy to protect it from having something strange and bad happen to it like the other v tools that the other group was working on.

Expected Behavior

move v-analyzer to github.com/vlang

Current Behavior

living separately

Reproduction Steps

n/a

Possible Solution

No response

Additional Information/Context

No response

Environment details (v doctor output)

n/a

Editor name

n/a

v-analyzer Version

n/a

VS Code Extension Version

No response

[i582]

Hey,

life is a bit risky. i think everyone would feel better to see it moved to v's main project hierarchy to protect it from having something strange and bad happen to it like the other v tools that the other group was working on.

It’s interesting to hear, but the project is threatened not by being in another organization, but by the lack of qualified developers who could figure it out and make a significant contribution. If you think that the project will be safe in V's organization, then you are mistaken. Here is a list of projects that are there and they are dead (have not received active development for a year or more):

• VLS
• Vinix
• Go2V
• C2V (almost dead)
• UI
• Gitly
• heroesV
• Playground
• py2v

This project was created separately so as not to repeat this trend that you do not want to notice, but the irony is that this project will suffer the same fate for the reason “the author of the language believes that he can do anything.” Like V's other projects, this project will be abandoned and die.

[verulian]

i don't know. i think that your argument lacks integrity given what has happened. i can't even find the other projects now that you've deleted them like the documentation i enjoyed, playground and stuff. hard to grasp the logic in what's being said here, it's like we're talking past each other and missing the point of what makes open source great.

v lost good stuff like documentation and playground, and now it's like you're trying to come back to the community in some twisted way after damaging it. something rotten somewhere here. it's not just about projects being dead or alive, it's about the community, sticking together and not letting good work go to waste. your actions are hostile to this ideal.

you're making good points that my suggestion is best path for this.

@antono2, no offence but you sound like just echoing what someone who already gave up on the community is saying. we need to bring v-analyzer back to the main v, where it can get real support and grow, not leave it out in the cold. why make it harder for the community?

let's not kid ourselves, this isn't just about project management or some hierarchy nonsense, it's about us not letting our hard work fall apart because of some disagreements and hurt feelings. v should pull together, not apart. this isn't just about code, it's about what v is as a community. a vls project like this is essential. you know this. this is why you're "defending" this little project. ulterior motives are made open. 👃💩

[i582]

@verulian

v lost good stuff like documentation and playground

https://docs.vosca.dev/
https://play.vosca.dev/

and now it's like you're trying to come back to the community in some twisted way after damaging it

v-analyzer is my project and if I respond to an issue it does not mean that I am trying to return to the community

it's about the community, sticking together and not letting good work go to waste.

And what did this community do together so that the work did not go to waste if we are talking about those projects that I listed in my first answer?

we need to bring v-analyzer back to the main v, where it can get real support and grow, not leave it out in the cold. why make it harder for the community?

Why are you so sure of this? Are you operating with your ideal ideas about open source or the real situation in V, which I know very well?

v should pull together, not apart.

This requires a leader, a real leader, which V does not have.

Overall, perhaps a year ago I would have agreed with you, but this year a lot has happened that has turned me away from V and I no longer intend to help this language, I spent a year and a half of my life on V but received only disappointment. No one will force you not to go through this path yourself and waste so much time, but maybe you should look at V more critically.

[spytheman]

And what did this community do together so that the work did not go to waste if we are talking about those projects that I listed in my first answer?

Everyone interested can work on them.
For example, I have fixed things in most of them.
I've fixed things in this project of yours too, while you neglected it, for several months.
I will also continue to do so, for as long as I am allowed.

This requires a leader, a real leader, which V does not have.

Would that be you @i582 ?

[spytheman]

@verulian I see no reason, for v-analyzer to be under https://github.com/vlang/, as long as it can be maintained, and not abandoned.

@i582 has given maintenance rights to both me and @joe-conigliaro , so we can do it, even if he (Petr) personally prefers to not be involved anymore.

[i582]

Everyone interested can work on them.
For example, I have fixed things in most of them.

@spytheman this is important work too, but I’m talking about the active development of projects.

I've fixed things in this project of yours too, while you neglected it, for several months.

Thank you.

Would that be you @i582?

I once thought about this, but now I think that while Alex rules everything in V (and this will be forever because this is his project), the project is doomed and investing time in it is a waste of time.

[demizer]

@i582 you did a great job on Vosca and v-analyzer. Sad to learn you had a falling out with the creator of V. Thanks for not deleting your work.

[verulian]

@demizer he did delete his work 🫠 several repositories are no more https://github.com/orgs/vlang-association/repositories

[demizer]

I just saw that vosca.dev was still up, didn't realize the repos were deleted. Sad. Anyways, it looks like vls is going to get reworked, eventually. The tree-sitter portion of this repo is still good and that should be moved to it's own repo in the vlang github org for sure.

At least when things are in the vlang github org Alex M. can at least assign other people as maintainers to the subprojects. If the current maintainers of v-analyzer decide they don't want to be around anymore then someone will have to track them down to get maintainer rights.

[i582]

it looks like vls is going to get reworked, eventually.

@demizer why? What's wrong with the current implementation that you want to change it? On the contrary, my opinion is that the tree-sitter part is the weakest here and because of it there are a lot of problems with parsing some code.

At least when things are in the vlang github org Alex M. can at least assign other people as maintainers to the subprojects

Why do you think so? I don’t remember a single such appointment; if someone works on a project, it’s because person created it or person’s interested in contributing.

P.S. And also why didn’t he appoint maintainers for the projects from my first answer?