[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
We never refer to our software as "open source" (see http://gnu.org/philosophy/open-source-misses-the-point.html) but a lot of your suggestions seem good to me. Here are some specific comments: We do have issue trackers that we use. > 4) Build a online testing tool > It would be awesome to have an online tool that could test any given > website against LibreJS standards. > Paste your URL, get the results. Is it possible to build such a thing using > NodeJS? We have a program to do this. It's called LibreJS. You install it in your browser, and you can check a site all by yourself. You can even check pages that are not yet posted on a site, or not publicly accessible. How would an "online testing tool" be different from this? And why would it be better? > 2) Weblabels first > Web labels is probably the easiest/fastest way to do it, and yet [2] only > kind of mentions it as "last resort" method, "if bandwidth is an issue". > I think describing how to do weblabels should be the first topic under > [Step 3: Adding license information] I think the reason we encourage webmasters to put the license and source pointer directly in the program is that this makes it easier for people looking at the page to find the source code. Does anyone recall the discussion about this? -- Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org www.gnu.org Skype: No way! That's nonfree (freedom-denying) software. Use Ekiga or an ordinary phone call.
