Hey, I’m posting this on behalf of @gallux because he is experiencing server erros whenever he tries to post to discourse. The following are his views:
I want to share my thoughts to question “base b2g on Android”.
- Philosophical Matters
We are on a special moment on the community. What we are thinking about the community goals now, would mark our future and the future of our efforts.
For that reason, what we think is important, for us and the people who want to join us.
What do we want?
This is main goal of our efforts. It appears that we want to maintain a mobile system which complains with open web standars and the freedom of its users. “Power to the user” would be a good motto in this sense.
But, there is a point. We are heirs right now. We recieve a history, ideals, a fighting which deserves our efforts, a way of thinking that we like.
Was Mozilla doing it right?
I guess that the answer is affirmative, at least, speaking on operative-system design.
Does it deserve to be maintained?
Maintaining b2g is the only way to keep our ideals walking.
It’s so harder, as many of you said before, but:
we do not have to create a system from nothing: the whole OS exists, for example, we don’t need to create a own kernel, compilation tools, etc; that work is already done.
We do not use any of hardest engineering techniques, as example, reverse engineering to reach our mobile system, for example, the haiku-os community, who, after 15 long years, has not re-created BeOS system absolutely. Currently, haiku-os is still in alpha. By the contrary, we have the possibility to access to the all related code, and, we are able to modify it, if we want.
We need our independence with us. Depending on Android in a “hard way” means sealing our future with it. Being the most supported platform today, will not mean it tomorrow. (Andromeda).
- Technical Limitations
Well, if we decide to keep b2g with the most fidelity as we can, we need to realize which it is not a harder work. In fact, no software development is an easy work.
All critical developments involve great technical knowledge, great amounts of resources and time, good relationship among us and our supporters, a lot of things those needs to join in some point to success.
It appears Hard and difficult, but I remember you FLOSS projects that had least possibilities to be successful, but history has shown the contrary:
A simple student experiment became one of pieces of software most used on the world. (Kernel Linux)
GNU project has started with a open letter to society.
Libreoffice has only twelve people as members when it started.
*bsd projects maintained by a small community around themselves ( I remind you that *bsd’s projects maintain whole operative systems)
Thinking on our technical limitations --we can’t do this-- only cut our own growth in something more. I think the right approach is "we can’t do this, yet…
We need to use the word “how” and ideas will appear on our minds.
- Future Plans
If we can organize ourselves, we could talk with enterprises, foundations, other FLOSS organizations, to ask their help, or propose the project. A first place to start is the former b2g interested --Panasonic, Telefonica, Deutsche Telecom, Alcatel and so on- With asking we don’t lose anything, but we open to possibility to get something.
We cannot think in short-term. Maintain a whole OS is a huge work and a work speaking in long-term. We cannot think only in short range of time, no if we want a project which shall be self- financed. ( I don’t believe that Mozilla will lend its resources per secula seculorum).
Our first priority is backup the code related to b2g. Our second priority is plaining how we could maintain it. The third priority is getting resources, donations, contacts, making campaigns, and doing our own foundation and only if we reach all of them, bring b2g to the next stage of its evolution.
It is possible. Again, Projects with least possibilities were (are) successful in their time and yet, today. It depends on the way which we offer (and what makes us different) to the geek-tech people and, if any, potential partners.