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

Removal of Cooliris Integration #14

Closed
Chraneco opened this Issue Apr 22, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@Chraneco
Member

Chraneco commented Apr 22, 2015

Cooliris development has been discontinued by its maintainers and the public API is already not available anymore.

Thus, everything related to Cooliris will be removed from JoomGallery's code base.

It doesn't seem like many people used this feature lately anyway.
If you rely on some code of this or suggest a workaround please post here before the release of JoomGallery 3.3. Otherwise, Cooliris will be removed with that release.

@Chraneco Chraneco added this to the v3.3.0 milestone Apr 22, 2015

@JoshuaLewis

This comment has been minimized.

Show comment
Hide comment
@JoshuaLewis

JoshuaLewis May 21, 2015

I'm in favor of removing Cooliris. Yahoo acquired Cooliris, but isn't doing anything with it.

JoshuaLewis commented May 21, 2015

I'm in favor of removing Cooliris. Yahoo acquired Cooliris, but isn't doing anything with it.

@Erftralle

This comment has been minimized.

Show comment
Hide comment
@Erftralle

Erftralle Jun 6, 2015

Contributor

👍
I created pull request #28 to remove Cooliris.

Contributor

Erftralle commented Jun 6, 2015

👍
I created pull request #28 to remove Cooliris.

@Erftralle

This comment has been minimized.

Show comment
Hide comment
@Erftralle

Erftralle Mar 31, 2016

Contributor

Since we have a merged pull request for this issue we could close here, right?

Contributor

Erftralle commented Mar 31, 2016

Since we have a merged pull request for this issue we could close here, right?

@Chraneco

This comment has been minimized.

Show comment
Hide comment
@Chraneco

Chraneco Apr 1, 2016

Member

GitHub should automatically close this issue once the 3.3 branch is merged into master. I'd like to test that feature.

Member

Chraneco commented Apr 1, 2016

GitHub should automatically close this issue once the 3.3 branch is merged into master. I'd like to test that feature.

@Chraneco Chraneco closed this in 19f4b0d May 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment