Thanks all for this effort. I woke up this morning delightfully surprised. Just a little background to what sparked this.
A year or so ago when we moved to a new hosting facility, we used the opportunity to begin migrating from RHEL 6 to RHEL 7 (CentOS, really). We did this by encapsulating a current snapshot of the RHEL 6 server into a VM and then proceeded to install 7 as the host OS, running 6 on top as a guest. We have been slowly migrating services from the 6 guest to the 7 host, in the hopes of eventually retiring the guest. The wiki is still running on the guest and has come up in discussion a few times over the past couple weeks. I have long lamented the lack of concise and pertinent information in our wiki. I imagine myself as a new visitor to CrossWire and find the wiki difficult to perceive the intent of which path I, as a new: core developer, module creator, or user of the engine (thanks Tom, for enumerating these), should walk down to get up to speed. Each time I visit the wiki to find a link to send to someone who has asked a question, or am searching for information myself, I realize how much information is either wrong or rather, what pearls are right are submerged deep in a sea of noise which a new visitor will have no idea how to swim to find what we are trying to tell them is important. I guess conciseness, clear direction, and accuracy are my main frustration. As a developer, I want to read a little as possible to get up to speed and when I don't know what is important, I trust only the important information will be presented, as a courtesy to me, to show value for my time. DM and I are the ones doing the server migration of services. I mentioned my frustration regarding the wiki to DM and Peter yesterday, pointing out the very first few lines, which I should understand as most important, were entirely misleading or irrelevant, giving a very bad impression. I asked if maybe the migration of the wiki from guest to host might be a good time to start fresh. Waking up this morning, it sounds like Peter ran with it-- which, given Peter's character to "just do it," I should have expected. I am grateful we have people who jump in and get things done, and I am also grateful we have people, like David, who have spent much of the their time curating many of the pages on the wiki, even when he admittedly was not an expert in their content. I accept that it is due to lack of participation from core and frontend developers on the wiki that it has become so unaccommodating for their kind. Let's please work together to make the wiki again useful for all those involved... and direct and concise, and not be offended when the sea is drained to reveal only the pearls. All here are loved and appreciated. Let's share in work together on this, Troy On 01/08/2018 08:06 AM, jhphx wrote: > For those that may not know, there are auto utilities to check > websites or lists of pages for broken links and then generate a nice > report on the nature of the bad links. That report could even be > posted, perhaps on its own page. > > Jerry > > On 1/8/2018 2:22 AM, David Haslam wrote: >> Dead links are a perennial problem. >> >> Thanks for the alert. >> >> Best regards, David >> >> >> Sent from ProtonMail Mobile >> >> >> On Mon, Jan 8, 2018 at 09:18, L'Africain <lafricai...@gmail.com >> <mailto:lafricai...@gmail.com>> wrote: >>> About the wiki, the link to the perl script to convert imp to osis >>> is dead. Le 08/01/2018 à 09:08, Peter von Kaehne a écrit : > On Mon, >>> 2018-01-08 at 07:40 +0000, Peter von Kaehne wrote: >> We are >>> currently engaging in a bit of culling and pruning activity. > >>> Project links: > > I am culling all Project pages on the wiki back >>> to the bare minimum - > it is not useful to duplicate info and make >>> new developers think that > the outdated info on our pages is all >>> there is. > > Please help by keeping contact details etc up date - >>> for your own > projects in particular (Project website, mailing >>> lists, source, covered > platforms) > > Peter > > >>> _______________________________________________ > sword-devel >>> mailing list: sword-devel@crosswire.org > >>> http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions >>> to unsubscribe/change your settings at above page >>> _______________________________________________ sword-devel mailing >>> list: sword-devel@crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel Instructions >>> to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
