this project could use a new maintainer
jamesturk opened this issue · comments
I haven't used django-markupfield in 3-4 years, though I continue to make minor bugfixes/etc. If someone else is using it and would like to take ownership I'd happily transfer ownership over to you if you get in touch and explain what you'd like to do/how you use django-markupfield.
particularly if you're interested in a rewrite to support Django 1.7
Well, I can try to rewrite it for Django 1.7 but I may need a little help (at least somebody who checks my grammar - english isn't my first language as you may already have noticed) and I won't be able to maintain it since a lot will be going in school on next year.
But I hope the project won't need much maintaining. I might able to push some bugfixes but I can't guarantee it right after they have been discovered, because school is more important to me.
I will have time for the rewrite because I'm having summer vacation in 3 days. In case, django 1.7 is released before I finish my rewrite (which is very likely), I suggest that we push my nasty regex fix that checks if the class is created by Migration.
I'd be happy to merge a rewrite for 1.7 if you come up with one!