For the newbs, by "project website" do you mean /<a href="http://www.crosswire.org/wiki">www.crosswire.org/wiki</a>?<br><br><div class="gmail_quote">On Tue, Nov 11, 2008 at 1:22 PM, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Top posting because I am commenting in general on this thread.<br>
<br>
The CrossWire main page should be very brief, concise, clean, hardly<br>
ever changed, and point people to project websites... and static.<br>
<br>
We have a very strange situation. CrossWire is intended for 2 very<br>
different groups of people. Everyone on this list is interested in the<br>
development process. MOST users are not-- especially Windows users<br>
(with whom most of us developers have a hard time sympathizing).<br>
<br>
The main CrossWire page attempts to sensitively cater to both. We<br>
briefly point out our developers' pages for SWORD and JSword<br>
immediately, and then go straight into an attempt to direct users to<br>
their frontend, organized by OS.<br>
<br>
In principle, I think we have the right idea. In practice we may not<br>
have hit this target as central as we would have liked.<br>
<br>
I agree with the need to let more people update things, but not for the<br>
main CrossWire page. And project pages have always been up to each<br>
project on how they let their pages be edited. If they want to have<br>
their whole page be a wiki, then they are welcome.<br>
<br>
But again, for the main CrossWire page, if things need to be edited<br>
often, then we haven't done our job with its purpose.<br>
<br>
As for the 'project website' for The SWORD Project engine...<br>
I'd love for more of The SWORD Project developer pages to be wiki<br>
editable and updated. Some of these things have already happened with<br>
the module creation pages, the .conf layouts, etc.<br>
<br>
We do have a static set of policies that I'd like to keep static-- our<br>
purpose statement, etc.<br>
<br>
And I'd love to give access to a few old-timer volunteers, who<br>
understand our terminology and goals, to update the CrossWire main page<br>
when they see it out of date. Volunteers?<br>
<br>
Feel free to tell me why I'm wrong. I figure if I give permission, then<br>
I'm reducing your sin. :)<br>
<br>
-Troy.<br>
<br>
<br>
<br>
Jason Galyon wrote:<br>
> Manfred Bergmann wrote:<br>
>> Am 10.11.2008 um 21:46 schrieb Chris Little:<br>
>><br>
>><br>
>>> The Wiki is just plain unattractive. We've got a fairly consistent<br>
>>> look<br>
>>> throughout the Sword, CrossWire, JSword, & other crosswire.org-hosted<br>
>>> sites. The Wiki is has an inconsistent and very plain appearance with<br>
>>> respect to the Sword site that would presumably point people to it.<br>
>>><br>
>> I think the wiki is not unattractive. It is light and bright, the<br>
>> color are ok and people (maybe) are familiar to it because of wikipedia.<br>
>> Currently I think it is more attractive and inviting than the static<br>
>> web page.<br>
>><br>
>><br>
>>> Collaborative editing often leads to bad edits. There are parts of the<br>
>>> CrossWire & Sword sites that are out of date and now possibly<br>
>>> inaccurate, but edits to the Wiki can (and have at times been) new and<br>
>>> inaccurate. We get spelling and grammar errors that make us look<br>
>>> unprofessional. We get branding inconsistencies since not everyone<br>
>>> knows<br>
>>> (or is careful about) the letter casing of the SWORD Project or<br>
>>> CrossWire.<br>
>>><br>
>>> I try to read all Wiki edits, and I know I've seen you do<br>
>>> corrections in<br>
>>> the past. But I can't guarantee that I will catch every bad commit and<br>
>>> it takes time out of my schedule during which I would rather do<br>
>>> something else.<br>
>>><br>
>> I could think of responsible people who check edits and tell the<br>
>> editor: "go back and correct your things".<br>
>> The wiki could be split in certain parts where there are more than one<br>
>> who "responsible" that content is ok.<br>
>><br>
>><br>
>>> If we want a more up-to-date webpage, Wiki is not the answer. A CMS<br>
>>> is.<br>
>>> Wikis are for collaboration and whiteboarding.<br>
>>><br>
>> A CMS would also be a good idea to start over with an updated web page.<br>
>><br>
>><br>
>> Manfred<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>
> Wikis are by their very nature, what you make of them. If ugly then the<br>
> mirror is the best place to throw stones.<br>
><br>
> Besides, many people look for functionality over aesthetic and 'purty'<br>
> appeal. Content counts.<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>
</blockquote></div><br>