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

@dylan => Folio overview #119

Merged
merged 4 commits into from Aug 6, 2015

Conversation

Projects
None yet
2 participants
@orta
Member

orta commented Aug 6, 2015

No description provided.

Show outdated Hide outdated source/_posts/2015-08-06-open-sourcing-energy.markdown
The Artsy Mobile team is pretty agressive in our stance on [Open Source by Default](http://code.dblock.org/2015/02/09/becoming-open-source-by-default.html). We've talked about it at [conferences](https://www.youtube.com/watch?v=2DvDeEZ0NDw&spfreload=10) [around](https://www.youtube.com/watch?v=SjjvnrqDjpM) [the](https://www.youtube.com/watch?v=zPbLYWmLPow) [world](https://speakerdeck.com/orta/ios-at-artsy), in [renowned magazines](www.objc.io/issues/22-scale/artsy) and on [our blog](http://artsy.github.io/blog/2015/04/28/how-we-open-sourced-eigen/).
It's worth mentioning that we don't just talk externally about Open Source. Internally the entire development team runs talks, explains how GitHub works and what the implications of all our work in the open are. We strive for an open culture in more than just the development team. The development team is just further along in the process.

This comment has been minimized.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

I gather who the "we" is here could be somewhat more explicit.

The second sentence is a bit wordy. Maybe something like "Internally, the Artsy Mobile team organizes talks about Open Source for the rest of the Artsy staff. As well, we discuss the tooling and business implications of having our work in public repos." ... maybe.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

I gather who the "we" is here could be somewhat more explicit.

The second sentence is a bit wordy. Maybe something like "Internally, the Artsy Mobile team organizes talks about Open Source for the rest of the Artsy staff. As well, we discuss the tooling and business implications of having our work in public repos." ... maybe.

Energy is commonly known as [Artsy Folio](http://folio.artsy.net). It's a tool for Artsy's Partners to showcase their artworks on the go, and quickly email them. Here's a beautiful splash showing it in action.
{% expanded_img http://folio.artsy.net/images/cover-bbf6fdf4.jpg Folio overview %}

This comment has been minimized.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

Eager contributors may note that Energy on iPhone doesn't support the landscape rotation...

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

Eager contributors may note that Energy on iPhone doesn't support the landscape rotation...

Eigen, the public facing iOS app, allows people to log in with a trial user account. We also have a known API Key + Secret for the [OSS app](https://github.com/artsy/eigen/blob/master/Makefile#L41-L42). With this, any developer can run a few commands and have a working application to play around in. This makes it easy to look around and see how things are done.
Energy, however, requires you have a Artsy partner account. So opening it up would mean that an OSS developer hits the login screen and is stuck. In developing this app, I've slowly been creating my own partner gallery account based on my paintings and photography. So now when you set up the app to be ran as an OSS app, it will pre-load a known database of artworks and metadata from my test gallery.

This comment has been minimized.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

Surprising turn!

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

Surprising turn!

Show outdated Hide outdated source/_posts/2015-08-06-open-sourcing-energy.markdown
Its easy to imagine that open sourcing something is an end-point, but from our perspective it is a journey. We want to make sure that anyone can download this app, learn how and why it's structured and then run through the app with a debugger to get a deeper sense of how everything connects. Just releasing the code would have been underwhelming. Instead we're aiming high.
I think that there is no higher compliment to your team, and your code than opening it to the public.

This comment has been minimized.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

I don't reckon you need that there comma.

@dylanfareed

dylanfareed Aug 6, 2015

Contributor

I don't reckon you need that there comma.

dylanfareed added a commit that referenced this pull request Aug 6, 2015

@dylanfareed dylanfareed merged commit 727d36b into source Aug 6, 2015

@orta orta deleted the folio branch Aug 7, 2015

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