[sword-devel] Wiki articles

[Peter Von Kaehne]

Dear all,

After a flurry of activity the wiki does hopefully look a better place. 

There are though a number of areas which need attention. And now that they are visible, I think they deserve fixing. 

1) There is now a series of pages on the front which claim to be active proposals. Having said that, none of the pages have been touched for years. (other than by David and me in last couple of days). I simply put them there as this was a good place and as genuinely active proposals certainly should be displayed in this fashion.  

The pages are 
https://crosswire.org/wiki/DevTools:PersistentKeyList
https://crosswire.org/wiki/TEI_Dictionaries/DictionaryProposal
https://crosswire.org/wiki/Git_Migration

Could those who started them (or feel otherwise called) either tell me that the pages are now irrelevant (and I delete them) or else do something useful?

2) We have two pages full of module suggestions. Some are done, some will never get done (because the proposals are dumb, because the texts are closed off or because no one wants to do them), some might well get done. But at the current rate the pages are impossible to deal with, overloaded, disorganised with a lot of relevant info hiding on the talk pages associated, dead links abounding etc etc. What would be good if the pages could be reorganised in a simple but effective fashion - dead links removed, the rest sorted through as als ready actually done (delete please), feasible (text exists online in an accessible format, is freely licensed and simply needs someone to pick things up), possible (make up your mind what you consider possible) or impossible (no text online, or just in form of pretty pictures/PDFs and license anyway prohibitive - so maybe delete it too). 

The pages are: 

https://crosswire.org/wiki/Module_Requests
https://crosswire.org/wiki/Non-CrossWire_Text-Development_Projects

The second one is likely to be more interesting as it is all about people trying to create open access texts. 

This needs someone diligent and careful, with an eye for the possible (understanding of licenses and text quality presented), but by no means anyone technical. Given that we have the pages in the history easily recallable, you can certainly be radical and creative. A neat table would be nice. Something someone who is bored can look at and always wanted to create a module can take an easy pick from. Something which we can look at and clean up easily in a couple of years. Something which will not look just as bad as this after 3, 4 years of new neglect.

Many thanks!

Peter