This is an brave and incredible initiative. Can OS design work?
I think so; hopefully I can make a good case for it.
Anyone else find it funny that the Open Source Design group is using two paid services (that aren't open source) to share the progress?
I guess that's why the group exists, to fix things like this, but semi-lol.
We're using a free LayerVault account though, which works just like a free GitHub project.
The one downside right now though is there isn't a way for people to publicly comment on LayerVault without being invited to the project. Adobe CC allows for public comments without a paid account.
We haven't found the perfect solution yet, but we're hoping things will change for the better.
We're also using GitHub Issues. https://github.com/opensourcedesignis/opensourcedesignis.github.io/issues/33
"The one downside right now though is there isn't a way for people to publicly comment on LayerVault without being invited to the project."
Missing this feature a lot - hopefully the guys from LayerVault are working on a solution. I'd love to see the possibility to let people who aren't explicitly invited to the project comment on it.
Isn't "designing in the open" what we've all been doing on Dribbble for years?
Ideally yes, but we seem to be afraid to let people see our work until it is done, and I wouldn't say that the Dribbble community does the best job of giving good feedback/collaborating. Nothing against Dribbble - it has the potential to make that happen, but I don't think we've really embraced that.
Good point. It's true Dribbble has changed over the years. And I suspect the more exposure a designer gets, the less they feel like showing their crappy first iterations to the world…
True and I think there are benefits to letting people not see our process and crappy iterations.
What benefit is there in not showing process?
Fear of rejection or ridicule. That and it can take work to get your process out there.
I'd like to refer back to this as an interesting example of sharing the process https://news.layervault.com/stories/7146-instapaper-redesign-iterations
That's a strange example...it seems like they were designing in the browser, and in order to share on Layervault they had to put screenshots in PS. Github needs a quick way to see iterations created in the browser.
GitHub pages works great for iterating in the browser, or even Codepen.io
Maybe GitHub pages, but there's not a quick way to move from iteration to iteration out of the box.
I have a hard time imagine iterating any thing more than components in Codepen.
We're using Codepen to iterate on the colors we use on Topcoat, before moving it to code.
Our designer forked the pen, and is working on the separately.
Yeowza, that's intense. Hadn't considered Codepen beyond snippets of things.