Matti, Let me know if you need help in migration. I sent you my contacts in a dm.
On Mon, Apr 30, 2012 at 12:34 PM, Alexander Jones <[email protected]> wrote: > Are we not able to just migrate all of the old website content onto the > main Qt website in the longer term? Hosting a HTTP 301 'moved > permanently'-issuing website to keep old links alive indefinitely would be > very cheap. > > > On 30 April 2012 18:39, Hugo Parente Lima <[email protected]> wrote: > >> On Monday, April 30, 2012 10:30:46 AM Srini Kommoori wrote: >> > I would like to propose S3/github for website hosting. It is pretty >> easy to >> > setup and we can automate to push the code/html pages very easily. >> >> I agree, github for website hosting. >> About the tarballs, we have tags on git for each release, so IMO tarballs >> are >> just another way of offer the same information and we can discard if it's >> causing troubles. >> >> > Here is my preferred service list: >> > S3/github for all static pages. >> > Blog - Blogger/Tumblr with multi user submits. >> > Wiki - [No change] Seems like already integrated with Qt main site. >> > Code - [No change] gitorious >> > >> > I can help and sponsor for the expenses(if any) related to the >> migration. >> > >> > thanks, >> > -Srini >> > >> > On Mon, Apr 30, 2012 at 9:18 AM, Erik Janssens >> > >> > <[email protected]>wrote: >> > > Hello, >> > > >> > > We have a professional Weebly account, >> > > (http://www.weebly.com/) and can offer a site account for >> > > this purpose. >> > > >> > > A Weebly site can host web pages + images + forms. But it's >> > > not suited to offer source or binary packages for download. >> > > >> > > The downside of using Weebly is that the site should be rebuild >> > > from scratch, something I estimate to be a couple of hours work >> > > for someone experienced with CSS, html. >> > > >> > > The upside being that it's very easy to maintain. >> > > >> > > Just let me know if this would be interesting... >> > > >> > > Cheers, >> > > >> > > Erik >> > > >> > > On Mon, 2012-04-30 at 14:45 +0300, Matti Airas wrote: >> > > > Hi list, >> > > > >> > > > There's one final thing in the PySide migration to Qt add-on: the >> > > > website. I've been trying to have the migration arranged, but >> progress >> > > > has been very slow. Also, May 3 is my last work-day at Nokia, so >> that >> > > > complicates things further. >> > > > >> > > > PySide is currently hosted at a Virtual Machine provided by Nokia >> IT, >> > > > which has made it easy because there have not been any fees or >> bandwidth >> > > > quotas (and the connectivity has been quite excellent). >> Unfortunately, >> > > > that VM is leased only until end of June, so arrangements need to be >> > > > made pretty soon. >> > > > >> > > > Unfortunately, Qt Project is unwilling to provide a virtual machine >> for >> > > > PySide, and therefore a direct migration of the VM is not feasible. >> They >> > > > have proposed that they can host the static content (binaries, >> > > > documentation & doc packages) which account for vast majority of the >> > > > traffic anyway. Then, the current WordPress site contents (which >> isn't >> > > > much any longer, anyway) could be moved to the wiki, with a >> possibility >> > > > to have a static landing page as the home page. The news blog would >> then >> > > > need to be migrated to any free 3rd-party blogging platform such as >> > > > wordpress.com. This is probably doable and something that the >> project >> > > > could live with, but it does require additional effort and decrease >> the >> > > > level of service somewhat, both for the administrators (no access >> to WP >> > > > authoring tools) and for the end-users (URLs for binaries and docs >> > > > change, blog aggregation needs to be updated). In the long term, >> this >> > > > would be the approach requiring the least amount of maintenance. >> > > > >> > > > Another alternative which could be feasible is to have a VM >> elsewhere >> > > > and Qt Project would just point the DNS there. The VM requirements >> are >> > > > not huge: the current VM is a single-core one Xeon 2.5 GHz with 2 >> GB of >> > > > allocated memory and 40 GB of disk space. However, the site >> generates >> > > > quite some traffic - in April, 120 GB, and the number has been >> > > > increasing at a steady pace. Also, having a separate VM would >> require a >> > > > dedicated admin who would be willing to maintain the VM, take >> backups, >> > > >> > > etc. >> > > >> > > > I would like to hear your opinions on this one. In the first >> option, the >> > > > up front work and changes would be bigger but the long-term effort >> > > > lower, and no external costs would be incurred. In the latter >> option, >> > > > the migration would be less painful but having the VM would require >> more >> > > > maintenance in the future, and recurring payments would occur. >> > > > >> > > > Also, I'd like to call for volunteers to help with the migration >> and the >> > > > future maintenance. As said, my work obligation at Nokia is ending >> and >> > > > while I'm not vanishing altogether, it'd be helpful if someone else >> > > > could take the lead. Srini, you volunteered for the webmaster and >> > > > wikimaster duties in February - although this might not be what you >> had >> > > > in mind, would you still be interested? >> > > > >> > > > Also, if a separate VM is desired, a sponsor is needed for that. I >> > > > wonder if any companies would be interested in providing that, for a >> > > > modest logo or banner visibility on the web site? A basic 3rd-party >> VM >> > > > with that amount of traffic would cost some 40-50 EUR/USD a month. >> Not a >> > > > huge sum, but I wouldn't feel happy paying it out of my own pocket, >> > > > especially with the steadily increasing traffic. >> > > > >> > > > Cheers, >> > > > >> > > > Matti Airas >> > > > _______________________________________________ >> > > > PySide mailing list >> > > > [email protected] >> > > > http://lists.qt-project.org/mailman/listinfo/pyside >> > > >> > > _______________________________________________ >> > > PySide mailing list >> > > [email protected] >> > > http://lists.qt-project.org/mailman/listinfo/pyside >> >> _______________________________________________ >> PySide mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/pyside >> >> > > > -- > Alexander Jones > Double Negative R&D > www.dneg.com > > > _______________________________________________ > PySide mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/pyside > >
_______________________________________________ PySide mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/pyside
