The idea of splitting the gitorious repo is good IMHO. In many cases people just don't have the bandwidth to download the whole repo only to change a couple of lines. If it is more modular, then it is easier to manage and lighter to download. In fact, only distribution related artwork should be housed at gitorious. Other artwork has been going to github as set up by Jos. I also really like the idea of having an owncloud instance for our team. As Richard points out, we don't always produce artwork related to the distribution and we end up making a lot of drafts, proposals and other artwork that requires refinement. For that end, having an owncloud would be easier to manage, especially for new users who might be used to services like Dropbox to share their content. At the same time, having this instance would have to be a "per user" folder and then a folder where final artwork is pushed to. I have no idea how to do this so I welcome any suggestions on how to make an owncloud managing diagram. I proposed the cloud idea to Jos some time ago and if anyone can make it a reality, let's go for it! As far as what we could do for distro artwork for the next release, I intend to propose ideas on the ML later this week. We can check in what position we all are to make these changes or add new ones. :D Thanks guys! Andy (anditosan) On Fri, Nov 22, 2013 at 11:35 AM, Richard Brown <RBrownCCB@opensuse.org> wrote:
On 22 November 2013 19:16, Stephan Kulow <coolo@suse.de> wrote:
Am 22.11.2013 18:34, schrieb Michal Hrusecky:
Hi,
I'm trying to convince people to put all our git repos in one place (move people who are still on gitorious to github) and I run accross art repository[1]. Is there still something valuable/needed or is everything moved already to github?
In the later case, I would like to propose to delete this repository...
Apart from that I noticed that artwork repo is quite huge... Have you ever thought about splitting it? We can split it into submodules and put some simple usage script in so you could still clone everything but you could also clone only parts of it and save some space. All that while keeping history.
What do you think about that?
I already moved branding out of it for that reason.
Greetings, Stephan
Hmm, splitting isn't a half bad idea.
My personal opinion is that GitHub isn't the best tool for many of our artists contributing to openSUSE, especially when we often need to share drafts (like we're going to need to do for the next release, which I think is gonna need a nice art refresh :))
GitHub's preference for 'small(er)' file sizes can be quite a hindrance, plus git doesn't necessarily come naturally to those contributors who don't also commit code
I've looked around for a solution, and I'd like to trial using an ownCloud instance - I think it will do the job quite nicely, and the combination of both a 'sync' client, 'live access' clients (any WebDAV client) and the web interface should make it possible for see and contribute stuff to what is currently in the GitHub artwork repo (where features like code review aren't needed)
What does everyone think about this? If its popular with the team, I'll pull a finger out and speak to someone from the infrastructure team about the viability
Of course, I think it should go without saying that I think -branding should stay as it is, where it is, in GitHub
In short
* Yes, delete gitorious/artwork unless someone else screams they're still using it * Splitting further sounds like a great idea, but I'd like to consider a more 'artist appropriate' tool like ownCloud first * Whatever we decide to do for artwork, lets leave branding where it is.
Thoughts? -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
-- Andy (anditosan) -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org