Bugzilla – Full Text Bug Listing
| Summary: | LocationCon 2017 - Add new domain for production and add an alias for staging | ||
|---|---|---|---|
| Product: | Community | Reporter: | Eric Poirier <eric.poirier> |
| Component: | EclipseCon | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | andrea.ross, chris.guindon, kat, nobody, Paul.White, thea.aldrich, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Eric Poirier
I've added the staging alias, and started wiring a basic vhost for the production side of things. So I have a couple of questions: 1) When is this going into production? 2) Are you really committed to the idea of using subdomains? Both of these stem from the fact that we'll need an SSL cert and wildcard certs are more expensive than 'plain' certs. -M. We could do locationcon.org/CalGIS2017, and not do a wildcard cert, however, I am happy to pay for a wildcard cert out of LocationTech budget and be done with it. (In reply to Eclipse Webmaster from comment #1) > I've added the staging alias, and started wiring a basic vhost for the > production side of things. When trying to access the following URL: eclipsecon-staging.eclipsecon.org/locationcon2017 I'm getting the "Sorry we couldn't find it" error. > > So I have a couple of questions: > > 1) When is this going into production? > 2) Are you really committed to the idea of using subdomains? > > Both of these stem from the fact that we'll need an SSL cert and wildcard > certs are more expensive than 'plain' certs. > > -M. Ok the staging is now running: https://www.eclipsecon-staging.eclipsecon.org/locationcon2017/ Andrea, Can you have a look at the site and let me know if you would like any changes to be made? Thanks. Thanks Eric. It looks great. Here's a bit of feedback: Please swap the LocationCon and CalGIS logos. They want to be on the left. Please swap the BayGeo logo for a CalGIS logo. Matt was supposed to provide one... I'll remind him. It can be simple like the BayGeo one. We'll want to swap the next up link... we can do that once the site is running on the production side. We'll also want to swap the past events... linking to FOSS4G NA 2015, 2016, FedGeoDay, and CalGIS 2016. We can do that once it's up in production. The twitter widget will be locationcon or CalGIS tweets.. again, we can fix that once it's running on the production server. We're going to need to overhaul the footer... Eclipse Foundation is supporting this one, but we're not organizing it in the same way we did FOSS4G NA, or EclipseCon for example. It's going to need to be me that does that given the nature of the relationships for this conference. I can fix that when it's running in production. Same with the Eclipse logo in the bottom right. (In reply to Andrea Ross from comment #2) > We could do locationcon.org/CalGIS2017, and not do a wildcard cert, however, > I am happy to pay for a wildcard cert out of LocationTech budget and be done > with it. Ok I'll make sure to send you the bill :). I'd still like to know when you plan for this to be live. Which leads me to another question: How long will we be keeping these sites around? Since each new year(or event) requires a DNS entry, at some point the list could get pretty long. Are you planning on archiving these somewhere after a period of time, or will we just be 'deleting' them? -M. No problem re: the bill. Thanks! Our policy for retention should be the same as EclipseCon. I believe that policy is to maintain the site for a year or two as is, and then maintain it as a static HTML site afterwards for a period of time. I am not aware of the point in which we start taking them off-line. Certainly keeping at least 5 years is important, but if we can maintain them longer, it's worth doing so. I know many speakers refer back to their talk they did at conferences. (In reply to Andrea Ross from comment #5) > Thanks Eric. It looks great. Here's a bit of feedback: > > Please swap the LocationCon and CalGIS logos. They want to be on the left. Ok that's no problem > Please swap the BayGeo logo for a CalGIS logo. Matt was supposed to provide > one... I'll remind him. It can be simple like the BayGeo one. Sounds good, I'll wait for Matt's logo > We'll want to swap the next up link... we can do that once the site is > running on the production side. You can give me the new link for the next up right now and I'll change it on staging before it's on production. > We'll also want to swap the past events... linking to FOSS4G NA 2015, 2016, > FedGeoDay, and CalGIS 2016. We can do that once it's up in production. Ok I'll have to tweak the module that creates the Past Conferences page so we can choose to print all the past conferences or only a specific list. > The twitter widget will be locationcon or CalGIS tweets.. again, we can fix > that once it's running on the production server. If you already have the twitter id I can change it on staging. > We're going to need to overhaul the footer... Eclipse Foundation is > supporting this one, but we're not organizing it in the same way we did > FOSS4G NA, or EclipseCon for example. It's going to need to be me that does > that given the nature of the relationships for this conference. I can fix > that when it's running in production. > > Same with the Eclipse logo in the bottom right. If you have a good idea of what you'd like to put in the footer. I'll have to alter the template on my end and it might be a better idea to make that change before it's on production. Just to let everyone know, I am now assisting with the design process for the CalGis logo, and the graphic of the LocationCon and CalGis side by side that will go up on the website. More to follow, but feel free to email me if you have any questions. (In reply to Katharine Hirsch from comment #9) > Just to let everyone know, I am now assisting with the design process for > the CalGis logo, and the graphic of the LocationCon and CalGis side by side > that will go up on the website. More to follow, but feel free to email me if > you have any questions. Ok thanks Kat for taking care of this. We can close this bug, the conference website is now on production and on staging. |