USB Bounty

If a programmer can’t work out how to edit a wiki page

Oh, well if it’s going to be that complicated…

:-)

If a programmer can’t work out how to edit a wiki page

Oh, I can edit a wiki page.

’’This’’? ’’’Here’’’? This is a wiki ‘’but it don’t speak wiki’’, it is a mish-mash of part MediaWiki and part Textile… (https://www.riscosopen.org/wiki/documentation/show/Wiki)

;-)

—~~~~

Of course if people want to ensure no duplication then you’re looking at someone spending time managing the new volunteers.

I refuse to be managed thank you.

How about having a list of “bugs” linked to in the wiki?
Not actually bugs though…
Or a combination of visio and project files that are uploaded and updated on a weekly basis, obviously with a nice PowerPoint presentation and a nice spreadsheet with pivot charts.

Or a combination of visio and project files that are uploaded and updated on a weekly basis, obviously with a nice PowerPoint presentation and a nice spreadsheet with pivot charts.

That needs a :-) or similar.
If I took it seriously I’d start imagining links to an office downstairs at work.
It’s close to the door in/out – some say it’s on the wrong side.

Might be one useful bit in your item: “updated on a weekly basis” just a status marker about whether anyone is doing anything.

If a programmer can’t work out how to edit a wiki page

Oh, well if it’s going to be that complicated…

:-)

Any non-programmer can edit a wiki page, so I agree ;-) However, in case we’re considering tabulated info, table markup under Textile could be described as “interesting”. So IMHO probably bullet points (which can be nested for claimants’ comments, etc.) would probably less of a hassle than tables… just my 2p for the mo.