#3533 Request for Resources: Gallery3 instance
Closed: Fixed None Opened 8 years ago by spot.

= phenomenon =

I would like for Fedora to host a Gallery 3 instance, so that we can have a centralized place to put pictures from FUDCons (and other Fedora events). I'm willing to maintain, and Ruth Suehle is willing to help maintain as well (she has experience doing this internally at Red Hat).


ok. I run a gallery instance at home as well. I'd be happy to work with you on this.

Since gallery3 is already all packaged up, the next step is probibly a dev instance. I can look at setting up one. There we can figure out any quirks of the setup/install/workflow process.

Some questions we will need to consider/work on:

  • How much space should we look at allocating ? Would we keep pictures forever, or expire out old ones?

  • Would there be a group curating pictures to weed out offensive/bad license?

  • We probibly need some kind of submission guidelines/sop for submissions. (License ok, must be Fedora event, etc)

  • Would we want to cache this behind our proxy/varnish caches? Or leave it on it's own? I think it might evict some of our other services since images are so large.

  • Would we want to look at multiple frontends? Can gallery3 even handle multiple frontends? If so we could do a pair with glusterfs shared storage for the images if needed.

I'll look at spinning up a dev instance soon and creating a sysadmin-gallery group.

Lets start with 10GB of space. If we eat through that, we should be able to grow it, but I imagine it will take us a while.

I'm working with RH Legal to figure out if we can use the FPCA to ensure default license (CC-BY) for all the photos. That will simplify things, but you can assume that Ruth and I will be responsible for weeding out any offensive/inappropriate pictures, as the gallery3 admins.

I haven't run gallery in so long that I've probably forgotten anything that is remotely relevant, but I think we might also want to use FAS accounts for access here (to enforce the FPCA check), which I doubt it supports out of the box.

As to caching, we don't want to inconvenience any other services, so we can leave it on its own for now.

Replying to [comment:2 spot]:

Lets start with 10GB of space. If we eat through that, we should be able to grow it, but I imagine it will take us a while.

ok. I gave the dev instance 20G... we can evaluate again before moving to staging or production.

I'm working with RH Legal to figure out if we can use the FPCA to ensure default license (CC-BY) for all the photos. That will simplify things, but you can assume that Ruth and I will be responsible for weeding out any offensive/inappropriate pictures, as the gallery3 admins.

ok.

I haven't run gallery in so long that I've probably forgotten anything that is remotely relevant, but I think we might also want to use FAS accounts for access here (to enforce the FPCA check), which I doubt it supports out of the box.

Perhaps it can use openid?

As to caching, we don't want to inconvenience any other services, so we can leave it on its own for now.

ok.

So, I have created a gallery01.dev.fedoraproject.org to work out how we want to set things up, etc.
There is also a sysadmin-gallery group for shell access to this server.

Next steps would be to install gallery3 there, and determine the best setup/config and begin writing up a SOP for anything we need to do to maintain it moving forward.

Red Hat Legal cleared this as long as we ensure the following:

  • Only FAS users who have agreed to the FPCA may upload/edit photos in Gallery
  • The upload/edit pages contain the following disclaimer text: "Please
    do not upload photos of people who were not aware that their picture was
    being taken."

I don't know if we can do that first item with OpenID alone. Can we?

Replying to [comment:4 spot]:

Red Hat Legal cleared this as long as we ensure the following:

  • Only FAS users who have agreed to the FPCA may upload/edit photos in Gallery

ok, so likely we will need to create a fas plugin and perhaps only let those users login. Gallery3 is php, so we may be able to reuse some of the work from the mediawiki plugin perhaps.

  • The upload/edit pages contain the following disclaimer text: "Please
    do not upload photos of people who were not aware that their picture was
    being taken."

Hopefully gallery3 has a way to display this. I guess we will have to explore a bit and find a way to do that.

I don't know if we can do that first item with OpenID alone. Can we?

nope. OpenID only allows a 'authed' or 'not', no group information, etc. ;(

  • The upload/edit pages contain the following disclaimer text: "Please
    do not upload photos of people who were not aware that their picture was
    being taken."

Hopefully gallery3 has a way to display this. I guess we will have to explore a bit and find a way to do that.

You can skin it like anything else. Shouldn't be a problem.

Replying to [comment:5 kevin]:

Replying to [comment:4 spot]:

I don't know if we can do that first item with OpenID alone. Can we?

nope. OpenID only allows a 'authed' or 'not', no group information, etc. ;(

Don't we provide OpenID only for Cla+1?

Yeah, it does require cla_done.

So, it could work out, provided we can find a gallery3 openid plugin that works... ;)

After discussion with Kevin, I will take care of the software stack of this service.
I have a working development instance working right now, using OpenID.

I will look into turning this into staging soon.

So, 3 years later... we have had one running in staging, but have done nothing at all to it. ;(

Do we still want to do this? If so, we should push it forward, if not, we should close this.

I think we can turn this off. It was a nice idea, but neither I nor Ruth have time to do it anymore.

Login to comment on this ticket.

Metadata