Separate taxi from Zebra and allow to have multiple backends

[jeanmonod]

If we completely separate taxi from the zebra backend, this will have major benefits:

• It will make taxi a real opensource project, useful outside Liip
• Taxi will be able to push entries to public backend such as Harvest, 10000ft or even a basic spreadsheet. This should boost the community support
• Personably I will be able to timesheet my personal project with my favorite timesheet tool... ;)

So in my idea, each aliases could be bound to a specific backend, and then when I do a taxi ci, the entries will be pushed to appropriate location.

What do you think about that? This goes in the same spirit as #24, #29 but one step ahead...

[sephii]

That would be very cool indeed.

I guess we can assume all backends won't use the same interface, so we could create "connectors" as separate plugins that would be developed outside of taxi and then would be bound to aliases in the configuration file.

The big thing I can see now is the configuration file. The more I use it, the more I think the ini configuration syntax is too limited (the most flagrant thing being that there are no subsections). I'm thinking of using a Python file but that would mean we can't change it dynamically anymore (eg. to add new aliases) so we'd need to change that as well.

So basically we'd need to:

• create a plugin architecture (this goes farther than just the commit command. Think about the update and the shared aliases for example)
• take the current Zebra connector out of Taxi
• change the configuration mechanism to allow configuration of specific backends

[sephii]

The feature is done and has been merged in dev. The zebra backend has been put here: https://github.com/sephii/taxi-zebra.

[jeanmonod]

I would suggest to move the taxi-zebra under liip (private repo), or even
under gitlab/liip. What do you think?

On Mon, Feb 16, 2015 at 9:32 AM, Sylvain Fankhauser <
notifications@github.com> wrote:

The feature is done and has been merged in dev. The zebra backend has been
put here: https://github.com/sephii/taxi-zebra.

—
Reply to this email directly or view it on GitHub
#40 (comment).

David Jeanmonod
david.jeanmonod@gmail.com
077 437 51 12

[sephii]

Zebra being open source I'm not sure it would make sense to have this in a private repo. Also, not releasing taxi-zebra publicly would mean not being able to simply install it with pip install taxi-zebra.

[jeanmonod]

Zebra open source??

On Mon, Feb 16, 2015 at 11:27 AM, Sylvain Fankhauser <
notifications@github.com> wrote:

Zebra being open source I'm not sure it would make sense to have this in a
private repo. Also, not releasing taxi-zebra publicly would mean not being
able to simply install it with pip install taxi-zebra.

—
Reply to this email directly or view it on GitHub
#40 (comment).

David Jeanmonod
david.jeanmonod@gmail.com
077 437 51 12

[sephii]

Let's put taxi-zebra on Pypi, so that users can easily install it with pip, and host it on github as a read-only mirror of an internal repository that will be used for bug reporting.

Anyway, this feature has been implemented in a6fc5a7 and has been merged in dev.