![]() ![]() There are also features that can request large amount of time. Some contradictionary features, that are exclusive (you can either have this or that, but not both) may have core group voting, or eventually community voting.Īnd then we would need to expand and grow the core group. and if you fix them, you can also commit changes to the repo. And if you use it, you encounter bugs, so you can either report them, or fix them for yourself. My first priority would probably be to gather core team of developers thatĪnd eventually provide all the access and permissions to themĪnd in the core team, you are not obliged to work on Gideros, or fix specific bug, it is enough that you use Gideros. Not that I know everything how Gideros works, also I have couple of diagrams of internal stuff drawn for myself, but it is not the environment where I feel myself at home (I mean c++ and OpenGL), but from what I saw, some developers here on this same forum, dive in so fast and easy, and provided so much based on the closed source project, I can't imagine what they could do with open source.Ībout website, forum, docs, as I discussed with it all will stay. I really don't know how many times can spend on it, but I know I'm willing to and will do it. I guess my questions can be summed up like : what are the elements that can make us optimistic about this move and what else should users know? What do you think about the "leadership" after going open source? Due to other priorities that I totally understand, it seems that you can't commit to communicate more. A successful open source project needs (I think?) a leader that is present and communicates (like Ton Rosendaal). and that "someone" will have a lot of work. Small updates will be submitted but "someone" will have to review the updates, etc. Are there examples of small open source projects that could grow well *without* a core team of dedicated developers that contributed to at least 80% of the updates? For now, the core team being focused on new priorities and the community of dev who could contribute not being organized, it feels like there won't be major updates. What are the other parts of the business that will be affected? (doc, site, blog, email support, etc)? If it's unsustainable, that means for you it can't be a priority anymore because you have to pay the bills (indeed we wish we could have supported the dev more) and you refocus your efforts = dev from the core Gideros team will be even slower. ![]() I'm not familiar with open source (most of the projects -Blender is an exception- that I knew and went open source died slowly) so I'm wondering : We had some discussion about it in the past. Hi very sorry to hear that this business model was unsustainable, because the product is good. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |