Hi,
On 15 Aug 2019, at 21:51, Jon Murphy jcmurphy26@gmail.com wrote:
I have asked for feedback and I got little. I do not think that many open points were left that could have easily been implemented. This is why I wasn’t too happy to read this email now, because I would have preferred some constructive ideas and help over this now.
You are a tough person to send feedback to. You have a tendency to react in off-putting ways. Re-read your response.
You did receive my constructive ideas in the Documentation list.
I told you why those are not possible to be implemented.
First of all: There is no time to work on this. I have been doing nothing else but infrastructure and admin work around the project for the last four weeks. I am barely able to respond to my email. One emergency after the other is happening and I am doing “quick and dirty” on more things than I would like to. Bare this in mind. This is also the reason why I am a bit on the edge.
How can I help?
Since I’m not a firewall expert, I help with documentation (I started working on the old wiki near April 2018)
Writing documentation is very helpful.
False information is worse than none.
Sorry to say but you’ll have to point those out (I know you are busy!). I’m not an expert but I have been going through and correcting what I can. I don’t have the skills to identify false info.
Okay, I will put this on my list.
From the top of my mind I know that we have some add-ons on the wiki that we have dropped a long time ago. Some of those pages have a note that the feature has been dropped. I think there is no reason to keep those pages.
Did the https://github.com/benweet/stackedit.js not work?
This project hasn’t been updated in years. I am not going to integrate legacy software into something new.
Sorry for dwelling on this (and I’m not trying to make you mad): To my unskilled eyes it looks like it was updated in Aug 2018. I saw your concern about PageDown but there is not a Pagedown reference in the JS code. On the webpage it states "stackedit.js is lightweight and has no dependency.” (I wrote a note to the developer to confirm). I am missing something obvious…
Stackedit.js is not an option at all. It just embeds an iframe and loads load of stuff from the Internet.
I do not want to send any user content to an untrusted third party. We also have infrastructure documentation in this wiki and nobody needs to know this. They even log for which page you are sending a request. Madness that it isn’t even documented anywhere.
So I wrote something lightweight and easy in less than 200 lines of JS code (could be 50 lines without comments, etc.). It has the following features:
* You can highlight text and then mark it as bold, italic, code or make a headline or link out of it * You can use keyboard shortcuts which I find very neat, because you don’t have to move your hands away from your keyboard. Hover over the icons to see the shortcuts.
Let me know if I forgot anything.
There is also a link to the “files” section now so that you can upload images with a few clicks only.
I only tested this in Safari and FF. So there might be problems with other browsers. IE? No idea. Feedback is of course appreciated.
I am also quite frustrated about seeing loads of HTML .... This is not how this was intended and we have talked about why this is a bad idea.
What should I correct? The HTML I remember is:
<color blue> Example </color> to <span style=“color:blue”> Example </span>
I believe I wrote to you asking for guidance and did not receive a response.
Please do not use *any* HTML.
Please do not use any colours. They create barriers for people who cannot see them.
Keep in mind, pages that look like this —> https://wiki.ipfire.org/hardware/arm?revision=2019-08-06T13:57:34.868460
Will now look like this —> https://wiki.ipfire.org/hardware/arm?revision=2019-01-09T19:34:43
Yes, I am aware of that. The page can be organised in a different way so it does not rely on those colours.
I’m sure you realize this is an uphill battle. Especially since users are allowed/encouraged to update wiki pages. Without the code to limit or exclude HTML you’ll become the wiki cop and continue to be frustrated by non-compliance. This doesn’t seem worth your time.
I am not fighting any battles here. In case someone turns against our mission that is a serious problem. We can have an argument, that is something totally different.
Users are very much encouraged to update the wiki. I think it could not be easier now. Nobody needs to have any skill apart from word.
Writing some markup syntax is in the nature of a wiki (see Wikipedia) and it works.
I am also quite frustrated about ... only the word “update” in the change log.
Look at the revisions for a single page. You see many proper remarks. The “Update” is normally a quick change where I got frustrated fighting the interface to get a page completed. My bad. I will do better.
No need to write a novel here. Three words can be enough. It just should be clear that the page has not only changed but what (and maybe why if it isn’t just some syntax stuff).
Again, none of this is meant to be mean. It just my feedback.
I didn’t take it like that. Please keep it coming.
Best, -Michael