On Friday 22 November 2013 19.35:26 Richard Brown 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?
Kill gitorious, I've anyway a copy of it locally and online.
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 :))
Okay talking about drafts, they are draft, one coding rules is never commit something that is not tested.
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 would not be so negative, There's plethora of way to share a file online. And somewhat a big number of of us able to pick it, and commit to git. This happen less than one month ago, with the new one-click icon.
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)
Will really an owncloud instance help ? (Where is it hosted, Who manage it, Who can fix it (think upgrade update there's a lot with owncloud) Behind owncloud, we have to manage also its file versionning system. Who will be able to checkout the complete revision ? How will be managed the changelog about files ...
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
You get my points, If a demoing system prove its strength over github why not.
Of course, I think it should go without saying that I think -branding should stay as it is, where it is, in GitHub
For sure ! I would have preferred the approach of one git main, and several sub-systems linked to it. If you want to check out t-shirt then grab only t-shirt etc. (This idea was exposed at osc 2011)
In short
* Yes, delete gitorious/artwork unless someone else screams they're still using it
* Splitting further sounds like a great idea, It is, did we need help to create a nice split an organized repository. (Michal/Stephan could teach any of us to make it a reality) but I'd like to consider a more 'artist appropriate' tool like ownCloud first why not if it prove its efficiency ... * Whatever we decide to do for artwork, lets leave branding where it is.
kill bill true
Thoughts?
done :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org