Bug 5213 - Require server space for marcom and artwork teams to store work
Summary: Require server space for marcom and artwork teams to store work
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
Keywords: Atelier
Depends on:
Blocks: 5229
  Show dependency treegraph
Reported: 2012-04-03 14:00 CEST by Patricia Fraser
Modified: 2015-01-26 12:34 CET (History)
11 users (show)

See Also:
Source RPM:
Status comment:


Description Patricia Fraser 2012-04-03 14:00:31 CEST
Both Marcom and Artwork require space on Mageia servers for storing artwork and marketing texts.

Artwork team will add detail about what they need.

Marcom is currently squashed onto the Wiki, and we need space to put work in progress, that we can then move into a public area like the wiki when it's ready for comment or completed.

This request has been hanging for quite a while now, and it's urgent.
Romain d'Alverny 2012-04-03 14:11:47 CEST

CC: (none) => rdalverny

Patricia Fraser 2012-04-03 14:50:49 CEST

CC: (none) => mageia-artwork

Comment 1 Max 2012-04-03 17:41:30 CEST
Ideally we'd like two levels:
1. To have a user-facing gallery that anybody can browse and download artwork from. This should be indexed, searchable and sorted intuitively.
2. To have a "private" database where artwork team members can work. In an ideal world each artwork piece will have a detailed history attached to it as well as a discussion thread, a place for comments. Only Artwork people should be allowed to upload to this database. In theory anybody could just browse and download artwork from there, but we won't be making the links public, however they will show up in meetings, mail archives and whatnot.
Transferring artwork from one level to the other should be simple and fast. And images that appear in the gallery should be "frozen". i.e. no changes can be made to that image by Artwork people, but forks are allowed.
If I think of anything else I'll add it.

CC: (none) => bogusman222

Marja Van Waes 2012-04-04 11:38:03 CEST

Blocks: (none) => 5229

Romain d'Alverny 2012-07-05 15:18:14 CEST

Keywords: (none) => Atelier

Comment 2 Marja Van Waes 2012-09-25 08:37:03 CEST
@ rda

It always gave me an uncomfortable feeling, that doc team had, and partly still has, a temporary solution on mageia.nl, but that no such temporary solution was available for art team.

At that time, I couldn't find an available mageia.* domain, but now I have one.

I'm willing to let someone use it for a temporary solution of this bug, until a permanent fix on mageia.org is available.

However, would it maybe be better to give it (+ some server space along with it) to mageia.org, to avoid fragmentation of Mageia?

CC: (none) => marja11

Comment 3 Buchan Milne 2012-10-21 21:07:23 CEST
This issue was discussed by email, but the solutions (sparkleshare/git?) offered weren't taken, without very good reasons.

The requirements listed by max are not strictly 'server space', or a file transfer protocol (specifically the gallery portion).

So, we need to discuss options further.

It may be that a gallery-type application may be better.

Or would just a webdav share be better? Or FTP with SSL? Or some more modern cloud storage API?

CC: (none) => bgmilne

Comment 4 ra oeai 2012-12-22 21:37:22 CET
shared dropbox and google groups, google docs for docs, but the other way that i was thinking is using github - at least for docs it is very nice, i know that dropbox was searching or buying music and photo services so maybe they already have something and just to show work to others it should be done in fb group or create a google group, i think that google stores more information so you will not need to search more space to store it. and there can be closed and open groups so not approved works will be in closed group for discuss and work, while approved will be stored in opened group.
for github i'm not really sured of disck space that they are providing
of course i can share my own ftp, but there's only 25mbits capacity and i got only about 80gb free space on it and no backup and even no ups right now.

and yes actually in dropbox each member can have his own storage that can be shared with others and then it will be pumped up into group folder and then in google or fb group, i'm up for social networks because it is a kind of showing that you are doing something to others to your friends at least - it is not so bad really.

so the real question what are the types of what will be stored, is it image files mostly?

CC: (none) => oeai

Nicolas Vigier 2013-04-09 12:02:30 CEST

CC: (none) => atelier-bugs

Nicolas Vigier 2013-04-09 12:04:15 CEST

CC: mageia-artwork => (none)

Comment 5 Donald 2014-01-09 12:29:09 CET
Git space would be fine for the internal storage of work in progress and of the final pieces.

The gallery was/is needed for hosting artwork collection from the public as we can't expect them all to have git access.

So we would happily take the git space as soon as we can get it as we are running into major issues with not knowing what is the current piece we should be using.

CC: (none) => watersnowrock

Comment 6 Sander Lepik 2014-01-09 12:55:21 CET
What about ownCloud instance for Mageia. OC supports LDAP for user management and since version 6 you can share public galleries too. Atelier could probably use some shared folder there to do their work and share it publicly if they think they have something to show.

It could be used for other such stuff too if we have enough free space.

CC: (none) => mageia
Hardware: i586 => All

Comment 7 Rémi Verschelde 2014-01-09 13:03:22 CET
Some people already talked about owncloud a while ago, and it would indeed seem like a great tool for atelier.

The issue here is to actually get things done. If someone is interested in owncloud and wants to set it up with LDAP support for Atelier, I think we're all in. In the mean time, a git repo is probably quite easy to set up, together with a mga-atelier LDAP group, so we'd gladly take it.

CC: (none) => remi

Comment 8 Patricia Fraser 2014-01-09 14:27:58 CET
One of the main reasons we need a git repo for Atelier is version control - we're finding that more and more difficult to achieve using Dropbox, and it would seem that any cloud-based storage system would have the same problem of requiring manual versioning. It only needs one person to forget, or not to know what they're supposed to do, and the whole thing goes pear-shaped.

Atelier's been waiting for space for quite a while - and it's been council-approved for ages. It would be very good if it could come up to somewhere a bit closer to the top of the list.
Comment 9 Filip Komar 2015-01-26 12:21:07 CET
Is this sufficient:

CC: (none) => filip.komar

Comment 10 Rémi Verschelde 2015-01-26 12:23:12 CET
IMO the git space is sufficient, this bug can be closed.
Now it's up to us in atelier to organise things a bit there. I'll try to do a proposal in the coming weeks.
Comment 11 Filip Komar 2015-01-26 12:34:43 CET
Closing. Please reopen if needed.

Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.