Re: Call for help in DarwinPorts Transition to MacOSForge

Hey James and others,

Here are my thoughts...


I'd be happy to help as I can, and as you can recall I was vocal in  
helping with documentation, but I was never clear as to the consensus  
on what was envisioned with our documentation. I have my ideas, but I  
don't want to assert myself if this would be unwelcome.

As for the site, I'd used WordPress extensively... It allows for  
multiple site blog and static page templates, but it may take a plug- 
in of some sort to allow the combination of:

1) a symlink from the DarwinPorts home directory to the master  
WordPress code base
2) usage of a separate templates directory depending on the value of  
PHP's $_SERVER['REQUEST_URI'] variable (i.e. the URL being used to  
access WP).

If the MacOSForge guys are cool with sharing a templates directory  
with DarwinPorts, or with tweaking WordPress to allow this sort of   
thing, WordPress could work out very nicely for plugging in text/HTML  
code into the site templates.


So, this is far from a formal proposal, but I think that perhaps  
before one can be issued we'd need to know about the nature in which  
we would be working with MacOSForge as an ISP, how you envision  
delegating access to make changes to the website, who the convent  
providers are and what we are doing to generate content, and what  
sort of CMS would work best (there are many choices).

Sorry to be so wishy washy here. If you are just kicking tires and  
seeing who is interested, I am =)



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

> As we begin to transition from our current hosting at opendarwin,  
> to our new hosting facility at Mac OS Forge (www.macosforge.org)  
> there are a large number of tasks to complete.
>
> I'd like to get a list of volunteers who can contribute in a  
> meaningful way to assisting with this transition.
>
> 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. We'll probably migrate our bug database  
> from bugzilla to trac, although some of the details of that have  
> not yet been worked out. As announced earlier, we're also going to  
> be using this opportunity to change our name from darwinports to  
> macports, using the macports.org domain.
>
> Most of the labor in moving from cvs to subversion can be  
> automated, as can, we believe, some things like migration of the  
> bug database. There are, however, certain key aspects of our  
> existence that cannot be so easily moved. These include the  
> following "Documentation" tools:
>
> 	- 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.
>
> I don't think that's as huge a job as it may sound, as there aren't  
> really _that_ many pages of documentation there. There's even xml  
> for the guide, which you might be able to do something tricky with.  
> This is, of course, also an opportunity to bring some sanity and  
> beauty to some of these areas that have been ignored for too long.
>
> Who can volunteer to help us through this transition?
>
> James
> _______________________________________________
> Darwinports mailing list
> [email protected]
> http://www.opendarwin.org/mailman/listinfo/darwinports