[KDE-India] A newbie

[Deep Laxman Sukhwani]

Thanks so much.

 I agree with you on self learning part when trying to submit first patch.

Look forward to talk to you guys further once I start working on bugs.

Regards

On Monday, 24 February 2014, Shantanu Tushar Jha <shantanu at kde.org> wrote:

> I forgot to answer the VM question. If your host OS is 64-bit, I suggest
> you install Kubuntu 64-bit and 32bit if the host is 32bit.
>
>
> On Mon, Feb 24, 2014 at 12:58 PM, Shantanu Tushar Jha <shantanu at kde.org>wrote:
>
> Hi Deep,
>
> Thanks for your email, nice to hear from you! Also good to know that you
> found Qt/KDE interesting enough that you want to contribute. In fact, if
> you talk around, we have lots of people in KDE who aren't necessarily from
> CS backgrounds, it really doesn't matter :) Also, usually starting with
> bugfixes is a great idea, you should use few applications and see if you
> can fix bugs in them.
>
> Around the suggestions you had, we've had that idea and have tried it but
> the sheer lack of infrastructure (good Internet, for example) makes it very
> difficult. Add the huge number of attendees and it becomes even harder to
> manage (if you remember how difficult it was to just do Qt basics workshop
> on Friday). So, we continuously strive to do such workshops, maybe we will
> have one day :) Still, the things you mentioned are something a
> self-motivated person (like you) will figure out pretty easily. Also, I
> personally took few weeks to put my first patch, but during those few weeks
> I learned what I would've never if somebody just told me the steps. So I
> think its pretty important for this to come by self-motivation rather than
> a formal instructor.
>
> As always, feel free to ask questions when you get stuck :)
>
> Cheers,
>
>
> On Sat, Feb 22, 2014 at 8:56 PM, Deep Laxman Sukhwani <
> deepsukhwani at gmail.com> wrote:
>
> Hello all,
>
> I have been attending this years KDE conference and I must say it is truly
> an amazing experience and the amount and kind of information shared by
> fellow speakers is of utmost value.
>
> I am too looking to begin contributing to KDE community, however so far I
> have learnt some Python through some CS courses online on sites like
> Coursera / Udacity and been involved in learning some JavaScript (mainly
> due to work related stuff). I work as a Testing Engineer for Musikaar
> Software, Ahmedabad.
>
> By qualification, I do not have any computer science qualifications, in
> fact I am qualified Chartered Accountant, however I am really keen on
> contributing to open source and after learning about Qt and its vast
> capabilities, I really want to get into more depth of it. I know a bit of
> C++, however I am still learning advanced C++ topics via online tutorials.
> Can you guide me if it is the right approach to complete some set of C++
> tutorials (like through learncpp.com) and jump straight to Qt and try to
> work on junior jobs or start observing bugs and see how I can contribute?
>
> Also, I have Mac as primary operating system and Ubuntu in virtual
> environment, I would like to install Kubuntu as per your recommendation,
> just a small doubt, should I proceed with 32-bit or 64-bit installation of
> Kubuntu 13.10? Reason I thought I would ask this is you guys are really
> experienced and you know ins and outs of what all problems can beginners
> like myself face. So just needed some guidance from you.
>
> --------------------------------------------------------------------
>
> Apart from this, I just wanted to put a general suggestion for a hands on
> workshop in this or upcoming KDE Conference: It would be awesome if someone
> could make us go through complete process right from the beginning to start
> contributing to KDE community, like one of the speakers said today it took
> him almost 9 months to submit his first patch. So say for example someone
> could tell us process may be in a format similar to like this:
>
>
>    - Signing up on KDE to be able to submit patches
>    - Writing first set of code
>    - Checking if there are any bugs reported for the patch that we are
>    about to submit
>    - If there is not any bug, we can file a bug for it ourselves to keep
>    track on it.
>    - Then the process to commit / check-in our created patches and how to
>    submit them.
>    - Then attach to the relevant bugs our commit ids through which we are
>    committing patches so that we can easily track progress.
>
> Of course this is just a sample process flow I was recommending.
>
>

-- 
--
Regards
Deep L Sukhwani
Mob: +91 9687 000 830 / +91 75036 10708
Website: My Blog Address <http://deepisblogging.blogspot.com/> / My Coding
Experiences <http://www.hauteclass.wordpress.com/>
GitHub Gist <https://gist.github.com/ProProgrammer/> |
@deepsukhwani<http://www.twitter.com/deepsukhwani>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-india/attachments/20140224/0f24ad54/attachment.html>