From owner-freebsd-current@FreeBSD.ORG Wed Oct 29 16:04:43 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6511C32F for ; Wed, 29 Oct 2014 16:04:43 +0000 (UTC) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25F21E2D for ; Wed, 29 Oct 2014 16:04:42 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id tr6so3327223ieb.32 for ; Wed, 29 Oct 2014 09:04:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=webassign.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JIqT8nlbrphK3sI9MwqjRnrHiAbD2bNqW5jCQb3zWEU=; b=WK92Wq3LexuvbIYKP3PtaZ9Z4W25ViR/OKU+N4g7pzHyS8lxolTVogBNaDsStDRWQO RINY+OlqBi6Kx54MwIHHzre0Gnk23ZRsQH1ALfzECFuOX/asb31uz7oE3rASkU7crrBv JzetODCFEEPK3aPq9wGLdgPC8Owl6iRGtAWKg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=JIqT8nlbrphK3sI9MwqjRnrHiAbD2bNqW5jCQb3zWEU=; b=Y/rJfRWilJNrjZd55dtJU045nKnqWOwvUi/tcsLMbUhuDSOpF8LsQrVeUm8xfJSiPK EoQx8N8UCNwFsbalPQP0IRf+LsidXXE+4wUK5ZN9jGLL4BNuenDrdDaoX/S4DRFDjecY KBdKA5NzM86xlakaoEoLLIB7eWy1fww3hmFM2huYZGvCBMW4iVzXqwmRqY0EpnaloVKY wmTD7o4RkQZxQYQnZqBUdLdJhhJpbN0nkBu/q18k71VxXvUPFye0rKlOvxihtGwdtk0T OetGHRMDLWwnXNJklmdJpN9vqHDx+t7IAWCnR74b+f7tHUfTkzBRkskQalsFfx6vbXVt EfrA== X-Gm-Message-State: ALoCoQlQydP9BUh+lMz+F4xOANezEZfUApvaUO486zeaW5jK2IG0F+1DZKMGa1gMabJ1gCsJPFeO X-Received: by 10.50.4.4 with SMTP id g4mr13855993igg.22.1414598682307; Wed, 29 Oct 2014 09:04:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.240.116 with HTTP; Wed, 29 Oct 2014 09:04:21 -0700 (PDT) In-Reply-To: <201410291155.53950.jhb@freebsd.org> References: <20141025204536.GD19066@dft-labs.eu> <20141028221413.GF26796@ivaldir.etoilebsd.net> <201410291155.53950.jhb@freebsd.org> From: Hunter Satterwhite Date: Wed, 29 Oct 2014 12:04:21 -0400 Message-ID: Subject: Re: junior kernel tasks To: John Baldwin X-Mailman-Approved-At: Wed, 29 Oct 2014 16:19:40 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Baptiste Daroussin , Mateusz Guzik , "bugmeister@freebsd.org" , FreeBSD Hackers , Eitan Adler , freebsd-current Current , Marcus von Appen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 16:04:43 -0000 GitHub + Gitter? https://gitter.im/ On Wed, Oct 29, 2014 at 11:55 AM, John Baldwin wrote: > On Tuesday, October 28, 2014 7:07:31 pm Eitan Adler wrote: > > On 28 October 2014 15:14, Baptiste Daroussin wrote: > > > On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: > > >> > > >> Quoting John Baldwin : > > >> > > >> > On Saturday, October 25, 2014 4:45:36 pm Mateusz Guzik wrote: > > >> >> Hello, > > >> >> > > >> >> In short, nice kernel tasks people with C language skills can do > in few > > >> >> evenings. > > >> >> > > >> >> https://wiki.freebsd.org/JuniorJobs > > >> >> > > >> >> It is assumed you know how to obtain sources and build the kernel. > > >> >> > > >> >> What you can get in return: > > >> >> - your own code in FreeBSD tree > > >> >> - eternal glory [1] > > >> >> - fun [2] > > >> >> > > >> >> If you are not interested, but know someone who does, please pass > it > > >> >> down. > > >> >> > > >> >> [1] - not really, no > > >> >> [2] - well, I guess that's subjective, so that's not a "no" > > >> > > > >> > Even though our bugmeisters have decided that we should not have > wishlist > > >> > items in our bug tracker, I really wish we could store the various > idea lists > > >> > (we have several) in an issue tracker instead. This would allow > for folks to > > >> > comment on ideas, vote for them, etc. It would also make it easier > for more > > >> > people to submit new ideas. > > >> > > > >> > > >> Speaking not strictly with the bugmeister hat, but from experience, > please do > > >> not let us go down the road of (ab)using a bug tracking solution as > task and > > >> idea management system. I think that using the tasks feature of > phabricator > > >> (our reviews instance) would provide better workflow support for > those things, > > >> starting out from sketching out rough ideas, discussing them, > breaking them up > > >> in seperate tasks (linked to and dependent on each other) and > collaborating > > >> on them (take a look at https://developer.blender.org/T42339 for a > > >> brief example). > > >> > > >> Having said this, let's keep the bug tracker a bug tracker. > > >> > > >> Cheers > > >> Marcus > > > > > > I disabled the tasks on phabricator to avoid having it a duplicate of > bugzilla, > > > but if we have a use for it I can activate it! > > > > > > Actually I do like the idea of the bug tracker aka bugzilla being only > for bugs > > > and uxe phabricator for tracking the tasks > > > > having disparate trackers for "wishlist" and "bugs" is quite harmful > > and splits the conversations. It makes people learn multiple systems > > and search multiple places - especially if the feature ends up being > > submitted as a patch to the bug tracker. > > > > I'd rather keep wishlist items in the bug tracker than split them into > two. > > > > (also, fwiw, I'd rather keep the tasks number space clean should we > > ever decide to import from bugzilla -> phabricator) > > I'm not tied to a specific issue tracker to use for this and am happy to > other > folks debate which implementation is best, but what I would prefer is a > system > to let us manage "ideas to implement" like the ideas page for GSoC and this > wiki page. The desired output is a list of vetted tasks. A task might > start > out as a wishlist entry, but someone has to step up and say "yes, this is > a good > idea and I will review it / shepherd it, etc." for it to become a "vetted > task". > Being able to store conversation about each task and tag it with other meta > data (e.g. tagging the person who "owns" the task and will do the review / > sheperding as well as being able to categorize them, etc.) However, I do > think > one important thing is that when a new idea is submitted, it has a built-in > sunset. If no one grabs it after time X it becomes closed instead of > remaining > an open wishlist forever. Similarly if the "owner" of a task drops > ownership, > the timer would start while waiting for a new owner. However, this does > feel > very much like an issue tracker. > > -- > John Baldwin > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Hunter Satterwhite Systems Engineer, Technical Operations (TechOps)