Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
remove all sources and update README #832
This PR removes all sources and updates the README to state that three20 is not maintained anymore.
It seems there are still new iOS developers that pick up three20 from somewhat old blog posts or tutorials and then ask questions about it on stackoverflow. By removing all sources and updating the readme it should become clear that three20 is at the end of its lifetime.
I'd propose to merge this PR into development-branch, after that merge the new development branch into master.
What do you think?
I suggest deleting the development branch completely, and add a huge note on the master's README file saying "three20 is no longer maintained" (but keep the entire README content as is). if you have access to the repo's admin, it also would be nice to remove the issues tab, so developers won't be able to open issues.
a warning on the README should be enough in my opinion. i don't see a reason to delete the entire source code from the master branch. it doesn't hurt anyone as long as the warning is big enough.
Thanks for the feedback.
I'm not sure a warning in the README is enough, people seem to miss warnings from time to time, and ofc it can be easily missed by updating only a submodule. Having no source anymore should be quite clear :-)
It might be a good idea to make the issues read-only, but I'm not sure this is possible. It also doesn't hurt that much, at least if no one is spammed by the mails :-)
Regarding development branch, I guess you're right. If people still need to fix stuff, they can do it in their own clones.
+1. As much as it makes me sad to see it go this seems like the most appropriate option so people don't continue to use non-maintained code.
I am for deleting the source code on the main branch in GH (master, currently) so that it's very obvious that it's no longer maintained. Here is what I would do:
One other nice thing would be to let people know alternatives to Three20 (Nimbus and AFNetworking come to mind) that have been kept up.
@phillipuniverse Thanks for the input.
What we basically want to achieve is that everyone gets three20 isn't maintained anymore. This should be clear when
I've updated the README.md to point to Nimbus (and to the migration guide), as well as how to get back to the version before we removed all sources.