Quote from: trainasauruswrecks on February 23, 2018, 03:12:48 PM

I don't know if it has been brought up here, but jbg suggested that perhaps the team form a "council" and we can apply the wallet donations to a multi-sig wallet controlled by the council. We are the process of forming this Council at the moment. That way a few of the community members will be in control of the funds and their release to him. He proposed that if we are not content with the work that he is doing then we could opt to dismiss him and use the funds to hire a new developer. The team will keep you updated on this and any other advancements that we make in the process of alleviating the existing uncertainty. Again, thank you for your concern. You've provided the less tech savvy of us with a necessary direction in this area.

Glad I could help to shed some light.

But, again always in my opinion, I don't think this is a problem of being content of jbg work or not, this is about if he is lying to the whole community or not. And in order to check this the actions are very simple:

1- Ask him to put 1.4 code public (promised but not done in almost a month),
2- If you are forming a council, ask him to show 2.0 code to the council, so you can actually see Bryce work.

Bear in mind that commit history can be manipulated, so I would pay attention if he is buying time, like he is doing with 1.4.

1 could clear some doubts (if the work done matches June/February commit gaps), 2 will clear most of them (if there are commmits from Bryce in the period Sept/Feb justify another developer working full time), as long as the council is not colluded and can evaluate the work done.