Time for semi-official fork?
0x2206 opened this issue · 6 comments
It looks this awesome project is not maintained anymore and as world moves on I guess it would be beneficial to all of us to deal with opened issues and pull requests. Last thing I want to do is to create another fork, take other's work and credit it to myself. That is why I propose to focus on one of already created forks and treat it as a successor. Alternatively, @dillidon could designate a new maintainer of this repository.
I am mentioning you, former contributors, as you are probably the best candidates:
@JoeSzymanski
@ss18
@loicgriffie
@jason-ingenuity
@basvankuijck
@kobeumut
@jahid-hasan-polash
@daemedeor
@dongdongpc
@theyongdai
What do you think?
When looking at the repository historic, small chances that @dillidon add maintainers or even take into account this. I agree with a fork to continue support this library with multiple maintainers to avoid the same
Excellent! Third option is to create organisation account on GitHub and cover fork under it. Let's wait couple of days more for other contributors input and then we move on with the fork.
🎉 Congrats
🚀 RLBAlertsPickers (1.1) successfully published
📅 November 9th, 16:31
🌎 https://cocoapods.org/pods/RLBAlertsPickers
👍 Tell your friends!
- Swift 4.2
- Fix warnings + deprecated
- TelegramPicker (thx @chingiz888)
Preferably, keeping this project away from cocoapods, it contains too much pixie dust. IMHO, the official/semi-official fork should capture the essence of the original project.
It's just another XCode project. Anyone can feel free to fork and add any fancy they want, cocoapods, swift package manager or <insert_fancy_manager_2_0>.
Hi guys! The birth of a child did not allow me to further develop the project! There are difficulties of its development in using the 'UIAlertController'', instead of which I would like to use a simplified version of SwiftEntryKit, that I use now in my current project.