<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’m already knee-deep in plugins, so I’ll see what I can do to make a list of what appears to be working and what isn’t. I agree that step one at this point should be triage.<br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; border-collapse: separate; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class="Apple-interchange-newline">- Fred McCann</div><div class=""><a href="mailto:fred@sharpnoodles.com" class="">fred@sharpnoodles.com</a></div></div></span></div></div></div>
</div><div class=""><br class="webkit-block-placeholder"></div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Feb 19, 2016, at 2:44 PM, Richard Wilbur <<a href="mailto:richard.wilbur@gmail.com" class="">richard.wilbur@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Fri, Feb 19, 2016 at 11:35 AM, Fred McCann <<a href="mailto:fred@sharpnoodles.com" class="">fred@sharpnoodles.com</a>> wrote:<br class="">[...]<br class=""><blockquote type="cite" class="">I’m more than happy to update the plugin list. Do I need an account to do<br class="">that? I’m don’t see any edit options.<br class=""></blockquote><br class="">You can use your <a href="http://launchpad.net" class="">launchpad.net</a> account to login and edit the wiki.<br class="">Just click the "login" link at the bottom of the page, click the<br class="">"Login" button on the next page, if your browser doesn't automatically<br class="">redirect click the "Continue" button, and you will find yourself at<br class="">the Ubuntu One (OpenID server) login page. After you provide your<br class="">launchpad credentials, approve the release of authentication<br class="">information to <a href="http://wiki.bazaar.canonical.com" class="">wiki.bazaar.canonical.com</a> and you will be authorized to<br class="">edit (the links should appear).<br class=""><br class=""><blockquote type="cite" class="">I’m still working through these, but it seems like quite a few are<br class="">abandoned and in some case have been rolled into bzr core. How can<br class="">we get that cleaned up?<br class=""></blockquote><br class="">I'm creating a list of plugins that have been specifically orphaned<br class="">(previous maintainer asked for someone to take over). It seems to me<br class="">that if no willing person steps up to adopt them, we could consider<br class="">putting them under the auspices of the bzr-core team, or some such,<br class="">which would lend more flexibility in authorizing maintenance and<br class="">releases.<br class=""><br class="">I'm all for updating the list with what works. I'd also be interested<br class="">in setting up some automated testing so it is easier to tell whether<br class="">or not they work without having to branch every plugin and run it's<br class="">test suite against current bzr trunk.<br class=""><br class=""><blockquote type="cite" class="">I think the best is to make a clear cut about what works with bzr-2.7<br class="">and what doesn't.<br class=""></blockquote><br class="">Yes. Then we'll have a list of what plugins need some love.<br class=""><br class=""><blockquote type="cite" class="">If enough people care and help we can then add more to the what works<br class="">list by doing releases for the plugins whose trunk is owned by lp:~bzr<br class="">(bzr-stats for example), it's harder if they aren't (bzrtools for<br class="">example) in that case, reaching to the project owner and nicely asking<br class="">for a release may be the way to go.<br class=""></blockquote><br class="">If we can offer a merge proposal for a branch with the fix, then we<br class="">might make the project owner's job even easier.<br class=""><br class=""><blockquote type="cite" class="">It’s lousy advertising to list very old plugins that don’t work<br class="">anymore.<br class=""></blockquote><br class="">I think it is unfortunate to list plugins that don't work anymore<br class="">under the "Working" status. On the other hand, I'd be interested in<br class="">collecting those that don't work anymore in a separate list with<br class="">appropriate status so we don't advertise them as working but have a<br class="">chance to remedy the situation.<br class=""><br class=""><blockquote type="cite" class="">Also, is there any plan/way to suggest that we look into rolling<br class="">some fundamental plugins like xmloutput, bzrtools (or some portion<br class="">of it), bisect, extmerge, etc into the core bzr codebase?<br class=""><br class=""><br class="">There has been discussions about that, but it's up to the project owners<br class="">to do so. I know that in some cases, copyright issues were raised and<br class="">blocked the process.<br class=""></blockquote><br class="">I wonder how hard those issues would be to resolve--especially for the orphans?<br class=""><br class=""><blockquote type="cite" class="">It seems like quite a few critical batteries are not included in<br class="">the box.<br class=""><br class=""><br class="">It's a hard balance to find between freedom to evolve in the plugins and<br class="">the additional work to carry them inside the core bzr tree.<br class=""></blockquote><br class="">I understand for new ideas and things that are a work in progress, the<br class="">freedom to change/evolve as needs and desires dictate is very useful<br class="">and encourages the process. On the other hand if the plugins are<br class="">orphaned, stable, or mature, it might be worth revisiting the<br class="">discussion on a case-by-case basis.<br class=""><br class="">Richard<br class=""></div></div></blockquote></div><br class=""></body></html>