Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 2 Apr 2006, Jason Flatt wrote:
> It seems that the two lists in the two different e-mail on this topic are very
> different.

The latest is the more correct one based on our RoadMap on the webpage
and without additions.

> On Thursday 30 March 2006 02:11 pm, Eric Sandall wrote:
<snip>
> Yes, I (or my team) will get this done.  Do we want this to be
> docs.sourcemage.org, or api.sourcemage.org?  Do we want other things there,
> such as the man2html docs I have listed below, and possibly the spell
> listings, or is it strictly for the bashdoc stuff?

Possibly all of the above. api.sourcemage.org for Sorcery APIs (the
APIs that spells/scripts can use, IMO) and docs.sourcemage.org for
converted info and man pages (including Sorcery's).

> On Saturday 01 April 2006 03:55 pm, Eric Sandall wrote:
> > Tome:
> >    * Online documentation (e.g. Sorcery BashDocs on
> > http://docs.sourcemage.org/)
> Yes, I (or my team) will get this done.
>
> >    * NNTP service
> Isn't the GMame setup that Adam did handling this item?  If not, I did not
> have plans for implementing it, and will not be making it a priority.

I believe GMane does NNTP, but I haven't verified it so it's not
marked as DONE yet.

> >    * Linking forums, mailing lists, and usenet
> For some reason, I thought this item got tabled, though I can't seem to find
> where I got that idea from.  I would be happy to get it done, but not as a
> priority for 1.0.

I believe it was deemed near impossible (or very difficult) to have
Drupal forums and the mailing lists (assuming Gmane does NNTP for us)
to be 'linked'.

> >    * Website should be distributable
> I thought this was tabled, also, but I cannot find what made me think that.  I
> think it may have been the current server setup and backups.  If not, it will
> not be a priority for 1.0.

I believe there were issues with MySQL and doing master/slave syncs.

> >    * Website stored in an SCM
> Done by Adam.

Saw your reply to this. Yes, SCM, not CMS. ;)

> Some other things I wanted to get done pre-1.0:
>  * I actually want to get all the documentation under the areas of "About
> Source Mage" and "Installing Source Mage" (at least) current and correct on
> the main Web site.

At least the installation instructions is what I asked for. What in
'About Source Mage' needs cleaning up? Just
http://bugs.sourcemage.org/show_bug.cgi?id=10690 ?

>  * Integrate the Source Mage man pages with the main web site, through the
> use of Seth's man2html code [0].

That'd work for docs.sourcemage.org as noted above, I think.

>  * Implement language translations on the main web site [1].  It's been
> started, but I've run into a snag on this one, so I'm not sure how far I will
> get.

I think, as you mention in the bug, this will be a never-ending
process. I'd assume you mean only the Drupal Books to be translated
and not the Works In Progress that we use the Wiki for?

>  * Get as much of the Web files as practical and/or possible into an SCM.

I think the main issue with this was putting the database in the SCM
(or any file) that contains other people's passwords (and other
information).

> [0] http://bugs.sourcemage.org/show_bug.cgi?id=10365
> [1] http://bugs.sourcemage.org/show_bug.cgi?id=10366

- -sandalle

- --
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEMe6zHXt9dKjv3WERAuI8AKDEQTyQdoGyXrkdZyo9ncN9saD9igCfXNVb
mhOreeNYnfvJk/wrow3xYMs=
=Z2Z4
-----END PGP SIGNATURE-----