Of course, there should be one B4x GitHub account and each Community-Library should be in a separate Repository.
This would give great benefits, I just explain 3 of them:
- B4x Customers don't have to google for great Libraries, they just find them
- Erel is relieved (strange word, he will have fewer burdens)
because he can delegate the tasks to Contributors who likes to take this role for a repository.
They can do the small tasks and for important Community-Libraries, Erel can keep the Master role to finally release new commitments after they were merged and tested.
This is much better than the current "solution" using a forum,
because Erel probably / usually does not fix and release community-libraries.
But community-libraries are the most powerful benefit in B4x, because the official Libraries are missing a lot of basic functions. Therefore, the community power should be directed into powerful tools.
- Everything is handled in well-defined processes:
- Issues are individually handled and for each issue, the state is clear.
In a forum, Users have to search all the posts to find related pieces of information.
- This makes it very easy to identify open tasks and contributors can... easily contribute.
- If a contributor is missing some documentation, he can just add it to the right file - and everyone can benefit
I can just talk about our experience using B4x:
we used it to develop a small App and we decided to switch to Java / Eclipse for new small projects
because the B4x is great to get started, but immediately get annoying if a little more complexity or usability is needed.
For example, we have spent hours to just find the right Forum Posts so that we can send 'big' sms and our code uses a lot of JavaObject and Reflection code. Often, such code would be great to pack into a community library.
The problem is, that we can't contribute in a fast and well-tested way like GitGub offers.
Therefore, we must build our own B4x Libraries and so it's hard to benefit from the community and there is no way to contribute to the community because the price to handle it in a forum would be higher by factors than if we use GitHub.
Of course, we could start our own B4x GitHub repository.
But that should be against the interest of B4x, because customers should find great libraries in one portal.
Therefore, B4x should invite contributors to move their Code into something like a central GitHub repository.
Kind regards,
Thomas