<pre>El Tue, 18 Jan 2011 22:42:32 -0600<br>Andrew Ter-Grigoryan <<a href="http://listas.trisquel.info/mailman/listinfo/trisquel-devel">roeplay en lavabit.com</a>> escribió:<br><br>><i> On Tue, 2011-01-18 at 18:47 -0800, SirGrant wrote:<br>
</i>><i> > Hey AndrewT,<br></i>><i> > <br></i>><i> > I was looking at the documentation and we have a good start. But I<br></i>><i> > notice a few issues. Firstly, it is starting to get unwieldy.<br>
</i>><i> > There is some content (e.g.<br></i>><i> > <a href="http://trisquel.info/en/wiki/how-configure-zte-mf626-3g-modem">http://trisquel.info/en/wiki/how-configure-zte-mf626-3g-modem</a>) that<br></i>><i> > isn't what I think we should have. Like with that example it isn't<br>
</i>><i> > our job to document how to get a modem how to work. It is the<br></i>><i> > people who make the modem's job to document that. Or it is a<br></i>><i> > question for the forum. (I know you didn't write that manual).<br>
</i>><i> <br></i>><i> For I while I have also thought the focus of that modem manual is just<br></i>><i> too narrow to merit inclusion. With all due respect to the writer of<br></i>><i> that manual, the choice of style for that manual needs a lot of<br>
</i>><i> improvement, parts are outdated (like the reference to Ali Gunduz's<br></i>><i> kernels), and it only applies to one specific model of hardware. For<br></i>><i> those reasons, I didn't include it in the table of contents. With that<br>
</i>><i> said, I wonder if Ruben be OK with deleting it?<br></i><br>Please don't!<br><br>We haven't deleted anything yet. Can you please give more information on why you don't want it deleted/changed. My opinion is it is too specific. There are millions of different pieces of hardware and we can't have articles on how to get each and every single one of them working. I think that article belongs more on a hardware site like <a href="http://www.h-node.com/">http://www.h-node.com/</a>. We were talking about just altering and changing it to something along the lines of "how to get your 3g modem working"<br>
</pre>