All,<div><br></div><div>My first impression, albeit a few years ago, was the same thing. I found it particularly hard to find my way around things. By chance I managed to stumble across the Jira instance, but then lost it again when I was wanting to see how much activity was happening. So whether a CMS or some other solution is the best answer, I don't know. What would be good though </div>
<div><br></div><div>Just one example, try and find the page for JSword from the home page. I have just tried and haven't really been that successful. Also, the "Developers" page <a href="http://crosswire.org/sword/develop/index.jsp">http://crosswire.org/sword/develop/index.jsp</a> encourages you to click on a link, which takes you nowhere (i.e. to the same page). As a result, you start wondering where the information is, or whether the link is a broken link.</div>
<div><br></div><div>I'm not sure we want to ditch the whole lot, as there are a lot of good things there, but it might make sense to revist the nagivation a bit and maybe introduce a site map?</div><div><br></div><div>
Chris</div><div><br><br><div class="gmail_quote">On 8 November 2010 09:17, Caleb Maclennan <span dir="ltr"><<a href="mailto:caleb@alerque.com">caleb@alerque.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Troy and Chris et all,<br>
<br>
I cannot speak for what David felt as the exact problem, but I can<br>
tell you why I jumped in with a comment. Troy it's hard to come up<br>
with a specific example because the problem might be best described as<br>
general discombobulation. The main crosswire site and the sword sub<br>
site are both navigational catastrophes. This happens over time as<br>
people come and go and projects eb and flow. I know how it is. The top<br>
level layout has lost focus and usefulness to newcomers and content<br>
has stagnated.<br>
<br>
Chris you mention the issue of balancing devel news / nightly snapshot<br>
type updates and releases that the public aught to be informed about.<br>
I realize this is an issue, but it was pointed out just last week on<br>
this list that the information for diatake on the site is some ten<br>
years old and there is no indication that it has actually been<br>
maintained to this day. Surely that's erring on the side of not enough<br>
up to date information.<br>
<br>
Also it was pointed on on another thread that there is a crosswire<br>
wiki. Even new module developers seem to miss that this exists. I<br>
looked and didn't see any reference to it on the crosswire home page.<br>
Furthermore a quick glace at each area shows massive duplication of<br>
content between the main site and the wiki, usually with the scales<br>
tipping to the wiki for being up to date. A little more poking shows<br>
even further duplication and even older content on the sword specific<br>
sub-site.<br>
<br>
Troy you mention the word involved in "committing to the maintenance<br>
of another framework". From the outside it looks like there are<br>
already at least a trio if not half a dozen frameworks that don't<br>
interact and are in various states of disrepair. I chimmed in on this<br>
thread because it sounded like David was suggesting getting all of the<br>
above under one heading so there is only one framework that actually<br>
CAN be reasonably maintained.<br>
<br>
Further thoughts?<br>
<font color="#888888"><br>
Caleb<br>
</font><div><div></div><div class="h5"><br>
On Sat, Nov 6, 2010 at 14:49, Troy A. Griffitts <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br>
> I agree with Chris on this issue. CMS has been a debated topic in the past.<br>
><br>
> From my conservative position, you must give a specific, real world<br>
> problem we currently have which is not easily solved with our current<br>
> infrastructure, or a real world benefit we are currently lacking because<br>
> we do not have something labeled a "CMS", for us to even consider<br>
> committing to the maintenance of another framework.<br>
><br>
> Troy<br>
><br>
><br>
><br>
> On 11/06/2010 12:22 PM, Chris Little wrote:<br>
>><br>
>><br>
>> On 11/6/2010 3:49 AM, David Haslam wrote:<br>
>>> We have an ftpmirror that does not keep track of updates to scripts and<br>
>>> other software tools that we host.<br>
>><br>
>> What you're referring to here (linking directly to the SVN versions of<br>
>> perl scripts that we maintain) would be akin to replacing every single<br>
>> binary we provide with nightly builds. We don't need to be publishing an<br>
>> SVN commit that I made just over 12 hours ago when it hasn't even<br>
>> undergone testing beyond one or two USFM docs. The perl scripts change<br>
>> seldom and slowly, and they are used and tested by very few people.<br>
>><br>
>> --Chris<br>
>><br>
>> _______________________________________________<br>
>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at above page<br>
><br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>