Closed mnapoli closed 9 years ago
There were no bug reports in 2 years either. The "build" fails just because I shut down my private piwik instance it ran against. Everything works as expected on a server a client of me runs. Stable != unmaintained.
OK, understand that for everyone except you it's hard to have any idea if the project work at all (unless spending time to figure it out) which is why we asked in the first place. Additionally things in Piwik's API evolve (new features are added), stable for 2 years probably also means that those features are not available to users.
@nkuttler good to hear from you! just wanted to ask if you need a Piwik instance for the CI tests? if so we could use demo.piwik.org (i could create a new website there or something). let me know...
@mattab Thank you! But I don't think demo.piwik.org would work, as my tests parse some of the tracker debugging output, and I think that has to be enabled globally. I guess I should just install piwik itself inside the travis machines, that would remove any external requirements. I think I originally avoided that because running the tests already took enough time. I'll have a look at the core travis config.
Hi @nkuttler
I don't think demo.piwik.org would work, as my tests parse some of the tracker debugging output
@nkuttler Ok, i think we don't really need to test the Piwik API side of things from the Python SDK CI. The Tracking API is very well tested on our piwik/piwik repository on CI (hundreds of tests cover it). So you can assume that Piwik Tracking API will work fine given your request parameters. An idea: maybe instead you can test that the requests you send have correct payload?
The project is still maintained by @nkuttler - closing
Hello there!
In an effort to make it easier for users to understand which options are available to them we are considering marking this project as unmaintained/deprecated. The reason for this is that there are been no activity here for 2 years and we don't know if the project still work at all (the build fails), so we are afraid that users might want to use it but be left confused and without support if things do not work.
By explaining to users that this project is unmaintained, they can still try to use it but they would be at least aware of the situation.
Of course the project could be revived anytime if somebody wants to do it.
Is there anyone here that thinks this is a bad idea? Or anyone that would like to start maintaining this project again?