<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I took a few moments to file a few more starters for Foundation (hopefully I should be able to fill out a few more soon). I ran across a some nice ones that should be relatively trivial to knock out. I think for Foundation the marker for a good starter bug would be things that are highly testable with a reduced scope of interfaces. Formatter subclasses are a great point to start with. Some of the NSUnimplemented methods are minefields that would require runtime support, whereas others are great points to start with.</div><div class=""><br class=""></div><div class="">Furthermore there will likely be a few good ones that will come in when the proposals start to land; there is a lot of busy work with the whole naming changes. So stay tuned on that front.</div><br class=""><div><blockquote type="cite" class=""><div class="">On May 23, 2016, at 7:18 PM, Brian Gesiak via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I'm glad people are finding these useful!!<br class=""><br class="">Yes, I've made one for corelibs-foundation as well: <a href="https://bugs.swift.org/secure/Dashboard.jspa?selectPageId=10410" class="">https://bugs.swift.org/secure/Dashboard.jspa?selectPageId=10410</a><br class=""><br class="">Of course, as David mentioned, task curation is what makes these dashboards really shine. Try assigning the "swift-3.0" label to tasks that should be taken care of in time for its release. Also, I noticed swift-corelibs-foundation doesn't have many tasks with the "StarterBug" label. I think those are a great way to encourage more people to contribute.<div class=""><br class=""></div><div class="">- Brian Gesiak</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, May 23, 2016 at 5:57 PM, David Hart <span dir="ltr" class=""><<a href="mailto:david@hartbit.com" target="_blank" class="">david@hartbit.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class=""><div class="">Brian Gesiak started started one for foundation. It seems it's only missing some trimming and labeling of issues:</div><span class=""><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><span style="background-color:rgba(255,255,255,0)" class="">David,</span><div class=""><span style="background-color:rgba(255,255,255,0)" class=""><br class=""></span></div><div class=""><span style="background-color:rgba(255,255,255,0)" class="">I actually started on one! <a href="http://tinyurl.com/foundation-dashboard" target="_blank" class="">http://tinyurl.com/foundation-dashboard</a> :)<br class=""><br class="">Like you mentioned, I don't have a ton of context on the project, so I'm a little hesitant to decide what should be tagged with "swift-3.0".<br class=""><br class="">Still, one thing that stands out: swift-corelibs-foundation has only one task with the StarterBug label! I wonder if some tasks can be cleaned up, given clearer instructions, and labeled as a starter task...</span></div><div class=""><span style="background-color:rgba(255,255,255,0)" class=""><br class=""></span></div><div class=""><span style="background-color:rgba(255,255,255,0)" class="">- Brian Gesi</span></div></blockquote></div></span><div class=""><div class="h5"><div class=""><br class="">On 23 May 2016, at 22:41, Tony Parker via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">This is slick!<div class=""><br class=""></div><div class="">I would love to have one for Foundation too (although my understanding of JIRA is limited at best).</div><div class=""><br class=""></div><div class="">- Tony</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 22, 2016, at 12:47 PM, Brian Gesiak via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">Hello all!<br class=""><br class="">If you're like me, you might be curious how Core Libraries like swift-corelibs-xctest are doing with regards to the looming Swift 3.0 release. Well, wonder no more -- this handy JIRA dashboard has the information you need: <a href="https://bugs.swift.org/secure/Dashboard.jspa?selectPageId=10408" target="_blank" class="">https://bugs.swift.org/secure/Dashboard.jspa?selectPageId=10408</a><br class=""><br class=""><div class="">The dashboard not only lists tasks that need to be resolved by Swift 3.0, but also open starter tasks for new contributors.<br class=""><br class="">Let me know if you find it useful! I personally think it'd be neat to have one of these for all the swift-corelibs-* projects, what do you all think? :)</div><div class=""><br class="">PS: For those interested, the dashboard is implemented using custom task filters:<br class=""><br class="">- corelibs-xctest Open Tasks: <a href="https://bugs.swift.org/issues/?filter=10469" target="_blank" class="">https://bugs.swift.org/issues/?filter=10469</a><br class="">- corelibs-xctest Open 3.0 Tasks: <a href="https://bugs.swift.org/issues/?filter=10471" target="_blank" class="">https://bugs.swift.org/issues/?filter=10471</a><br class="">- corelibs-xctest Open Starter Tasks: <a href="https://bugs.swift.org/issues/?filter=10470" target="_blank" class="">https://bugs.swift.org/issues/?filter=10470</a></div><div class=""><br class=""></div><div class="">To track tasks related to Swift 3.0, I created a new "swift-3.0" label in JIRA. I hope no one minds. (+cc Jordan Rose, I've seen him managing labels on JIRA before.)</div><div class=""><br class=""></div><div class="">- Brian Gesiak</div><div class=""><br class=""></div></div>
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-corelibs-dev mailing list</span><br class=""><span class=""><a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a></span><br class=""></div></blockquote></div></div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></div></blockquote></div><br class=""></body></html>