Re: [OpenOCD-devel] Offer for website
Hi David, I think you missed my most recent mails about this subject. I now fully understand the hesitation to rely on javascript for static content generation. No more need to convince me ;-) Kind regards, Kristof Mulier - Oorspronkelijk bericht - Van: "David Riley" Aan: "kristof mulier" Cc: "Paul Fertser" , "openocd-devel" Verzonden: Zondag 25 oktober 2020 14:55:09 Onderwerp: Re: [OpenOCD-devel] Offer for website On Oct 24, 2020, at 9:40 AM, kristof.mul...@telenet.be wrote: > > Hi Paul, > I think I get the point now. You are blocking javascript, > are you? > > Yes, Johan's website makes use of javascript to generate > the menu and load the content pages. So if you block > javascript, it won't work. > > I don't think this is an issue. All modern browsers can > handle javascript. It is an issue for many people who do not allow javascript to run unless explicitly trusted. - Dave ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On Oct 24, 2020, at 9:44 AM, Andrzej Telszewski wrote: > > Hi, > > I would like to let you know about: > > - [Hugo](https://gohugo.io/) > - [Jekyll](https://jekyllrb.com/) > > These are static websites generators. > What is very attractive for me is that the website can be written using > *Markdown*. > I must confess that I haven't tried any of them, but recently I started being > interested in *Markdown* proper. > And as I aim to center everything around *Markdown*, I came across *Hugo* and > *Jekyll*. I'd put in a vote for Jekyll. It's pretty easy to use and customize, and it's popular and well-supported (Github uses it for Pages, among other things). Plus, since the content is written in Markdown, it means the documentation is generally readable as plain text as well. - Dave ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On Oct 24, 2020, at 9:40 AM, kristof.mul...@telenet.be wrote: > > Hi Paul, > I think I get the point now. You are blocking javascript, > are you? > > Yes, Johan's website makes use of javascript to generate > the menu and load the content pages. So if you block > javascript, it won't work. > > I don't think this is an issue. All modern browsers can > handle javascript. It is an issue for many people who do not allow javascript to run unless explicitly trusted. - Dave ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
> On 25 Oct 2020, at 11:23, Johan Cockx wrote: > > Two possible purposes I have read are > - a blog for announcements > - online documentation Jekyll conveniently supports both blog style posts (ordered by date) and regular pages. Regards, Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
> On 24 Oct 2020, at 16:44, Andrzej Telszewski wrote: > > - [Jekyll](https://jekyllrb.com/) > These are static websites generators. That's correct. I started using static sites generated by Jekyll several years ago, and now all my websites (Eclipse Embedded CDT, xPacks, µOS++) are Jekyll based. > What is very attractive for me is that the website can be written using > *Markdown*. > I must confess that I haven't tried any of them, but recently I started being > interested in *Markdown* proper. > And as I aim to center everything around *Markdown*, ... I think that this is a very good choice. Writing all pages in markdown is very, very convenient. For my sites the conversion from markdown to html is done automatically by some CI jobs, so it is transparent, no need to worry. Highly recommended. Liviu ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hello. I am Johan, Kristof's colleague and co-founder of Embeetle. Beetle relies heavily on OpenOCD, so I am very grateful for the work done by the OpenOCD community. Regarding the website, my first question is: what is the purpose of the website? All other decisions should be secondary and should serve that purpose. Previous remarks in this thread include: "a new look/design for the OpenOCD website", "The current one looks quite ugly and old.", "We should also update the website to httpS" and "The current hosting platform is not always very stable". That in itself is not enough to warrant the effort to design a new website, as long as it serves its purpose. OpenOCD is not about cosmetics, it is about functionality. Adding httpS or switching to another hosting platform can be done without changing the content. Two possible purposes I have read are - a blog for announcements - online documentation Are these purposes sufficiently served by the current website? If not, where/how is it lacking? What other purposes should it serve? If these purposes can be well served without javascript, then I see no good reason to use javascript on the OpenOCD website, and some very good reasons not to use it. Most of them have been mentioned before in this thread. On the Embeetle website, I used javascript because: 1. It don't want to reload the menu and other fixed parts of the website when switching to another page (faster, limit data bandwidth/usage) 2. Some features like popup notes and foldable sections are hard to implement without javascript 3. We want to understand how our website is used without resorting to Google Analytics and without compromising privacy in any way. I experimented with Matomo (open source alternative) but didn't like it: too complex, I don't understand how it works (unless I spend a lot of time, which I don't have). The total amount of javascript code used on the Embeetle site is less than 1200 lines. It is not minified. It uses *no* external frameworks, not even jQuery. I will add an open source license. The above arguments are for Embeetle and do not necessarily apply to OpenOCD. Johan -- Johan Cockx - Embeetle bv - https://embeetle.com - jo...@embeetle.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On 25/10/20 5:39 pm, kristof.mul...@telenet.be wrote: > This of course throws a new question in the group: do > you (OpenOCD developers) like the style - the "look and > feel" - of our website (https://embeetle.com)? Well, I'll point out that I'm just one of the users of OpenOCD, not a developer. Above all features a website should have, it should work. Looking nice is pretty useless if the site doesn't achieve its aim of disseminating information. There's definitely been a "fashion trend" for single-page-application style websites being used in place of more traditional server-side-rendered sites. I think it's wise to critically ask: "do I really need to do it this way?" If something is likely to change on the page after the user initially loads it, sure, use a framework that lets you do the DOM-twiddling needed. I'm thankful we've moved beyond the bad old days of two ways of doing things in early 21st century DHTML. That said, most of these frameworks are huge. Wherever the OpenOCD website gets hosted, there's an Internet quota to consider. For a quota of finite size: a trebling of the page's download size means we can support one third of the page views in a month before the web host starts charging for over-quota usage. Add to this the code safety concerns, and the argument for complex client-side rendering quickly becomes frivolous. > You said: >> "[..] bit hard to make a browser-based development >> environment without some sort of client-side code >> executing, whether it be JavaScript, Adobe Flash, >> Sun Java applets, etc." > Embeetle is not a browser-based IDE. It's a desktop > application intended for Linux and Windows. Is there > something about the homepage that made you think our > IDE is browser-based? Ahh right, I did have a brief look at the documentation but didn't bother downloading as it didn't serve a use case I needed. I had assumed that the reason the website needed lots of scripts enabled was because it did it all in the browser. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hi Stuart,
ABOUT THE WEBSITE
=
You have a point. Yesterday, Johan and I talked about
this, and we fully understand the hesitation you and
other OpenOCD members feel about a javascript-based
website (in the sense that javascript is responsible
for showing static content). Johan told me:
> "It is perfectly possible to create a fully static
> website without javascript, but with a similar menu
> to ours."
This of course throws a new question in the group: do
you (OpenOCD developers) like the style - the "look and
feel" - of our website (https://embeetle.com)?
Johan will join the OpenOCD mailing list after the
weekend to join the discussions. He looks forward to
help out with the webdesign. It's one of the many
things he's very good at :-)
ABOUT EMBEETLE IDE
==
You said:
> "[..] bit hard to make a browser-based development
> environment without some sort of client-side code
> executing, whether it be JavaScript, Adobe Flash,
> Sun Java applets, etc."
Embeetle is not a browser-based IDE. It's a desktop
application intended for Linux and Windows. Is there
something about the homepage that made you think our
IDE is browser-based? If yes, that means we made a
mistake in our "communication strategy". Please tell
us, so we can make the appropriate changes ^_^
Kind regards,
Kristof Mulier
- Oorspronkelijk bericht -
Van: "Stuart Longland (VK4MSL)"
Aan: "openocd-devel"
Verzonden: Zondag 25 oktober 2020 00:32:48
Onderwerp: Re: [OpenOCD-devel] Offer for website
On 24/10/20 11:40 pm, kristof.mul...@telenet.be wrote:
> I don't think this is an issue. All modern browsers can
> handle javascript.
Yes, most modern browsers can execute JavaScript.
Do you want your browser to execute ${WEBSITE}'s JavaScript?
Do you have the time to review the minified JavaScript code that website
calls up to see if it is safe?
Do you have the expertise to conduct such a review?
I'm fine with JavaScript on a site that actually requires it to
accomplish the task it is designed for. These are called client-side
web applications. They're not simple web pages. Embeetle's own service
would be a good example here: bit hard to make a browser-based
development environment without some sort of client-side code executing,
whether it be JavaScript, Adobe Flash, Sun Java applets, etc.
Pages where the content is updated "live", sure, JavaScript all the way.
Rendering *static* menus and text on a page is not a job that JavaScript
is required for. It's a bg attack surface for little benefit.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On 24/10/20 11:40 pm, kristof.mul...@telenet.be wrote:
> I don't think this is an issue. All modern browsers can
> handle javascript.
Yes, most modern browsers can execute JavaScript.
Do you want your browser to execute ${WEBSITE}'s JavaScript?
Do you have the time to review the minified JavaScript code that website
calls up to see if it is safe?
Do you have the expertise to conduct such a review?
I'm fine with JavaScript on a site that actually requires it to
accomplish the task it is designed for. These are called client-side
web applications. They're not simple web pages. Embeetle's own service
would be a good example here: bit hard to make a browser-based
development environment without some sort of client-side code executing,
whether it be JavaScript, Adobe Flash, Sun Java applets, etc.
Pages where the content is updated "live", sure, JavaScript all the way.
Rendering *static* menus and text on a page is not a job that JavaScript
is required for. It's a bg attack surface for little benefit.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
signature.asc
Description: OpenPGP digital signature
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On Sat, Oct 24, 2020 at 03:40:30PM +0200, kristof.mul...@telenet.be wrote: > I think I get the point now. You are blocking javascript, > are you? Of course I am. I guess we just have to disagree there. I want to have access to structured information with semantic markup with hyperlinks, not to turn my computer into an inefficient thin client running a VM with some code controlled by the remote party. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On 24.10.20 15:28, Paul Fertser wrote: > My colleague Johan designed a simple, elegant javascript-css skeleton >> that we based our website on: >> [1]https://embeetle.com > I'm attaching a screenshot and that fully expresses my personal > opinion about this idea. Full ACK from me - it looks the same on my browser. While I do applaud the idea of donating a new look/design for the OpenOCD website, the requirement of javascript to display static content is a no-go for me. I'd rather have an somewhat old-style site that I can read with any browser without fiddling with the settings and thinking "do I trust this site enough to allow their code to run on my side". cu Michael ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On Sat, Oct 24, 2020 at 03:37:48PM +0200, kristof.mul...@telenet.be wrote: > I don't understand the message you want to convey > with your screenshot. It looks like the website > fails to load in your browser, right? I'm not sure if "fails to load" would be the accurate description but the fact is the result seems to be unusable. > I don't know when you took this screenshot. Just prior to posting. It looks exactly the same right at the moment. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hi, I would like to let you know about: - [Hugo](https://gohugo.io/) - [Jekyll](https://jekyllrb.com/) These are static websites generators. What is very attractive for me is that the website can be written using *Markdown*. I must confess that I haven't tried any of them, but recently I started being interested in *Markdown* proper. And as I aim to center everything around *Markdown*, I came across *Hugo* and *Jekyll*. On 24/10/2020 15:16, kristof.mul...@telenet.be wrote: "https is not a problem, thanks to letsencrypt. I can set it up (for free) if it is hosted on my server. All they would need to do is point a DNS record for their domain (or a subdomain like new.openocd.org to experiment) to my server at 213.136.92.230" For experimentation that's fine. But for the final implementation, I vote against. Although I'm not a part of OpenOCD, my suggestion is that the whole infrastructure is in the hands of OpenOCD *owners*. But that does not prevent *Johan* becoming part of OpenOCD and with an agreement, keeping part of the infrastructure on his personal services. And yes, the website really needs a bit of refinement. ;-) I wish you all the best! -- Best regards, Andrzej Telszewski ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
On Sat, Oct 24, 2020 at 03:16:39PM +0200, kristof.mul...@telenet.be wrote: > "https is not a problem, thanks to letsencrypt. I can > set it up (for free) if it is hosted on my server. All > they would need to do is point a DNS record for their > domain (or a subdomain like new.openocd.org to experiment) > to my server at 213.136.92.230" Currently the website is hosted on SF.net. It's certainly less stable than we'd like it to, but probably not too bad. SF.net allows us to use HTTPS, just nobody bothered with it yet. I'm not sure what's better: to self-host the website or to let it stay at SF.net but I would prefer to not depend on Embeetle company for hosting because I'm afraid it might complicate things in the long run. Just my personal opinion. Another thing to decide would be what exactly OpenOCD project needs a website for. Current one allows to share the news, including links to success stories or interesting related conference talks. Current one allows to host a copy of online documentation. What else is needed? > a zoom/skype meeting ... -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hi Paul, I think I get the point now. You are blocking javascript, are you? Yes, Johan's website makes use of javascript to generate the menu and load the content pages. So if you block javascript, it won't work. I don't think this is an issue. All modern browsers can handle javascript. Kind regards, Kristof Mulier - Oorspronkelijk bericht - Van: "Paul Fertser" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Zaterdag 24 oktober 2020 15:28:17 Onderwerp: Re: [OpenOCD-devel] Offer for website Hey Kristof, On Fri, Oct 23, 2020 at 01:07:57PM +0200, kristof.mul...@telenet.be wrote: > My colleague Johan designed a simple, elegant javascript-css skeleton > that we based our website on: > [1]https://embeetle.com I'm attaching a screenshot and that fully expresses my personal opinion about this idea. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hi Paul, I don't understand the message you want to convey with your screenshot. It looks like the website fails to load in your browser, right? I don't know when you took this screenshot. The website has been unstable some days ago because Johan was doing experiments on it. Please let me know if it works now. Kind regards, Kristof Mulier - Oorspronkelijk bericht - Van: "Paul Fertser" Aan: "kristof mulier" Cc: "openocd-devel" Verzonden: Zaterdag 24 oktober 2020 15:28:17 Onderwerp: Re: [OpenOCD-devel] Offer for website Hey Kristof, On Fri, Oct 23, 2020 at 01:07:57PM +0200, kristof.mul...@telenet.be wrote: > My colleague Johan designed a simple, elegant javascript-css skeleton > that we based our website on: > [1]https://embeetle.com I'm attaching a screenshot and that fully expresses my personal opinion about this idea. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hey Kristof, On Fri, Oct 23, 2020 at 01:07:57PM +0200, kristof.mul...@telenet.be wrote: > My colleague Johan designed a simple, elegant javascript-css skeleton > that we based our website on: > [1]https://embeetle.com I'm attaching a screenshot and that fully expresses my personal opinion about this idea. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
Re: [OpenOCD-devel] Offer for website
Hi Marc, Thank you for your reply. ABOUT THE WEBSITE = I can reassure you - Johan's websites are NOT Wordpress-based. Our first Embeetle website was made in Wordpress, but there were too many problems. So we decided to throw Wordpress in the bin and start from scratch. Johan designed a clean website structure that all of us (Embeetle developers) can easily add content to. Personally, I'm not versed in web development - so I was happy my Embeetle colleague Johan took this task on his shoulders. Once he finished the backend, I just needed HTML and some basic CSS to add new pages. Each new page appears automatically in the menu on the left (Johan's backend takes care of that). I just talked to Johan, and we have the following questions: - Do you (OpenOCD developers) have basic HTML knowledge to add content that way? Or would you prefer some kind of markup system? - If you're worried it would be hard to add content to the website, Johan can make an admin page where you can add a new page directly in the browser. The admin page would provide a basic editor in which you can enter the HTML for the new page (or edit HTML of an existing page). - Johan's website structure is NOT a blog. A blog is typically less organized than a hierarchical menu. Do you (OpenOCD developers) prefer a blog or a website? If you prefer a website, we can offer one in the same style and structure as ours (https://embeetle.com). ABOUT NIKOLA This looks interesting indeed. However, neither me, nor my colleague Johan knows the Nikola framework. It would take us quite some time to get used to it. We'll look into it and give some feedback later. ABOUT HTTPS === I asked Johan about https, and he replied: "https is not a problem, thanks to letsencrypt. I can set it up (for free) if it is hosted on my server. All they would need to do is point a DNS record for their domain (or a subdomain like new.openocd.org to experiment) to my server at 213.136.92.230" Why don't we setup a zoom/skype meeting to talk these things through? To have a successfull meeting, we should certainly invite the OpenOCD developers that are involved in the website. But I have no idea who that is? Kind regards, Kristof Mulier - Oorspronkelijk bericht - Van: "dev" Aan: "kristof mulier" , "openocd-devel" Verzonden: Vrijdag 23 oktober 2020 20:01:13 Onderwerp: Re: [OpenOCD-devel] Offer for website Hi Kristof, I would love to see a new website on openocd.org. The current one looks quite ugly and old. However, personally I would prefer to have a blog-like website as the current one. It's easier to publish new content. To reduce maintenance (security updates etc.) I would rather use a static website like Nikola [1] than WordPress. We should also update the website to httpS... Any opinions on that? Best regards, Marc [1] https://getnikola.com/ On Fri, 2020-10-23 at 13:07 +0200, kristof.mul...@telenet.be wrote: > Dear OpenOCD developers, > > We use OpenOCD in the Embeetle IDE. We are grateful for this free > software, and also for the countless times you have helped us to > fix certain problems. Although we didn’t contribute to the source > code itself (yet), we feel part of the OpenOCD community. > > We’d like to do something back, something bigger than just drawing > a logo. We had a great idea that we’d like to share with you. > > THE IDEA > > My colleague Johan designed a simple, elegant javascript-css skeleton > that we based our website on: > https://embeetle.com > > On the same skeleton, we also built this website: > https://qscintilla.com > > And I use it for my personal consultancy-website: > https://chipdesk.com > > What do you think about giving OpenOCD a new look? Johan would > like to send you the javascript-css code and he is happy to help > with the practical implementations. > > Maybe the new OpenOCD version being released soon (see mail from > @Paul Fertsen) is the perfect moment for this ^_^. Once implemented, > users can download the new version on the download page of the new > OpenOCD website. > > EXTRA CONTENT > = > We have some nice content on our Embeetle website about OpenOCD: > https://embeetle.com/#embedded-dev/software/dev-tools/flash/basics > > And here [not yet ready]: > https://embeetle.com/#embeetle-ide/troubleshoot/flash > > And this [build instructions]: > https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build > > We plan to write more pages in the future. It would be nice to > add similar content to the OpenOCD website. Of course - we’d only > add content to a test-version of the website, so you (the OpenOCD > developers) can first check it before pushing anythi
Re: [OpenOCD-devel] Offer for website
Hi Kristof, I would love to see a new website on openocd.org. The current one looks quite ugly and old. However, personally I would prefer to have a blog-like website as the current one. It's easier to publish new content. To reduce maintenance (security updates etc.) I would rather use a static website like Nikola [1] than WordPress. We should also update the website to httpS... Any opinions on that? Best regards, Marc [1] https://getnikola.com/ On Fri, 2020-10-23 at 13:07 +0200, kristof.mul...@telenet.be wrote: > Dear OpenOCD developers, > > We use OpenOCD in the Embeetle IDE. We are grateful for this free > software, and also for the countless times you have helped us to > fix certain problems. Although we didn’t contribute to the source > code itself (yet), we feel part of the OpenOCD community. > > We’d like to do something back, something bigger than just drawing > a logo. We had a great idea that we’d like to share with you. > > THE IDEA > > My colleague Johan designed a simple, elegant javascript-css skeleton > that we based our website on: > https://embeetle.com > > On the same skeleton, we also built this website: > https://qscintilla.com > > And I use it for my personal consultancy-website: > https://chipdesk.com > > What do you think about giving OpenOCD a new look? Johan would > like to send you the javascript-css code and he is happy to help > with the practical implementations. > > Maybe the new OpenOCD version being released soon (see mail from > @Paul Fertsen) is the perfect moment for this ^_^. Once implemented, > users can download the new version on the download page of the new > OpenOCD website. > > EXTRA CONTENT > = > We have some nice content on our Embeetle website about OpenOCD: > https://embeetle.com/#embedded-dev/software/dev-tools/flash/basics > > And here [not yet ready]: > https://embeetle.com/#embeetle-ide/troubleshoot/flash > > And this [build instructions]: > https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build > > We plan to write more pages in the future. It would be nice to > add similar content to the OpenOCD website. Of course - we’d only > add content to a test-version of the website, so you (the OpenOCD > developers) can first check it before pushing anything to the public > website. > > SOME FINAL THOUGHTS > === > If you like this idea, would you like to have a meeting to discuss > it further? We could hold a zoom meeting / skype / ... > > Kind regards, > Kristof Mulier > ___ > OpenOCD-devel mailing list > OpenOCD-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openocd-devel ___ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
