Public SourceMage Discussion List

["Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>]

On Oct 24, Andrew [afrayedknot AT thefrayedknot.armory.com] wrote:
> On Mon, Oct 24, 2005 at 08:15:51AM -0700, Jason Flatt wrote:
> > On Sunday 23 October 2005 11:59 pm, Jeremy Blosser (emrys) wrote:
> > >
> > > 3.  It should be the individual Team Leads' responsibility to make sure
> > >     things in their areas of the wiki that are complete get moved to the
> > >     Drupal site in a timely manner.  The Tome team and the Project
> > >     Lead/Asst. Project Lead will be available to help with this, but it
> > >     will be the TL's job to make sure it gets done.  Drupal will remain
> > >     editable only by those who have edit permissions, which includes the
> > >     Tome team, the Leads, and their designees.
> > 
> > Knowing how things currently are with the Source Mage development team
> > (and how they were in the past), I'd say that the wiki will end up
> > being the primary doc site, because only a very few people will move
> > the final docs to the Drupal side.  As it is, the team leads don't even
> > update their own objectives very often, and no amount of poking by any
> > project leader has improved that.  Very few people want to document --
> > they only want to code, and that's universal.
> 
> I tend to agree, its a good idea but it seems like it wont work in
> practice, both because of social problems (I prefer to code), and because
> of technological issues. Wiki markup isnt the same as html markup so it
> would be a non-zero amount of work to transfer wiki->drupal book. That
> just adds to the social aspect of the problem, now not only do I prefer to
> code, but when I have the motivation to work on docs, its more difficult
> (for me, i prefer wiki markup to html, i know that isn't universal). As
> proposed I dont think this solution will work.

While I tend to agree we're likely to end up with way more stuff on the
wiki than in Drupal, I don't know why we couldn't automate the more routine
parts of the conversion.  Heck we may be able to automate all of it
depending on how tolerant Drupal is of having its db modified behind its
back.

If the Tome team thinks their job is made easier by having one framework to
pull all user-facing stuff into, I want to support getting them there as
long as we can still meet the needs of developers.  I don't see this as
different from other teams wanting to put reasonable limits on the types of
things their systems are expected to handle.

Attachment: pgp4O7Ud1PT0K.pgp
Description: PGP signature