Not knowing much about Plone yet, I agree with the plan, except that step 1 shall be performed by someone having FTP access to the site (IOhannes). So do I understand right, that rather than migrating the whole content as it is, you are suggesting a restructuring/cleanup? If so, I support the idea, but the process will need to be refined further.
András On Thu, Nov 22, 2012 at 12:54 PM, Nicolas Montgermont < nicolas_montgerm...@yahoo.fr> wrote: > Hello all, > > I was thinking on how we may manage this switching, specially if we must > have to start from a fresh install, I think there are few clear steps: > > 1 - installing a new hidden plone. > 2 - thinking the architecture of the new site > 3 - filling the architecture with the "old" content > 4 - graphical design of the new site > 5 - filling the website with member contents > 6 - checking and switching to the new version. > > A proposal on how we should do that: > step 1 : handled by Andras. > step 2 : discussion on this list > step 3 : handled by section responsables (if we agree on this kind of > organisation) > step 4 : discussion on this list and marco's implementation. > step 5 : maybe we can send a mail to every member of the actual site to > have them move their own content? > step 6 : pdweb-list and maybe pd-list help. > > I think it's no problem if we have all this switching lasting a few > months. The longest step for me is step 5, and I think it's really better > if we let a long time to people to switch their content. > An intermediate part of the website between members and architecture is > the community section, where it is good to have people create their own > page for patching circles and others. I am ok to write a little tutorial to > achieve an homogen creation of specific pages, and to write individual > mails to each local groups member. > > best, > n > > > Le 09/11/12 22:41, IOhannes m zmölnig a écrit : > >> On 11/09/2012 07:06 PM, András Murányi wrote: >> >>> >>> Definitely that is the way. By "duplicating" I meant exactly this: to >>> make a completely independent, not publicly visible copy of the existing >>> web site, where we can play around until it's perfect. >>> Attention: we'll have to take into account, however, that the existing >>> web site may evolve meanwhile we're playing around with the copy, so >>> before finally swapping in the new one for the old one, we'll have to >>> make sure that any content that was added to the new one is reflected on >>> the new one as well. We'll how see how exactly this is best achieved. >>> >> >> glad to see so much activity here... >> >> >> >>> About the first steps: according to [1] it's not really a copy of the >>> >> >> the biggest problem i remember is, that the puredata.info instance uses >> a custom plone product for storing media files on the filesystem rather >> than within the zodb. >> currently, there are about 3GB of files external to the zodb; after an >> upgrade those files should still be available somehow. >> this might require either someone with zope/plone skills illing to >> upgrade that product manually or a patient hand (manually copying the >> files). >> >> >> existing site that we'll need but an EMPTY Plone 3.3.x install. When >>> IOhannes has the time to set it up, we're ready to go. >>> >> >> i'm basically out-of-office for the next 2 weeks, but after that my >> stress level should diminsh considerably. >> >> >> fgmasdr >> IOhannes >> >>
_______________________________________________ Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/listinfo/pdweb