[haiku-web] Re: Renaming mailing list before R1
- From: Serpentor <serpentor013@xxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Tue, 26 Aug 2008 10:04:58 -0600
Niels,
I would like to help with the testing of the system as it gets migrated over
to the new server. Let me know when and I will make myself as available as
possible during that timeframe.
Serpentor
On Tue, Aug 26, 2008 at 9:23 AM, Jorge Mare <kokitomare@xxxxxxxxx> wrote:
> On Tue, Aug 26, 2008 at 2:30 AM, Niels Reedijk <niels.reedijk@xxxxxxxxx>
> wrote:
> >> I think what happened is that we were going to try to do the server
> >> migration and upgrade to Drupal 5.x at the same time. But it does not
> >> look like we are upgrading Drupal anytime soon, so we might as well do
> >> the server migration and get over with it first (that way we can kiss
> >> WF goodbye!). IIRC, we will have to migrate the email (to Gmail?),
> >> right?
> >
> > I would like to gently disagree about not upgrading Drupal soon.
>
> If there are people willing to work on the Drupal upgrade, then I
> agree. But if we struggle to find people/time for the upgrade, then we
> should not delay the server migration because of this, as we have an
> ISP contract renewal deadline that we cannot miss. The Drupal upgrade
> can happen after the server migration.
>
> > The
> > test migration I did a while back, which can be found at
> > http://experimental.web.haiku-os.org/, is pretty good. It needs some
> > polishing, but basically the data and the functionality migrate.
> > Things to do are:
> > - I found two instances where we lose some data.
> > - Several modules have not yet been enabled again (such as the phpbb
> module).
> > - The theme still needs some minor tweaks: the one on the main website
> > evolved since I did the port. I would suggest actually doing the
> > development of the theme in the mercurial repository in order to keep
> > track of the changes.
>
> The theme is an asset that was created by non-programmers, and while I
> understand why the developers would want to put it in a version
> control system repo, I think this would have the effect of
> marginalizing the very creators of the theme by leaving them out of
> the contribution process by imposing a tool we do not use. This is not
> nice, to say the least. Please remember: we are not programmers and
> don't know have the skills to use such a system, and most probably
> have no time or interest in learning it either (at least I know that I
> don't).
>
> We went through this before, on this list, and in that occasion, after
> some discussion Axel was gracious enough to acknowledge that it should
> be up to the creators of the theme; I thought we had put this topic to
> rest back then, but apparently not... :/
>
> > So basically I imagined it like this: I'd suggest I fix the last known
> > issues in the theme. Then we plan a weekend where we do the migration.
> > I'd suggest just finding a web of volunteers that try the migrated
> > site and through an IRC channel communicate with a few of us admins so
> > we can touch up the site where needed.
>
> I like the idea; I would try to be there if the meeting is scheduled
> with enough advance notice.
>
> A few observations based on a quick look to the experimental site:
>
> * Templates still need to be modified
>
> * Breadcrumbs seem to be missing from the Community & Development sections
>
> * Image embedding is missing from content creation forms (unless I am
> missing something); our current 4.x solution for this is suboptimal,
> but Drupal 5.x has some neat modules that would make adding images to
> content and managing them very easy; IMCE module comes to mind:
>
> http://drupal.org/project/imce
>
> * We may consider adding wysiwyg editing; they were pretty crappy back
> in the days when we created the site, but they have matured a lot, and
> a few are quite usable now.
>
> Jorge
> -----------------------------------------------------------------------
> haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
>
>
Other related posts:
