Re: Breakout: how to attract new contributors?
> Maybe we don't just lack documentation. > > What kind of contributions are we expecting? It would be interesting > to have an outline of what kind of things we're interested in having > so people doesn't only contribute but also know confidently that > they're working in our direction. > > Aleix Hi Aleix I've read about the lack of sufficient test coverage for different multiscreen configurations. Problems with multiscreen is my biggest pain point with KDE Plasma since I started using Plasma with the upgrade to Fedora 22. Right now I'm building Plasma directly from KDE sources because it seems the delay bug I'm experiencing on the external monitor (see my message Plasma 5.7.5 / 5.8.0 multiscreen: Menu and widgets react to mouse events with seconds of delay if Primary Display = external monitor to plasma-devel) might get some attention if I can prove that it actually occurs in upstream code ... I'm willing to debug this problem, but I may need some guidance for running Plasma using the libraries that I build/install in my home directory. So ... I'm all for contributions that help making Plasma (and particularly multiscreen) more stable. Just my 10 cents ... Fredy Neeser IBM Zurich Research
Re: Breakout: how to attract new contributors?
On Mon, Oct 17, 2016 at 7:00 PM, Jonathan Riddell wrote: > we need more contributors, junior jobs are best way to get started > the most critical thing we can do for developer recruitment > is change the way we publish/blog > our blogs are mostly work notes aimed at users, we need to > write more blog posts that engineers like to read > mgraesslin: the interesting thing is that among the best and > brightest fresh young open source contributors, we have quite a few > users - e.g. in the Rust community quite a few use Plasma, because C++ > is the next best thing - but we don't publish anything they like to > read so we don't convert > > discuss! Maybe we don't just lack documentation. What kind of contributions are we expecting? It would be interesting to have an outline of what kind of things we're interested in having so people doesn't only contribute but also know confidently that they're working in our direction. Aleix
Re: Breakout: how to attract new contributors?
On Tuesday, October 18, 2016 11:24:00 AM UTC Marco Martin wrote: > On Monday 17 October 2016, Jonathan Riddell wrote: > > we need more contributors, junior jobs are best way to get > > > > started the most critical thing we can do for developer recruitment > > is change the way we publish/blog > > our blogs are mostly work notes aimed at users, we need to > > write more blog posts that engineers like to read > > mgraesslin: the interesting thing is that among the best and > > brightest fresh young open source contributors, we have quite a few > > users - e.g. in the Rust community quite a few use Plasma, because C++ > > is the next best thing - but we don't publish anything they like to > > read so we don't convert > > it's kind of a pipe dream, but indeed, great documentation would be one of > the most effective things That's the point of the developer guide which I've started, but haven't finished yet. I'll put some time aside to progress it. -- sebas Sebastian Kügler•http://vizZzion.org•http://www.kde.org
Re: Breakout: how to attract new contributors?
> I am one of those new contributors that I would like to help... :) > > It might be a very good thing a "per distribution" way to build plasma's > master branch and install it on a user's path (not global in order to > not break the distribution's official packages)... Very good idea. In my case, this would hopefully allow me to debug a new multiscreen issue ... There are some recent HOWTOs at [1] https://community.kde.org/Guidelines_and_HOWTOs [2] https://community.kde.org/Guidelines_and_HOWTOs/Development [3] https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source [4] https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Details [5] https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Plasma_5_on_Ubuntu_14.04_LTS but I don't know yet how useful [3]-[5] really are. > For example an analytic guide for some of the most used distributions, > Ubuntu, Fedora, openSUSE etc. > > I am using openSUSE and I would love to have a walk through to follow > for the first steps... I'm using Fedora -- yes, a walk through for building Plasma (ideally with distro-specific hints) would be greatly appreciated. Cheers Fredy Neeser IBM Zurich Research
Re: Breakout: how to attract new contributors?
Hello, I am one of those new contributors that I would like to help... :) It might be a very good thing a "per distribution" way to build plasma's master branch and install it on a user's path (not global in order to not break the distribution's official packages)... For example an analytic guide for some of the most used distributions, Ubuntu, Fedora, openSUSE etc. I am using openSUSE and I would love to have a walk through to follow for the first steps... regards, michail On 18/10/2016 12:24 μμ, Marco Martin wrote: On Monday 17 October 2016, Jonathan Riddell wrote: we need more contributors, junior jobs are best way to get started the most critical thing we can do for developer recruitment is change the way we publish/blog our blogs are mostly work notes aimed at users, we need to write more blog posts that engineers like to read mgraesslin: the interesting thing is that among the best and brightest fresh young open source contributors, we have quite a few users - e.g. in the Rust community quite a few use Plasma, because C++ is the next best thing - but we don't publish anything they like to read so we don't convert it's kind of a pipe dream, but indeed, great documentation would be one of the most effective things
Re: Breakout: how to attract new contributors?
On Monday 17 October 2016, Jonathan Riddell wrote: > we need more contributors, junior jobs are best way to get > started the most critical thing we can do for developer recruitment > is change the way we publish/blog > our blogs are mostly work notes aimed at users, we need to > write more blog posts that engineers like to read > mgraesslin: the interesting thing is that among the best and > brightest fresh young open source contributors, we have quite a few > users - e.g. in the Rust community quite a few use Plasma, because C++ > is the next best thing - but we don't publish anything they like to > read so we don't convert it's kind of a pipe dream, but indeed, great documentation would be one of the most effective things -- Marco Martin
