Re: junior kernel tasks
On Sat, Oct 25, 2014 at 10:45:36PM +0200, 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 There are some new tasks on the list. Go ahead, take your pick. -- Mateusz Guzik mjguzik gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
On Tuesday, October 28, 2014 7:07:31 pm Eitan Adler wrote: On 28 October 2014 15:14, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: Quoting John Baldwin j...@freebsd.org: 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
GitHub + Gitter? https://gitter.im/ On Wed, Oct 29, 2014 at 11:55 AM, John Baldwin j...@freebsd.org wrote: On Tuesday, October 28, 2014 7:07:31 pm Eitan Adler wrote: On 28 October 2014 15:14, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: Quoting John Baldwin j...@freebsd.org: 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-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org -- Hunter Satterwhite Systems Engineer, Technical Operations (TechOps) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
On, Wed Oct 29, 2014, Eitan Adler wrote: On 28 October 2014 15:14, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: Quoting John Baldwin j...@freebsd.org: 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 ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org 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. We have this situation right now with reviews and the bug tracker. reviews is used by the committers only right now, and both loosely interact with each other. Opening reviews to the public won't improve the situation of having two disparate systems to look into. Same goes for the Wiki and bug tracker, mailing lists, etc. The more relevant question thus would be: how do we point people to the correct location and at which point of time? This will call for a more tight integration in the foresesable future (e.g. search abilities for reviews, that can be triggered from the bug tracker and vice versa). 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) Fair enough. If we are going to do that, the area however should be separate from typical bugs, so people do not confuse wishes with bugs and vice versa. Also, to avoid long and misleading comment trails, we would need the ability to hide/remove errornous (bug-related) comments in the wishlist (a feature wished for independent of this, but a necessary prerequisite [probably coming soon]). Wishlist items thus should not belong to a currently existing product or component, but should be clearly classified in an own product and/or component category. Except from that, what else would be required and desired to have a suitable wishlist? The bug tracker right now features: - tags - keywords - links to internal bugs/items (dependencies and blockers) - links to external systems - links to svn commits and reviews - attachments - flags to request/confirm/deny things Cheers Marcus pgpPGRbV_Fn1c.pgp Description: PGP signature
Re: junior kernel tasks
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. It also provides a better place to store metadata about the issue itself (wikis are kind of poor for that). -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
Quoting John Baldwin j...@freebsd.org: 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: Quoting John Baldwin j...@freebsd.org: 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 ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org 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 regards, Bapt pgp3JNwdA14ys.pgp Description: PGP signature
Re: junior kernel tasks
On 28 October 2014 15:14, Baptiste Daroussin b...@freebsd.org wrote: On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote: Quoting John Baldwin j...@freebsd.org: 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 ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org 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) -- Eitan Adler ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
On Tue, Oct 28, 2014 at 1:35 PM, Marcus von Appen m...@freebsd.org wrote: Quoting John Baldwin j...@freebsd.org: 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org I do not know difficulty of maintaining a tracker such as bug tracker , a different tracker such as development tracker may be defined and used . In that way , ideas which are not expressible as bug in bug tracker ( because sometimes it is not possible to decide whether a problem is bug or a design decision ) may be specified in development tracker and be followed from there . With such a structure the improvement ideas will not be lost in individual mails . At some point an idea may be considered useless or inapplicable but over time it may become very feasible but forgotten or the same person may not mention it once more . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
El 25/10/2014 22:46, Mateusz Guzik mjgu...@gmail.com escribió: Hello, In short, nice kernel tasks people with C language skills can do in few evenings. It would be nice if this page lists other junior tasks in base, documentation, etc, not just the kernel. Cheers. 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 Cheers, -- Mateusz Guzik mjguzik gmail.com ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
Nice info... On Sat, Oct 25, 2014 at 11:45 PM, Mateusz Guzik mjgu...@gmail.com 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 Cheers, -- Mateusz Guzik mjguzik gmail.com ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org -- Mageirias Anastasios www.junkbytes.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: junior kernel tasks
On Sat, Oct 25, 2014 at 1:45 PM, Mateusz Guzik mjgu...@gmail.com wrote: Hello, In short, nice kernel tasks people with C language skills can do in few evenings. https://wiki.freebsd.org/JuniorJobs Thanks for making that list. I was looking at some other projects, and noticed that on the front page of http://www.dragonflybsd.org/ , they have a Now Hiring section with multiple links to Code Bounties, Summer of Code, etc., to help attract new people to the project. We need something like that on the front page of freebsd.org, to help attract new blood to the project. We have all the info, but it is just scattered across many different web pages, and is often outdated and not maintained. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
