Assuming Pedro still has his git repo somewhere (local hard drive, github fork) it's not really gone and we can restore it, or at the very least cherry-pick the commits.<br><br><div class="gmail_quote">On Wed, Oct 3, 2012 at 7:05 PM, Anil Saldhana <span dir="ltr"><<a href="mailto:Anil.Saldhana@redhat.com" target="_blank">Anil.Saldhana@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Shane,<br>
did you throw away the JPA code that Pedro had done for almost a
month? Where is that code? <br>
<br>
Code contributions have legal ramifications. We cannot just throw
away code and loss of history is deeply disturbing.<br>
<br>
Regards,<br>
Anil<div><div class="h5"><br>
<br>
On 10/03/2012 05:39 PM, Shane Bryzak wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div>There was a little bit of confusion
over the legacy IDM code (I had forgotten that it had been
migrated to the picketlink-idm repo on GitHub albeit under
different branches) but this has been sorted out now, and I
believe all the history for it is intact. As for the temporary
IDM implementation we have the final snapshot of it, however
since then I've blown it away anyhow and started working on the
proper implementation. I don't think we need the history for
the temporary stuff. <br>
<br>
Agreed with the collective PL release. As for the version
number, did we ever do a 2.x release? If so, then I agree we
should update it to 3.x for the new project.<br>
<br>
Shane<br>
<br>
On 04/10/12 01:06, Anil Saldhana wrote:<br>
</div>
<blockquote type="cite">
<div>Shane,<br>
ahh. You could not wait a day or two. :) I am wondering if
we could have retained history via some form of "git mv".<br>
<br>
We should probably have PicketLink version as 3.0 for all the
code and rather than do individual releases, we can do a
collective PL3.x release.<br>
<br>
Cheers.<br>
<br>
On 10/02/2012 04:56 AM, Boleslaw Dawidowicz wrote:<br>
</div>
<blockquote type="cite">
I restored our branches and synced with Shane on IM.
<div><br>
</div>
<div>picketlink-idm/master will be nuked and only contain some
README pointing to new locations</div>
<div><br>
</div>
<div>Current picketlink-idm repo will be kept for few more
months at least and after we are in more calm situation with
GateIn/EPP it will be renamed into picketlink-idm-legacy. </div>
<div><br>
</div>
<div>Things under control :)</div>
<div><br>
</div>
<div>Bolek</div>
<div><br>
<div>
<div>On Oct 2, 2012, at 11:08 AM, Boleslaw Dawidowicz <<a href="mailto:bdawidow@redhat.com" target="_blank">bdawidow@redhat.com</a>>
wrote:</div>
<br>
<blockquote type="cite">
<div style="word-wrap:break-word">
<div>I must say I'm quite pissed off… even yesterday I
shared a link to one of configuration files in 1.4
branch with a consultants. We released twice last
month… how could have it happened without any
question?</div>
<div><br>
</div>
<br>
<div>
<div>On Oct 2, 2012, at 11:06 AM, Boleslaw
Dawidowicz <<a href="mailto:bdawidow@redhat.com" target="_blank">bdawidow@redhat.com</a>>
wrote:</div>
<br>
<blockquote type="cite">
<div style="word-wrap:break-word">Have you just removed
picketlink-idm on github?
<div><br>
</div>
<div>We are actively working on 1.4 branch and
this is critical for EPP. Other branches are
still maintenance for older versions of
GateIn/EPP. I think I was fairly clear that we
need those. </div>
<div><br>
</div>
<div>This repo needs to be restored ASAP. </div>
<div><br>
<div>
<div>On Oct 2, 2012, at 12:30 AM, Shane
Bryzak <<a href="mailto:sbryzak@redhat.com" target="_blank">sbryzak@redhat.com</a>>
wrote:</div>
<br>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000"> In
the interests of presenting a clear
message to our developers, one of the
steps we'll be taking is to consolidate
the various PicketLink projects into a
single project and presenting this as
the "go to" solution for application
security. For now I've merged the CDI
and IDM subprojects (these are now
submodules of the PicketLink project,
with "CDI" renamed to "Core") and the
plan is to eventually merge the social
and federation modules also.<br>
<br>
You can find the new GitHub repository
here:
<a href="https://github.com/picketlink" target="_blank">https://github.com/picketlink</a>
(renamed from picketlink-cdi) and the
picketlink-idm repository has now been
deleted. For anyone working on these
modules, please use the new repository
from now on.<br>
<br>
Thanks!<br>
Shane</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
security-dev mailing list
<a href="mailto:security-dev@lists.jboss.org" target="_blank">security-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/security-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<br>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
security-dev mailing list
<a href="mailto:security-dev@lists.jboss.org" target="_blank">security-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/security-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
security-dev mailing list<br>
<a href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/security-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/security-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>