4 ms·

I'm curious to see how the whole 'forking/cloning' concept is replicated here, especially if Pixelapse is seeking to become the Github for design. I'm fairly ce

I'm curious to see how the whole 'forking/cloning' concept is replicated here, especially if Pixelapse is seeking to become the Github for design. I'm fairly certain that the restrictions for use of graphic content in a public format is a lot more prohibitive as opposed to software (there's not really such a thing as 'open-source graphics' besides measly clip art galleries). The true social value of Github is in its community-oriented approach where any developer anywhere can fork code and contribute changes. That doesn't seem as possible with imagery, and my impression is that designers are more concerned with protecting their work (nothing wrong with that - just an observation).

nlh 14y ago
I didn't immediately see a "fork" option (am I missing it?) - but I hope they add that feature. I think this has a ton of cool potential. Open source design could be massive. There are already tons of places where designers give away assets to the community - fonts, PSD templates, logo templates, etc. But they all have the limitation of being done by a single designer. I think - despite the fears of "design by committee" that some might have - there could be some great stuff that comes out of collaborating in this way.
JangoSteve 14y ago
We recently started using Pixelapse (we're a development team that just welcomed our first full-time graphic designer a few months ago). It's pretty nice, but there is one huge difference between design and development that makes the idea of "Github for design" seem like the wrong idea. Developers really only need to share code with other developers. There's almost no such thing as a passive receiver of code. The ability to easily collaborate on code with other developers and within a team, via cloning, forking, pushing and pulling, makes Github (and Bitbucket and Gitlab, etc) immensely beneficial. Design interactions, on the other hand, tend to be made up primarily of designers sharing designs with non-designers, whether it be the client for feedback or the technical team for implementation (or the printers, or the marketing department). I think Pixelapse is more like the "Github for design" if you just think of Github as a 3rd-party repository for easy version tracking and uploading of code, and which makes it easy for others to comment and compare different versions of the code. In other words, minus the forking and cloning concept. At least, that's how we use it.

nlh 14y ago

I didn't immediately see a "fork" option (am I missing it?) - but I hope they add that feature. I think this has a ton of cool potential. Open source design could be massive. There are already tons of places where designers give away assets to the community - fonts, PSD templates, logo templates, etc. But they all have the limitation of being done by a single designer. I think - despite the fears of "design by committee" that some might have - there could be some great stuff that comes out of collaborating in this way.

JangoSteve 14y ago

We recently started using Pixelapse (we're a development team that just welcomed our first full-time graphic designer a few months ago). It's pretty nice, but there is one huge difference between design and development that makes the idea of "Github for design" seem like the wrong idea. Developers really only need to share code with other developers. There's almost no such thing as a passive receiver of code. The ability to easily collaborate on code with other developers and within a team, via cloning, forking, pushing and pulling, makes Github (and Bitbucket and Gitlab, etc) immensely beneficial. Design interactions, on the other hand, tend to be made up primarily of designers sharing designs with non-designers, whether it be the client for feedback or the technical team for implementation (or the printers, or the marketing department). I think Pixelapse is more like the "Github for design" if you just think of Github as a 3rd-party repository for easy version tracking and uploading of code, and which makes it easy for others to comment and compare different versions of the code. In other words, minus the forking and cloning concept. At least, that's how we use it.