You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "stf_ios_support" project and it's associated pieces were unmaintained for around 3 years. As a result the code has been rotting and many new methods and ideas have been invented since it was last working properly.
As the original author of it, I have stepped in to maintain it once more, and will happily work with and allow people to contribute and make it usable once more.
I will be:
Going through all the open issues and updating them as possible
Going through the existing PRs and getting the changes within them integrated
Myself re-testing the whole setting and making new maintenance changes to make things function again
The repos themselves are going to be in the dryark namespace. For this moment they are in my personal namespace, but I will move them there soon. While they will be away from the DeviceFarmer namespace, the goal of this is not to kill over working with DeviceFarmer, but rather the opposite. I am taking on the effort of acting as maintainer, and moving the bits to a namespace I control to make it clear who is in control of this particular effort and who people should go to to get things integrated or have their questions answered.
Where reasonable, if issues are with upstream DF / STF, I will direct users there.
The text was updated successfully, but these errors were encountered:
The "stf_ios_support" project and it's associated pieces were unmaintained for around 3 years. As a result the code has been rotting and many new methods and ideas have been invented since it was last working properly.
As the original author of it, I have stepped in to maintain it once more, and will happily work with and allow people to contribute and make it usable once more.
I will be:
The repos themselves are going to be in the dryark namespace. For this moment they are in my personal namespace, but I will move them there soon. While they will be away from the DeviceFarmer namespace, the goal of this is not to kill over working with DeviceFarmer, but rather the opposite. I am taking on the effort of acting as maintainer, and moving the bits to a namespace I control to make it clear who is in control of this particular effort and who people should go to to get things integrated or have their questions answered.
Where reasonable, if issues are with upstream DF / STF, I will direct users there.
The text was updated successfully, but these errors were encountered: