valorie.zimmerman at gmail.com
Fri Aug 14 23:55:31 UTC 2015
Let me second Aaron's welcome. No matter what your talents, we can use them!
I personally use Konversation for IRC, but Quassel is good as well.
IRC is great for discussions and questions *right now* -- not so good
for longer discussions.
For those, and all official things we use the Kubuntu-devel list.
Finally, user help here on the Users list is always welcome.
All the best,
On Fri, Aug 14, 2015 at 2:26 AM, TuxMario DETREB
<tuxmario.detreb at gmail.com> wrote:
> Hello Valorie and Aaron
> I started using Quassel and reached the freenode #kubuntu-devel
> I'm using the pseudo "TuxMario"
> Is Quassel the recommended tool or do you recommend another one (Kopete,
> Konversation ...)?
> I joined kubuntu-devel list
> ( kubuntu-devel mailing list membership configuration for
> tuxmario.detreb at gmail.com, Mario ROGER)
> I apologize but I think I'm little bit stupid! I don't know
> how to introduce myself
> how to join kubuntu-tester (ing?)
> how to propose my contribution subjects
> Documentation review
> Packaging (I don't know Debian packaging but made few RPM for RedHat
> some years ago. May be Debian packages are not so different from RedHat
> ones' ?)
> Could I be useful for Kubuntu community ?
> Regards : Mario ROGER
> Le 06/07/2015 09:13, Valorie Zimmerman a écrit :
> On Thu, Jul 2, 2015 at 5:32 AM, TuxMario DETREB
> <tuxmario.detreb at gmail.com> wrote:
> Le 01/07/2015 08:10, Valorie Zimmerman a écrit :
> On Tue, Jun 30, 2015 at 2:19 PM, Felix Miata <mrmazda at earthlink.net> wrote:
> Billie Walsh composed on 2015-06-30 16:03 (UTC-0500):
> No critter likes "change". We all want things to remain just as they
> are, and always have been. The change from KDE3 to KDE4 meant that I had
> to learn to use a new piece of software.
> Some of us in older generations have learned to not fix what ain't broke,
> would like to see some respect from naive youth causing change. KDE upstream
> has at least twice discarded invested wealth by starting from scratch in
> order to institute perceived need to change. It's learned little from the
> wisdom that history provides.
> Many of the changes have come about because if there is no fix, it
> will *become* broken. Hardware changes, the kernel has to adapt, and
> software changes radiate out in all directions as a result. I wouldn't
> cast blame on the young, either -- some of us older folks create
> Kubuntu, and create KDE.
> We welcome all people of good will to help us build Kubuntu. If you
> want Kubuntu to continue to grow and thrive, consider contributing. We
> need people to test, to file bugs, to triage and fix those bugs, to
> package, write documentation, translate and internationalize, promote
> Kubuntu, plan meetings and gatherings, do artwork, and on and on. If
> you have time, we need YOU.
> Hello Valorie
> I like very much Kubuntu/KDE and I'm ready to help the project going
> Do you have some tutorial explaining how to start contributing?
> I think I could help for :
> Translation (I'm French)
> Basic testing
> NB : I'm not very available until end of august but after I could find free
> time for this activity
> Regards : Mario ROGER
> Hi Mario, what a lovely offer. Summer is indeed a chancy time for both
> developers and new volunteers. People are traveling or just away from
> their computers.
> Two things will help: if you can use IRC, please join #kubuntu-devel
> on Freenode, introduce yourself, and hang out there as much as
> possible. The more you read there, the more you see how we work
> Whether or not you use irc, please join the Kubuntu-devel list, and
> again, introduce yourself and what you might be interested in doing.
> Translations are always needed, although localization and
> internationalization for the software are done by either the KDE
> translation team or the Ubuntu translators for the most part.
> We do have a bit of our own software, and our documentation and
> important pages of our website that need translators. Documentation
> always needs fresh eyes, to check that text and screenshots are
> correct, and written as simply and accurately as possible.
> Every new Kubuntu and KDE release we need testing, of course. Ask to
> join the testing team, and you'll be added to the IRC "call for
> testers" which will ping you when something new comes up.
> And last, but certainly not least, we always need packagers. The more
> people learn packaging, the lighter the burden and faster we can get
> new stuff out to our users.
> To sum up: join #kubuntu-devel, and
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel and speak up!
> All the best,
More information about the kubuntu-users