@ALL
@GeorgeFive
I am thinking about this question for a long time and want to know what your, the users, view is on this question?
There was a user at imdbphp that i offered to use my version but he couldn't use it because differences (mainly in PSR version) so that got me thinking about this.
At the time i decided that my library would not be a fork and that it would become a very stripped version of the original.
This thought changed over time, it did become a full blown version and it is almost a full fork of the original.
So the question is should my project be a one on one fork of imdbphp or not?
There are a few differences:
some method names differ
some method output is different (mostly due to extra functions/data)
additional methods that are not in imdbphp
additional classes that are not in imdbphp
Please share your thoughts about this!
@ALL
@GeorgeFive
I am thinking about this question for a long time and want to know what your, the users, view is on this question?
There was a user at imdbphp that i offered to use my version but he couldn't use it because differences (mainly in PSR version) so that got me thinking about this.
At the time i decided that my library would not be a fork and that it would become a very stripped version of the original.
This thought changed over time, it did become a full blown version and it is almost a full fork of the original.
So the question is should my project be a one on one fork of imdbphp or not?
There are a few differences:
some method names differ
some method output is different (mostly due to extra functions/data)
additional methods that are not in imdbphp
additional classes that are not in imdbphp
Please share your thoughts about this!