<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Sun, Aug 4, 2013 at 10:09 AM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com" target="_blank">tzafrir.cohen@xorcom.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On Sun, Jul 14, 2013 at 03:14:56PM -0500, Matthew Jordan wrote:<br>
> On Sun, Jul 14, 2013 at 12:37 PM, Faidon Liambotis <<a href="mailto:paravoid@debian.org">paravoid@debian.org</a>>wrote:<br>
<br>
</div><div class="im">> > Filed under asterisk/pjproject, 6 months ago, no reply at all (while at<br>
> > the same time #1/#2 were closed):<br>
</div>> > <a href="https://github.com/asterisk/**pjproject/issues/3" target="_blank">https://github.com/asterisk/**pjproject/issues/3</a><<a href="https://github.com/asterisk/pjproject/issues/3" target="_blank">https://github.com/asterisk/pjproject/issues/3</a>><br>
<div class="im">><br>
><br>
> I don't think we're watching the issue tracker on github terribly closely.<br>
> The build modifications to pjproject were all tracked in Jira (see<br>
> <a href="https://issues.asterisk.org/jira/browse/ASTERISK-20811" target="_blank">https://issues.asterisk.org/jira/browse/ASTERISK-20811</a>). Since Jira is<br>
> where all issues Asterisk related are filed - and people dealing with the<br>
> Asterisk project know to look there - it would probably be better to file<br>
> any future issues with the Asterisk compatible pjproject there.<br>
><br>
> Even so, I'm not sure what actions we can take on this issue. As was<br>
> already said, removing libraries out of it isn't really our call to make,<br>
> unless we want to take complete ownership and fork the project.<br>
<br>
</div>I have a semi-working package. Where do I file bug reports? On the<br>
chans/chan_pjsip component in the Jira? I would also hate to firce<br>
any contributor to sign *Digium*'s license agreement for uploading a<br>
patch to that package.</blockquote><div><br></div><div style>So first, thanks for testing it out Tzafrir. It's really appreciated!</div><div style><br></div><div style>I'd prefer to use Jira for issues made against the pjproject fork, until such time as we submit the patch back to Teluu. While I know github provides an issue tracker, trying to maintain issues and work queues in multiple issue trackers is not much fun. Assuming they accept the changes, I'd prefer to see any modifications or issues should be made through their issue tracker.</div>
<div style><br></div><div style>That's not a hard and fast decision. There may be some exceptions we make to this - a security vulnerability detected in pjproject by a user of Asterisk comes to mind - but in general I'd prefer to not reproduce problems in multiple issue trackers. It would also be cumbersome for bug marshals to have to clean up and report issues in Teluu's bug tracker from Asterisk issues. I have a feeling we'll be working through the mechanics of this some more as time goes on - so far now, we'll just be flexible and see how things go.</div>
<div><br></div><div>As far as modifications are concerned, a pull request against the github project should be sufficient. Having an issue in Jira that you reference to that pull request may be helpful since bug marshals typically watch Jira. Since Digium does not hold the License to pjproject, any modifications made to it simply have to be made under Teluu's licensing scheme. As such, I don't see any reason to attach the patch made in the pull request to the Jira issue.</div>
<div style><br></div></div>Matt<br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div><div>
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div></div>
</div></div>