Re: Call for help in DarwinPorts Transition to MacOSForge

On Aug 8, 2006, at 1:24 AM, James Berry wrote:

> As part of the transition, we will be moving from cvs -->  
> subversion, and also to trac, which provides bug tracking, wiki,  
> and web-view of sources.

Yay!

> - DarwinPorts site and guide
> - Wiki pages
>
> I suspect that both of those can/should be moved into trac, though  
> macosforge also uses WordPress for some things, so that might be a  
> candidate environment as well.
>
> We'd love to get hear from some people who can:
>
> 	- Develop a strategy for the migration of the DarwinPorts guide  
> and other site-based materials (and wiki) to our new home at  
> macosforge.
>
> 	- Work to complete the migration of those materials.

So it is:

1. The home page, which has news and news archives, plus it is  
written in many languages.

I would agree that WordPress is a good fit for this, more so than  
Trac. It will provide news archiving, time-based RSS feeds, and as  
far as multiple languages go, one of these should suffice: http:// 
codex.wordpress.org/Plugins/Translation_and_Languages

2. The DarwinPorts Guide

I would love to see the XML for this, to see what I can do about  
automatic migration onto Trac. Would the goal be to create something  
like this: http://trac.edgewall.org/wiki/TracGuide? Or is it to lose  
all structure and go full wiki, with lots of pages with descriptive  
titles? Edgewall themselves seem to use a hybrid approach, they have  
the aforelinked guide, but also lost of other pages in that wiki. See  
http://trac.edgewall.org/wiki/TitleIndex.

3. http://wiki.opendarwin.org/index.php/Category:DarwinPorts

If this is all that the wiki is, I would vote to merge this content  
onto whatever the result of migrating item 2 is.

4. Bugzilla

Hopefully this helps: http://trac.edgewall.org/browser/trunk/contrib/ 
bugzilla2trac.py

5. Subversion

As you mention, cvs -> subversion should not be that complicated. The  
only time I've heard of problems with this, is on very large trees  
that make the migration script run out of memory.

> Who can volunteer to help us through this transition?

I can. :)

I could start with the guide as soon as you folks decide on the  
details. Where is the XML?

--
Jordi Bunster
http://bunster.org/contact/