Further consolidation of forks?

[tax]

Hi @michiya and @dlo

Right now I use django-mssql which works excellent, but only on windows. I would really like to run on a linux server so I am now investigating the use of ODBC. I really appreciate all the work that has been done and that you guys are still doing.

It took me quite some time to find if and where the ODBC backend was maintained.
I found:
http://code.google.com/p/django-pyodbc/ (last commit about 3 years ago)
then:
https://github.com/avidal/django-pyodbc @avidal fork.
then:
https://github.com/aurorasoftware/django-pyodbc/ @aurorasoftware version which has @avidal improvements merged when issue #3 was closed.
and:
https://github.com/michiya/django-pyodbc-azure actively maintained by @michiya and with azure support.

Maybe you guys allready knew about each others fork and have your own reasons to have different forks. If not it could be an idea to consolidate the code and all future improvements to one repo. If there is anything I can do to help this process: testing or any other task please let me know.

Again thanks for sharing your work,

Paul

[avidal]

@tax As you saw in #3, I opened up the discussion with @aurorasoftware about merging in the fixes I have in my branch. At the time, all they had done was project structure/doc cleanups (which are certainly important!) and a couple of fixes. My changes allowed it to work against Django 1.4, and as far as I know the version at @aurorasoftware now works on Django 1.5.

I have every intention of updating my fork to point to this one as soon as I get the green light from these guys; and I think it'd be excellent for them to consolidate with the Azure fork.

Like I mentioned in #3, there are also some outstanding bugs/pull requests on my fork that will hopefully be addressed. I think that soon enough it'll stabilize to a point where everyone can be directed to this fork as the primary development source.

[tax]

Thanks @avidal, I think everybody will benefit from one primary development source.
@dlo and @michiya what do you guys think?

[dlo]

@tax totally agree. It looks like Azure support is a huge plus--I can go through @michiya's repo and see what needs to be changed for it to happen on this fork's end.

@avidal Right now, we're using this version in production, and it seems that with the other updates, it should be pretty close to stable. I've already incorporated all (I think?) of the updates in the pull requests on your version, though I will double check.

[avidal]

@dlo Sounds good. I'll update my repository to point here. Thanks for the hard work.

[michiya]

Hi guys,

I appreciate your letting me know about this. It's a good idea to consolidate Azure support into this repo, everyone will benefit from it. What can I do for you?

[dlo]

Hey @michiya! Thanks for joining in :)

Since I currently don't have any currently running projects on Azure, it probably makes sense for you to have a commit bit here and merge in your changes to try it out. Does that work?

[michiya]

@dlo Okay, from now I will go through this repo to see what changes should be done to support Azure and make those changes step by step on the repo. After the consolidation is made I will remove my package from PyPI for people not to confuse which package should they use.

[dlo]

@michiya awesome, thanks! let me know if you want any help on my end. I'll close this issue and add another one regarding the Azure support.