Christian suggested Bloodhound could be offered as an issue tracking tool for new podlings in the incubator. I think that's a great idea.
What do you think is left to do for this to be feasible? How far away is our multi product support for example from being stable? - Joe On 11 April 2013 19:00, Joachim Dreimann <[email protected]>wrote: > > On 10 April 2013 19:22, Christian Grobmeier <[email protected]> wrote: > >> On Wed, Apr 10, 2013 at 7:35 PM, Joe Dreimann >> <[email protected]> wrote: >> > I think that's a great idea Christian. >> > >> > We will need to improve our MultiProduct support a little further >> before its ready, but hopefully that's not far away. >> >> Oh, cool. Maybe it would be a good idea to speak with the BH team on >> the idea, others might have some more issues they want to clear out >> before going such a path. >> > > I will raise this on the dev@bloodhound mailing list and will report back > next week. > > >> >> > Will it need to be vetted by Infra for security etc? >> >> I don't know, but it is surely a good idea to ask Infra for advice on >> that matter. >> > > Will do. > > >> Is there a chance to import tickets from Bugzilla or Jira btw? I mean, >> if a project wants to move. >> > > > Cheers >> Christian > > > We've not had any contributions in that direction, but there are tools > available for Trac that may serve as a starting point. I would argue that > migration tools for specific source applications should be out of the scope > of the core project, but that's a discussion for the Bloodhound community. > > Cheers, > Joe > > >> > >> > - Joe >> > >> > ________________________ >> > @jdreimann - Twitter >> > Sent from my phone >> > >> > On 10 Apr 2013, at 18:30, Christian Grobmeier <[email protected]> >> wrote: >> > >> >> Hi, >> >> >> >> we suggest using Jira or Bugzilla for new podlings: >> >> >> http://incubator.apache.org/guides/proposal.html#template-issue-tracking >> >> >> >> But we have Apache Bloodhound, and they have an installed instance >> here: >> >> https://issues.apache.org/bloodhound >> >> >> >> I am not sure if it is ready for other projects, but can imagine. >> >> Anybody knows about the status? >> >> >> >> If it is ready for us I think we should invite podlings to use >> >> Bloodhound - and maybe even suggest Bloodhound as first idea. >> >> >> >> Thoughts? >> >> >> >> Christian >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/> @jdreimann <https://twitter.com/jdreimann> * * *Join one of our free daily demo sessions on* *Scaling Subversion for the Enterprise <http://www.wandisco.com/training/webinars>* THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of WANdisco, unless the author is authorized by WANdisco to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and review by WANdisco. Although WANdisco operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.
