From gschrader at gmail.com  Fri Sep 27 17:01:47 2019
From: gschrader at gmail.com (Glen Schrader (gschrader))
Date: Fri, 27 Sep 2019 11:01:47 -0600
Subject: Using Caciocavallo code
Message-ID: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190927/d2d8cd32/attachment.html>

From emilian.bold at gmail.com  Sat Sep 28 06:20:35 2019
From: emilian.bold at gmail.com (Emilian Bold)
Date: Sat, 28 Sep 2019 09:20:35 +0300
Subject: Using Caciocavallo code
In-Reply-To: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
Message-ID: <CAL6R17BwYY1jsDnkAA9wgmS_nv9Jh=bETnKtGeyY04CqCK6Tqg@mail.gmail.com>

The mailing list still seems to work.

Making a public GitHub repository should be enough.

PS: for internal projects GPL does not force you to make the code public,
but don't let that stop you!

--emi

s?m., 28 sept. 2019, 02:55 Glen Schrader (gschrader) <gschrader at gmail.com>
a scris:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/45870c1d/attachment.html>

From neugens.limasoftware at gmail.com  Sat Sep 28 06:23:28 2019
From: neugens.limasoftware at gmail.com (Mario Torre)
Date: Sat, 28 Sep 2019 08:23:28 +0200
Subject: Using Caciocavallo code
In-Reply-To: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
Message-ID: <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>

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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/6d7552c3/attachment.html>

From pontus.amberg at gmail.com  Sat Sep 28 12:46:04 2019
From: pontus.amberg at gmail.com (Pontus Amberg)
Date: Sat, 28 Sep 2019 14:46:04 +0200
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
Message-ID: <CAPJFWx=sk-At7NjvrtUbjdCqUwtwREEf3oXqHGJiWeTXVaqRfw@mail.gmail.com>

I was looking at Caciocavallo a while ago to run headless test and the only
thing that stoped me from using it was the incompatibility with more
recents JDK:s. So a public update would be really appreciated!

/Pontus

On Sat, 28 Sep 2019 at 08:25, 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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/092818d6/attachment.html>

From gschrader at gmail.com  Sat Sep 28 14:11:32 2019
From: gschrader at gmail.com (Glen Schrader (gschrader))
Date: Sat, 28 Sep 2019 08:11:32 -0600
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
Message-ID: <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>

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.

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.

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 <mailto: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/ <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 <http://neugens.wordpress.com/> - Twitter: @neugens
> Proud GNU Classpath developer: http://www.classpath.org/ <http://www.classpath.org/>
> OpenJDK: http://openjdk.java.net/projects/caciocavallo/ <http://openjdk.java.net/projects/caciocavallo/>
> 
> Please, support open standards:
> http://endsoftpatents.org/ <http://endsoftpatents.org/>

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

From gschrader at gmail.com  Sat Sep 28 14:12:37 2019
From: gschrader at gmail.com (Glen Schrader (gschrader))
Date: Sat, 28 Sep 2019 08:12:37 -0600
Subject: Using Caciocavallo code
In-Reply-To: <CAPJFWx=sk-At7NjvrtUbjdCqUwtwREEf3oXqHGJiWeTXVaqRfw@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <CAPJFWx=sk-At7NjvrtUbjdCqUwtwREEf3oXqHGJiWeTXVaqRfw@mail.gmail.com>
Message-ID: <265096F6-1E6D-442D-9262-69CE23D562DB@gmail.com>

I?m glad I?m not the only one still interested in this then!

> On Sep 28, 2019, at 6:46 AM, Pontus Amberg <pontus.amberg at gmail.com> wrote:
> 
> I was looking at Caciocavallo a while ago to run headless test and the only thing that stoped me from using it was the incompatibility with more recents JDK:s. So a public update would be really appreciated!
> 
> /Pontus
> 
> On Sat, 28 Sep 2019 at 08:25, Mario Torre <neugens.limasoftware at gmail.com <mailto: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 <mailto: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/ <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 <http://neugens.wordpress.com/> - Twitter: @neugens
> Proud GNU Classpath developer: http://www.classpath.org/ <http://www.classpath.org/>
> OpenJDK: http://openjdk.java.net/projects/caciocavallo/ <http://openjdk.java.net/projects/caciocavallo/>
> 
> Please, support open standards:
> http://endsoftpatents.org/ <http://endsoftpatents.org/>

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

