> 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
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
>
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/bl
> 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 cas
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
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
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
