<div class="gmail_quote">2011/1/15 <span dir="ltr"><<a href="mailto:roeplay@lavabit.com">roeplay@lavabit.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">> 2011/1/15 <<a href="mailto:roeplay@lavabit.com">roeplay@lavabit.com</a>><br>
><br>
>> > Hi,<br>
>> ><br>
>> > For documentation writers<br>
>> > ==============<br>
>> > I just wanted to ask if it is really necessary to have the Roadmap<br>
page[1].<br>
>> > That page lists several tasks for Trisquel, the website and some<br>
suggestions<br>
>> > or feature requests. Why don't you use the issue tracker in the<br>
>> website?<br>
>> > It<br>
>> > has the functionality for that kind of items in the category field:<br>
>> bug<br>
>> > report, task, feature request, support request.<br>
>> ><br>
>> > For Spanish translators<br>
>> > ============<br>
>> > I want to contribute with translations but I'd like to know first the<br>
conventions you are using. For example, I've seen that in some pages<br>
>> you<br>
>> > use<br>
>> > "ustedeo"[2] but in others you use "tuteo"[3].<br>
>> ><br>
>> > Do you always translate developer documentation? Why? I think that<br>
development information should be kept in English only since almost<br>
>> every<br>
>> > aspect of development requires people involved in it to be able to<br>
communicate in that language.<br>
>> ><br>
>> ><br>
>> > Thanks in advance,<br>
>> ><br>
>> > 1. <a href="http://trisquel.info/en/wiki/roadmap" target="_blank">http://trisquel.info/en/wiki/roadmap</a><br>
>> > 2. <a href="http://trisquel.info/es/wiki/plan-de-trabajo" target="_blank">http://trisquel.info/es/wiki/plan-de-trabajo</a><br>
>> > 3. <a href="http://trisquel.info/es/wiki/manuales" target="_blank">http://trisquel.info/es/wiki/manuales</a><br>
>> ><br>
>> > --<br>
>> > Felipe Lopez<br>
>> > IntrosMedia <<a href="http://introsmedia.wordpress.com/" target="_blank">http://introsmedia.wordpress.com/</a>><br>
>> ><br>
>> > _______________________________________________<br>
>> > Trisquel-devel mailing list<br>
>> > <a href="mailto:Trisquel-devel@listas.trisquel.info">Trisquel-devel@listas.trisquel.info</a><br>
>> > <a href="http://listas.trisquel.info/mailman/listinfo/trisquel-devel" target="_blank">http://listas.trisquel.info/mailman/listinfo/trisquel-devel</a><br>
>> ><br>
>> ><br>
>> Let me try to answer the second inquiry:<br>
>> It's true that translating developer documentation like the roadmap<br>
page<br>
>> is of least priority. If you would like to translate wiki pages to<br>
Spanish, you can bypass those. But the vast majority of our<br>
>> documentation<br>
>> is not "developer documentation", but for users from novice to<br>
advanced.<br>
><br>
> Ok. I won't translate those.<br>
><br>
> There's one thing I'd like to add here. It's just my personal view, but I'd<br>
> like to hear your opinions, too.<br>
><br>
> I usually use the website playing two different roles: user and<br>
> contributor.<br>
> I'd like to find, easily, the documentation more relevant for each role.<br>
For<br>
> example, if I could modify the website, I'd add a new link to the<br>
header,<br>
> a<br>
> "Contribute" button. This way I could link the "Documentation" button to<br>
a<br>
> page listing the available user manuals for each version of the distro<br>
and<br>
> the "Contribute" button to a page describing the Trisquel Team and how<br>
to<br>
> join and help with programming, documentation, translation, etc. In<br>
short,<br>
> I'd like to see the user documentation separated from the contributors<br>
documentation.<br>
><br>
> I think this could help organize better each Team as well.<br>
><br>
<br>
</div></div>Maybe it isn't necessary to separate the two. You'll notice that almost<br>
all of the wiki pages are written for users, very few just for developers.<br>
The few that are only for developers (like the Design page) are not filed<br>
under "documentation" in the wiki hierarchy. The Roadmap page is kind of a<br>
borderline case. It is really for both users (at least, the more<br>
interested ones) and developers. Even the Design page is for users in a<br>
way (e.g. anyone can add to that page if they want), because we have a<br>
very open community.<br>
<div class="im"><br>
><br>
>> If you would like to contribute regularly (instead of just<br>
occasionally)<br>
>> to the translation of the website into Spanish, maybe you would like to be<br>
>> added to the Trisquel team?<br>
(<a href="http://trisquel.info/en/wiki/trisquel-team" target="_blank">http://trisquel.info/en/wiki/trisquel-team</a>)<br>
> I can contribute about 8 hours weekly. If that's enough, then yes.<br>
><br>
> P.D.: AndrewT, thanks for correcting the Japanese how-to.<br>
><br>
> --<br>
> Luis Felipe López Acevedo<br>
</div><div class="im">> IntrosMedia <<a href="http://introsmedia.wordpress.com/" target="_blank">http://introsmedia.wordpress.com/</a>><br>
><br>
> _______________________________________________<br>
> Trisquel-devel mailing list<br>
> <a href="mailto:Trisquel-devel@listas.trisquel.info">Trisquel-devel@listas.trisquel.info</a><br>
> <a href="http://listas.trisquel.info/mailman/listinfo/trisquel-devel" target="_blank">http://listas.trisquel.info/mailman/listinfo/trisquel-devel</a><br>
><br>
><br>
<br>
</div>8 hours a week is plenty. Since he is generally pretty busy, it might be a<br>
couple more days until Ruben sees this email and gets around to adding<br>
you. Since you've been a long-time member of the community and contributed<br>
much already, I'll just make the reasonable assumption that Ruben wants<br>
you on the team and go ahead and add you to that page. Welcome to the<br>
Team!<br>
<br>
And I found your iBus how-to very helpful! Good work!<br>
<br>
--AndrewT<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br>Ok, thanks.<br><br>-- <br></div></div>Luis Felipe López Acevedo<br><a href="http://introsmedia.wordpress.com/" target="_blank">IntrosMedia</a><br><br>