The library has no readme yet - sadly. I aim to write one as soon as possible. Since I want a useful readme, it is likely to be written after V1.0 is "released". This project is very small scale and tries to accomplish a single goal at this time.
However my use case is very limited - export from Jira (clockwork app) to Odoo timesheets - I do wish to extend the functionality to many more applications, or at least set up a framework that makes writing an export portal to a certain service easy. At the time of writing this, it is unsure whether this will be done through mainly pull requests and additional development in this library, or extendability of the project. Both of which have advantages and drawbacks.
As it stands, I have chosen a mix between both; naming this repo with a neutral -sync-timesheet postfix. Yet, I have included a third-party portal (odoo9). Either of which may change, based on findings of the 'analysis' below.
Advantages and drawbacks
Development in this repo
Drawbacks:
testability - I would need access to the third party export targets to make sure portals work
scale - more export portals means more deprecation / maintenance (I am also not sure how many export portals there could be)
Advantages:
sharing - as this software is open source, this approach would mean the portals can be reused (assuming third-party-app version support is built-in)
Extendable portals
Drawbacks:
duplication - obviously people would have to write export methods themselves, duplicating work in the process
Narrative
The library has no readme yet - sadly. I aim to write one as soon as possible. Since I want a useful readme, it is likely to be written after V1.0 is "released". This project is very small scale and tries to accomplish a single goal at this time.
However my use case is very limited - export from Jira (clockwork app) to Odoo timesheets - I do wish to extend the functionality to many more applications, or at least set up a framework that makes writing an export portal to a certain service easy. At the time of writing this, it is unsure whether this will be done through mainly pull requests and additional development in this library, or extendability of the project. Both of which have advantages and drawbacks.
As it stands, I have chosen a mix between both; naming this repo with a neutral
-sync-timesheetpostfix. Yet, I have included a third-party portal (odoo9). Either of which may change, based on findings of the 'analysis' below.Advantages and drawbacks
Development in this repo
Drawbacks:
Advantages:
Extendable portals
Drawbacks:
Advantages: