[sword-devel] [OT] just join, testing only

DM Smith dmsmith555 at yahoo.com
Sat Nov 8 05:13:20 MST 2008

On Nov 8, 2008, at 4:50 AM, Chris Little wrote:

> Matthew Talbert wrote:
>> On Fri, Nov 7, 2008 at 11:19 PM, Chris Little  
>> <chrislit at crosswire.org> wrote:
>>> Note that the links on the main page of the Wiki are intended for  
>>> links
>>> to development Wikis ONLY. I know there are links to project pages  
>>> as
>>> well, but those are more properly placed within the main website.  
>>> The
>>> Wiki is basically for development purposes (the FAQ being the main
>>> exception).
>>> I'll go through the Wiki this weekend and clean out these links and
>>> other inappropriate content/pages.
>>> --Chris
>> Could you explain this a little more? Since the wiki was started,
>> there have been project pages for different frontends. In addition,
>> there are pages about suggested fonts, module repositories, how to  
>> get
>> sword for different platforms (Asus EEE), etc. Where is this
>> information supposed to be, if not on the wiki? I guess I was unaware
>> that it was only for development purposes.
> The main pages (www.crosswire.org and www.crosswire.org/sword) are  
> where
> most user-oriented material should go, including blurbs about &  
> links to
> software using Sword. It's inconsistent to have half of the software
> links on the main page linking within the Wiki and half linking to
> off-site main pages.
> Using the Wiki to perform collaborative document editing, as with the
> FAQ or the Eee guide, is great. But the Wiki isn't the main CrossWire
> page, nor its public face.


I have replicated nearly all the static pages of the CrossWire website  
into the wiki. I have done this gradually over time. I was frustrated  
that we would discuss the front page, how it was woefully out of date,  
having many dead works and not clearly identifying the active and most  
useful front-ends. (I don't think the front page should be focused on  
development, but rather should lead to it.) I also noticed that many  
of the rest of the pages were incorrect (e.g. references to locked  
modules and how to work to unlock them).

So I created a personal site map, which I shared here. And then I  
started adding the content of the static pages into the wiki,  
correcting them and improving them as we went.

I think it is important for the CrossWire website to be fresh and  
current. As one comes to the home page, it should give the best  
impression. I don't think it does.

The value of the wiki is that it is a collaborative effort, maintained  
by everyone and overseen by those that care.

As to being a developer's place, that may have been the original  
intent, but it is hardly how it was used. I believe that GnomeSword  
was the only front-end project that used it as a whiteboard for  
planning. For whatever reason, that activity has been moved out of the  
CrossWire wiki. The only development activity has been regarding  
module development. And that is very good.

So my recommendation is to leave the wiki as is until such time that  
the rest of the CrossWire website is being cleaned up and actively  
maintained by a larger group.

In Christ's Service,

More information about the sword-devel mailing list