The new CocoaDev.com un-wiki. The ultimate solution to the wikispam that's plagued the CocoaDev wiki for years. Edit the Markdown content and submit a pull request. Encourages quality content while maintaining wiki-like history and editing.
There's really no need to burden the wiki with personal and company pages. I myself am guilty of this (since the early 2000s) but I think it would greatly reduce clutter and set a standard.
Of course, as the host and curator, I reserve the right to create a static page about me... ME... MEEEEE!!!!! ;-)
It seems that the code for zlibInflate/zlibDeflate is originally from you and was published on cocoadev.com - is this correct?
We are also using this code and I am trying to comply with FOSS guidelines.
Have you published this code under a specific license?
We should create a "scripts" folder so contributors can share their scripted work on the CocoaDev content. Helpful scripts include link cleanup, content validation, spam link blacklist removal (though this shouldn't really be a problem any more), etc.
Some volunteer time could be spent locating and removing all pages that needlessly duplicate Apple documentation pages. This would reduce clutter and eliminate the need to maintain something Apple themselves maintain. A link to the documentation is work enough (since they regularly restructure and break links without proper forwarding).
Hi @jnozzi โ while I appreciate the efforts you've put into rebuilding CocoaDev, there's a lot of conversion problems in the Markdown and I'd really like to reference some of the materials in a non-broken manner.
Would it be possible to get a copy of the original CocoaDev.com as it was before you took over? Thanks!