Using Caciocavallo code

Sat Sep 28 20:32:05 UTC 2019

Sorry I’m resending this as I ended up over the size limit with a screenshot:

Yes it doesn’t seem like there is much advantage to reopen the project, the mailing list is really the only thing that would be missing from GitHub. I don’t really foresee any code that would be contributed back to openjdk.

I agree keeping the history is important, the Github import kept that I think.

I was thinking maybe it would be best to create a Github organization to have the project in, that way I could also split out the other backend modules into their own repos (using git filter-branch) and keep them rather than outright deleting them. I see the org name has already been taken though, did you guys already grab this by chance?

https://github.com/caciocavallo <https://github.com/caciocavallo>

The only other thing I can think of at the moment is being able to push new releases to maven central, I don’t know if maybe the group id should change to reflect the new home.

Glen

> On Sep 28, 2019, at 12:13 PM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
> 
> Il giorno sab 28 set 2019 alle ore 16:11 Glen Schrader (gschrader)
> <gschrader at gmail.com> ha scritto:
>> 
>> Yeah I’m torn, I almost put my hand up earlier, my problem is not understanding the other backends and if they could even be kept working. I’m guessing since they are excluded from the module set in the pom that maybe they are already in a questionable state.
> 
> Well, that's a decision for the new maintainer, code can be removed,
> added, deprecated ;)
> 
>> For the foreseeable future I will be trying to keep shared/tta working on LTS releases.
>> 
>> I’m not sure what project Skara offers in addition to the Mercurial import Github can already do.
> 
> I don't think it matters in general for development, but we should
> preserve the history in the code, which is what skara help doing. If
> you would like to formally revive the project let me know, it probably
> makes more sense to just keep it on GitHub however, the only caveat is
> that external contributions need to sign the OCA if this is an OpenJDK
> project, you don't need that if you don't want to ever merge this code
> back into OpenJDK (even in the remote case the project is revived).
> 
> The only practical advantage would be to keep the mailing list and the
> OpenJDK infrastructure like the bug database I think.
> 
> Since we voted to close the project and the mailing list is still
> active just by chance, to revive the project we will need approval on
> the porters group, so the case should be strong that a new maintainer
> is willing to take Cacio to the next level.
> 
> Cheers,
> Mario
> 
>> Glen
>> 
>> 
>> On Sep 28, 2019, at 12:23 AM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
>> 
>> Ho Glen,
>> 
>> I notified registrar but it seems things are still alive ;)
>> 
>> If you plan to contribute more I think the best would reopen the project and make you lead, if you instead think this is a one off contribution, perhaps followed by occasional patches in the future, creating a GitHub repository is probably best.
>> 
>> In fact, we could migrate all the current code to GitHub now anyway using project Skara tooling.
>> 
>> Cheers,
>> Mario
>> 
>> On Sat 28. Sep 2019 at 01:55, Glen Schrader (gschrader) <gschrader at gmail.com> wrote:
>>> 
>>> Hello again,
>>> 
>>> I know the project was dissolved (in fact I’m not even sure this email will go through) but I’m just wondering what I should do with code changes I made in order to get the shared and tta modules working under JDK11. My initial plan was to stop using Caciocavallo and use Xvfb/vnc to run headless unit tests but I ran into other issues going that route so I ended up making the necessary code changes. I know the license is GPL so I should be making the code available, right now I have it imported into a private GitHub repo, so at the very least I will make that public but I wonder if I should just take the code I need and start a new project. Any thoughts?
>>> 
>>> PS if this email bounces, then I will email Mario and Roman directly instead.
>>> 
>>> Thanks,
>>> Glen
>> 
>> --
>> pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
>> Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF
>> 
>> Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens
>> Proud GNU Classpath developer: http://www.classpath.org/
>> OpenJDK: http://openjdk.java.net/projects/caciocavallo/
>> 
>> Please, support open standards:
>> http://endsoftpatents.org/
>> 
>> 
> 
> 
> -- 
> pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
> Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF
> 
> Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens
> Proud GNU Classpath developer: http://www.classpath.org/
> OpenJDK: http://openjdk.java.net/projects/caciocavallo/
> 
> Please, support open standards:
> http://endsoftpatents.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/7ad2c290/attachment-0001.html>