From roman at kennke.org  Sat Sep 28 14:42:39 2019
From: roman at kennke.org (Roman Kennke)
Date: Sat, 28 Sep 2019 16:42:39 +0200
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
Message-ID: <177DF3D5-347E-4130-91D9-AB461A8741B7@kennke.org>

I'd suggest moving it to github and not bother with OpenJDK bureaucracy.
Roman

Am 28. September 2019 08:23:28 MESZ schrieb Mario Torre <neugens.limasoftware at gmail.com>:
>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/

-- 
Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20190928/11c6a580/attachment.html>

From neugens.limasoftware at gmail.com  Sat Sep 28 18:13:15 2019
From: neugens.limasoftware at gmail.com (Mario Torre)
Date: Sat, 28 Sep 2019 20:13:15 +0200
Subject: Using Caciocavallo code
In-Reply-To: <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
Message-ID: <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>

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/

From gschrader at gmail.com  Sat Sep 28 20:32:05 2019
From: gschrader at gmail.com (Glen Schrader (gschrader))
Date: Sat, 28 Sep 2019 14:32:05 -0600
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
 <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
Message-ID: <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>

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>

From neugens.limasoftware at gmail.com  Mon Sep 30 11:40:03 2019
From: neugens.limasoftware at gmail.com (Mario Torre)
Date: Mon, 30 Sep 2019 13:40:03 +0200
Subject: Using Caciocavallo code
In-Reply-To: <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
 <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
 <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>
Message-ID: <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>

Il giorno sab 28 set 2019 alle ore 22:32 Glen Schrader (gschrader)
<gschrader at gmail.com> ha scritto:
>
> 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 think the mailing list is only really significant if you want to use
it for reviews (which is where Skara would help, since it makes the
bridge between GitHub and the mailing list automatic). As for the bug
database, historically Cacio predates the public Jira OpenJDK, so we
always used our own bugzilla:

https://icedtea.classpath.org/bugzilla/describecomponents.cgi?product=Caciocavallo

I would be happy to hand you the "keys".

>
> 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

I didn't, and I don't think Roman did either, we should probably
contact GitHub and see who owns that and if they are willing to
release it.

> 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.

I don't think there's any problem in changing it, although for
historical reasons we may want to keep it the same. If you refactor
the group id you should also change the packages though, for
consistency.

Cheers,
Mario
-- 
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/

From dalibor.topic at oracle.com  Mon Sep 30 12:04:15 2019
From: dalibor.topic at oracle.com (Dalibor Topic)
Date: Mon, 30 Sep 2019 14:04:15 +0200
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
 <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
 <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>
 <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>
Message-ID: <da5175a6-e8eb-21e4-f0a3-dc66a651de9d@oracle.com>

On 30.09.2019 13:40, Mario Torre wrote:
>> 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.
> 
> I don't think there's any problem in changing it, although for
> historical reasons we may want to keep it the same. If you refactor
> the group id you should also change the packages though, for
> consistency.

Generally speaking, if someone forks a project off OpenJDK to somewhere 
else, please make sure to change existing OpenJDK references such 
org.openjdk maven coordinates, etc. to avoid conflicts and confusion 
down the road if, for example, someone else chooses to continue with 
development within OpenJDK.

cheers,
dalibor topic
-- 
<http://www.oracle.com>
Dalibor Topic | Consulting Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961> | Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 M?nchen
Registergericht: Amtsgericht M?nchen, HRB 246209
Gesch?ftsf?hrer: Ralf Herrmann

<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment

From gschrader at gmail.com  Mon Sep 30 14:53:58 2019
From: gschrader at gmail.com (Glen Schrader (gschrader))
Date: Mon, 30 Sep 2019 08:53:58 -0600
Subject: Using Caciocavallo code
In-Reply-To: <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
 <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
 <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>
 <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>
Message-ID: <102E6778-96CF-497B-9149-C92F3007F47E@gmail.com>


> On Sep 30, 2019, at 5:40 AM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
> 
> 
> I think the mailing list is only really significant if you want to use
> it for reviews (which is where Skara would help, since it makes the
> bridge between GitHub and the mailing list automatic). As for the bug
> database, historically Cacio predates the public Jira OpenJDK, so we
> always used our own bugzilla:
> 
> https://icedtea.classpath.org/bugzilla/describecomponents.cgi?product=Caciocavallo
> 
> I would be happy to hand you the "keys?.


I only spot, 7 issues in there (4 without resolution) so maybe just manually copying them into GitHub Issues is the easiest.


> 
> I didn't, and I don't think Roman did either, we should probably
> contact GitHub and see who owns that and if they are willing to
> release it.

I sent GitHub a request, we?ll see what they say.



> 
> I don't think there's any problem in changing it, although for
> historical reasons we may want to keep it the same. If you refactor
> the group id you should also change the packages though, for
> consistency.
> 

Given Dalibor?s comment, I guess changing it probably makes more sense. How about the copyright notices, I noticed there is a mix between Sun and Oracle and even a couple Red Hat notices thrown in. I assume those remain unchanged? What about current files that are missing one, should one be added?

Thanks,
Glen

From neugens.limasoftware at gmail.com  Mon Sep 30 15:22:20 2019
From: neugens.limasoftware at gmail.com (Mario Torre)
Date: Mon, 30 Sep 2019 17:22:20 +0200
Subject: Using Caciocavallo code
In-Reply-To: <102E6778-96CF-497B-9149-C92F3007F47E@gmail.com>
References: <0E2BDB3F-43E5-4C71-98D1-18D9B3A36520@gmail.com>
 <CAGUMyaRQ+8MzFHMC+u8TC1fj0DT_cpSBjOSAf2B7DkwcsmEYwQ@mail.gmail.com>
 <811758E4-9A80-4C43-B3EF-2EC451F02EB7@gmail.com>
 <CAGUMyaTJir3Oar0VKvvKs+AoOOmq9FM=uNwo_o_K4AcmOJgjBQ@mail.gmail.com>
 <84BD3B50-ECA3-4751-AABE-0DF7EB98E5DF@gmail.com>
 <CAGUMyaRQfHXJ0X1g4cM9V0aTfX5nHoAqBiN4c9p58eU7ognLqA@mail.gmail.com>
 <102E6778-96CF-497B-9149-C92F3007F47E@gmail.com>
Message-ID: <CAGUMyaTghFsX4=PCyvO_OHNPCinnV_fbz_5AKkBfPPAhZ5FsUQ@mail.gmail.com>

Il giorno lun 30 set 2019 alle ore 16:54 Glen Schrader (gschrader)
<gschrader at gmail.com> ha scritto:
>
>
> > On Sep 30, 2019, at 5:40 AM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
> >
> >
> > I think the mailing list is only really significant if you want to use
> > it for reviews (which is where Skara would help, since it makes the
> > bridge between GitHub and the mailing list automatic). As for the bug
> > database, historically Cacio predates the public Jira OpenJDK, so we
> > always used our own bugzilla:
> >
> > https://icedtea.classpath.org/bugzilla/describecomponents.cgi?product=Caciocavallo
> >
> > I would be happy to hand you the "keys?.
>
>
> I only spot, 7 issues in there (4 without resolution) so maybe just manually copying them into GitHub Issues is the easiest.
>
>
> >
> > I didn't, and I don't think Roman did either, we should probably
> > contact GitHub and see who owns that and if they are willing to
> > release it.
>
> I sent GitHub a request, we?ll see what they say.
>
>
>
> >
> > I don't think there's any problem in changing it, although for
> > historical reasons we may want to keep it the same. If you refactor
> > the group id you should also change the packages though, for
> > consistency.
> >
>
> Given Dalibor?s comment, I guess changing it probably makes more sense. How about the copyright notices, I noticed there is a mix between Sun and Oracle and even a couple Red Hat notices thrown in. I assume those remain unchanged? What about current files that are missing one, should one be added?

Yeah, everything should stay the same. For the missing files the
Oracle copyright notice is enough, for new files you will add you can
use anything you want as long as it's compatible with the current
license.

Cheers,
Mario


-- 
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/