I’m talking specifically about the current lack of project organization on the GitHub account. The lack of documentation & code notes. The lack of proper revision/releases. The project would get a D- in terms of Organization, and this stems from having one person shoulder 99% of the development.
This cannot change unless people feel welcomed to contribute. Overly aggressive “enforcement” does the opposite.
That’s great. But in business this would be a huge red flag. A single point of failure.
The only way for this to ever change is for him to be willing to work with others. Publish submission guidelines. Show others his validation/testing methods so they can share the burden.
If he doesn’t want that, then perhaps a community fork is in order.
We are just getting there, Rome wasn’t build in one day! Benjamin has now more time than ever to work on that stuff. That we have what we have is sort of a merical. I’m actively looking for helping hands on the code base.
Then I hope you can understand exactly why I’ve stressed how your actions can have a negative impact on creating a welcoming environment for developers.
How many years has the codebase been on GitHub?
You may want to consider changing how this has been managed moving forward. Clearly there is room for improvement given the number of active developers on such a largely used project.
Idk if I speak for anyone but me but I don’t really have any brand loyalty when it comes to esk8 anyway… I’ll use whatever works the best & most reliably. Today the vesc, tomorrow the neobox, eventually - who knows?
I don’t have brand loyalty but I will always prefer the open source version of a product, even if it means giving up some features. When riding I don’t complain about the firmware on my ESC, so until something replaces it, it’s going to be VESC based for the foreseeable future.
Here we go again, people should just learn to ignore Trampa and do their own thing whether frank bitchs about it or not. A lot of people have argued with him and no one has ever changed his mind because he is just so stubborn, most of his threads are just political discussions that go nowhere except to rile people up some more.
We should lock this thread up and close it down.
Why does every new esc fork need to be processed and analyzed by Vedder? I find it shockingly hard to believe he is the only human being capable of improving existing tech.
This open source present feels like a very closed future.
The fork doesn’t need, only the commit, he analyzes it and merges into the main branch. You can’t merge random commits that anyone can submit without looking at it first
@jeffwuneo In my opinion forking it makes no sense, in the recent time Benjamin has been merging a lot of commits, you make your own branch, and then you vanish, now what? Everything that improves on the oficial branch is lost in yours and there is no updates. Look at the Unity, as it looks right now future firmware updates will rely on someone working on the spare time when possible
You want to be sure that the new feature or changed code actually works. And you don’t want cluttered up source code. The best man on plant to review the code is Vedder. It is a complex software with many dependencies. A fuckup can easily send you flying.
As a developper, I don’t see the point to contribute to a project if the code I wrote will be re-write each time I push it. Fuck that (I understood why Ben does think it is a good idea but I do not agree). Big solo projects don’t hold in time.
Could we just scrap 90% of this convo and focus on using it as a actual thread for this repository and fork the annoying slap fight into another thread please. This is getting old fast.
I mean to say I’d like so see more individual pursuits being made.
It would obviously be best as a community to support and improve one project, not many. But this development then gets pressed back under the name of BV and the licensing of one company. I don’t see that being necessarily good for the community. That sounds like a compliant monopoly.