[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-quality
Subject: Re: contribution
From: "Jos Poortvliet" <jos () mijnkamer ! nl>
Date: 2007-08-20 10:35:20
Message-ID: 5c77e14b0708200335g3f8bb976r8f63b4f3f6496760 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 8/20/07, Jerry Penny <jpenny@lonetree.com> wrote:
> Hello,
>
> I read in KTip that there are many ways to contribute.
>
> I use KDE and would like to contribute.
That is great! Welcome to the KDE community ;-)
A place to start could be techbase: http://techbase.kde.org/Contribute
But it is mostly geared towards developers. Now, if you like, you could
update it with information for those NOT able or willing to write code. So
while you are searching for ways to contribute (like proofreading, as you
note), you can update techbase with pointers to how to contribute that way!
It would help others like you to start contributing as well.
Now for the proof-reading: I just happened to read the Commit Digest, the
weekly bulletin about 'what is going on in KDE development', and it
mentioned a developer asking for someone to proofread his documentation! So
that seems te be a good place to start.
Here is the link, you can try to google the name of the guy to contact him
about this:
http://commit-digest.org/issues/2007-08-19/moreinfo/700975/#changes
Another way to help with documentation is to contact your local translations
team. They might need some help as well. And you can choose a project you
like or are interested in, contact them and see if they need help for their
documentation. For example, if you want to help with Kolourpaint, Google it,
find the homepage, conact the authors/mailinglist and offer help.
There are many other ways to get involved, I'm sure others can fill you in
as well.
Have fun!
> I think that about the only thing that I might have to offer is
> proof-reading.
>
> How do I go about this?
>
> Thanks,
>
> Jerry
> _______________________________________________
> kde-quality mailing list
> kde-quality@kde.org
> https://mail.kde.org/mailman/listinfo/kde-quality
>
[Attachment #5 (text/html)]
<div><span class="gmail_quote">On 8/20/07, <b class="gmail_sendername">Jerry \
Penny</b> <<a href="mailto:jpenny@lonetree.com">jpenny@lonetree.com</a>> \
wrote:</span></div> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: \
0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>I read in KTip that \
there are many ways to contribute.<br><br>I use KDE and would like to contribute. \
</blockquote> <div> </div>
<div>That is great! Welcome to the KDE community ;-)</div>
<div> </div>
<div>A place to start could be techbase: <a \
href="http://techbase.kde.org/Contribute">http://techbase.kde.org/Contribute</a></div>
<div>But it is mostly geared towards developers. Now, if you like, you could update \
it with information for those NOT able or willing to write code. So while you are \
searching for ways to contribute (like proofreading, as you note), you can update \
techbase with pointers to how to contribute that way! It would help others like you \
to start contributing as well. </div>
<div> </div>
<div>Now for the proof-reading: I just happened to read the Commit Digest, the weekly \
bulletin about 'what is going on in KDE development', and it mentioned a \
developer asking for someone to proofread his documentation! So that seems te be a \
good place to start. </div>
<div>Here is the link, you can try to google the name of the guy to contact him about \
this:</div> <div><a href="http://commit-digest.org/issues/2007-08-19/moreinfo/700975/# \
changes">http://commit-digest.org/issues/2007-08-19/moreinfo/700975/#changes</a></div>
<div> </div>
<div>Another way to help with documentation is to contact your local translations \
team. They might need some help as well. And you can choose a project you like or are \
interested in, contact them and see if they need help for their documentation. For \
example, if you want to help with Kolourpaint, Google it, find the homepage, conact \
the authors/mailinglist and offer help. </div>
<div> </div>
<div>There are many other ways to get involved, I'm sure others can fill you in \
as well. </div> <div> </div>
<div>Have fun!</div>
<div> </div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid">I think that about the only thing that I might have to \
offer is proof-reading.<br><br>How do I go about this? \
<br><br>Thanks,<br><br>Jerry<br>_______________________________________________<br>kde-quality \
mailing list<br><a href="mailto:kde-quality@kde.org">kde-quality@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-quality"> \
https://mail.kde.org/mailman/listinfo/kde-quality</a><br></blockquote><br>
_______________________________________________
kde-quality mailing list
kde-quality@kde.org
https://mail.kde.org/mailman/listinfo/kde-quality
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic