Thats a good point, where the board has not agreed to a solution so far.
My personal opinion is that we should find a solution for the “sandbox”. This sharing of “hey lookt at this code, it may help you” is also an important part, but we see at the other hand that there are quality expections to such project, which are not aligned with the quality of the contributed code.
I get earlier this year a mail about a project which didn’t work with a certain version of Domino/Notes and the expectation was that this has to be fixed. And this will not happen for this praticular project, because the project owner is not anymore in that business.
So our new approach in handling project should lead to less but better supported project and maybe also a clear place where “SandBox Projects” can rest and inspire developers or act as starting point.
@Patrick: Would this be a good solution for your concens?
I was at your session, and I can understand the new approach. But I can also see the point of view of Patrick about the sandbox function. I think it when you put your new sandbox project in GIT repository, so it easier to contribute to that project and add new functions or even better fix certain bugs.
I think it is great you facilitate the ability to work with projects in a more mature approach. I have no answer on the Sandbox question but I think it has always been an attractive part of OpenNTF. Those expectations you mention I have also experienced with my OpenNTF projects “can you fix this”, “can you change that”. I hope you have a standard reply snippet in your mailbox in which you state the project owners are solely responsible for the code.
Patrick Kwinten
October 30, 2015 at 9:57 am
Looks like OpenNTF will loose it “Sandbox” feature where developers “drop” their projects for others to do with it whatever you please?
guedebyte
October 30, 2015 at 10:41 am
Thats a good point, where the board has not agreed to a solution so far.
My personal opinion is that we should find a solution for the “sandbox”. This sharing of “hey lookt at this code, it may help you” is also an important part, but we see at the other hand that there are quality expections to such project, which are not aligned with the quality of the contributed code.
I get earlier this year a mail about a project which didn’t work with a certain version of Domino/Notes and the expectation was that this has to be fixed. And this will not happen for this praticular project, because the project owner is not anymore in that business.
So our new approach in handling project should lead to less but better supported project and maybe also a clear place where “SandBox Projects” can rest and inspire developers or act as starting point.
@Patrick: Would this be a good solution for your concens?
flinden68
October 30, 2015 at 10:50 am
I was at your session, and I can understand the new approach. But I can also see the point of view of Patrick about the sandbox function. I think it when you put your new sandbox project in GIT repository, so it easier to contribute to that project and add new functions or even better fix certain bugs.
Patrick Kwinten
October 30, 2015 at 11:23 am
I think it is great you facilitate the ability to work with projects in a more mature approach. I have no answer on the Sandbox question but I think it has always been an attractive part of OpenNTF. Those expectations you mention I have also experienced with my OpenNTF projects “can you fix this”, “can you change that”. I hope you have a standard reply snippet in your mailbox in which you state the project owners are solely responsible for the code.