-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project status and relation to ezdof2 #25
Comments
Yep, I am aware of that. This project newer than ezodf2. However, I started my fork and is about to make a new release(under pyexcel-ezodf) since ezodf 0.3.2. Please read this note too: pyexcel#2 |
Ah complex relations. It would be nice if this could be described in details in all three (or more) related projects. Do I understand you right? |
I have mentioned recent move in https://github.com/pyexcel/pyexcel-ezodf#maintenance. And I am trying to refresh the library in pypi using package name pyexcel-ezodf but it won't have any impact on programming level. Still you do 'import ezodf'. |
I think I plan to Does T0ha told he just make "holiday" and will come back? From my point of view it would have been nice if he would let you join his project/repository and you work with that. I would appreciate if you booth would re-join your repositories. |
I agree that it will be nice I would join. However, I got to roll out the fix for alphagov/notifications-admin#1426. I don't think I would wait for another year. However, I could always upstream my changes in pyexcel-ezodf as long as someone click accept the PR. |
I see your point. What I meant was that t0ha should give you admin rights to his project. Than you can merge the PR yourself. ;) I think this is no big deal. |
Hi. Do you know about this?
https://github.com/iwschris/ezodf2
The last commit there was 2013. But the README says that it is derived from "ezdof".
But your last commit is much more fresh. ;)
So can you give some more infos about it? I would assume that your "ezdof" is newer and more stable then "ezdof2"?
The text was updated successfully, but these errors were encountered: