Project Panama is moving to GitHub

Thu Jan 23 18:16:15 UTC 2020

Hi Vladimir,

If more time is needed we should postpone.

Though, I think no matter when the move happens, some amount of slowdown 
will be unavoidable. At some point we have to bite the bullet, so I 
would like to try and pick a concrete date for the move. If more time is 
needed at that point, or something else comes up in the mean time, we 
can postpone again.

How much time do you think is needed? Can you suggest a date?

Thanks,
Jorn

On 23/01/2020 19:01, Vladimir Ivanov wrote:
> I fully support the move to GitHub, but would like to suggest 
> postponing it for Vector API project.
>
> Currently, the project goes through a major refactoring and I'm afraid 
> that in the short term the adaption to new workflow will slow us down.
>
> I suggest to do the switch once most of the planned work land in the 
> repository.
>
> Best regards,
> Vladimir Ivanov
>
> On 15.01.2020 02:30, Viswanathan, Sandhya wrote:
>> The move and split are ok from our side as well.  We would need the 
>> automerge feature for "vector" also going forward.
>>
>> Best Regards,
>> Sandhya
>>
>>
>> -----Original Message-----
>> From: panama-dev <panama-dev-bounces at openjdk.java.net> On Behalf Of 
>> Paul Sandoz
>> Sent: Tuesday, January 14, 2020 9:51 AM
>> To: Maurizio Cimadamore <maurizio.cimadamore at oracle.com>
>> Cc: Erik Duveblad <erik.helin at oracle.com>; Robin Westberg 
>> <robin.westberg at oracle.com>; panama-dev at openjdk.java.net
>> Subject: Re: Project Panama is moving to GitHub
>>
>> Likewise, I support the move and split, with the few weeks heads up.
>>
>> Panama covers a wide area, in the future there might be other 
>> technically non-intersecting but complementary repos under Project 
>> Panama’s vision and governance.
>>
>> Paul.
>>
>>> On Jan 14, 2020, at 7:08 AM, Maurizio Cimadamore 
>>> <maurizio.cimadamore at oracle.com> wrote:
>>>
>>> I support both:
>>>
>>> * moving to Git
>>> * adopting the PR model
>>> * splitting vector from ffi support - we already have different set 
>>> of requirements for these two pieces (e.g. ffi branches are 
>>> automerged, vector ones are not), so IMHO it makes sense to split, 
>>> now that we have the ability to do so.
>>>
>>> Cheers
>>> Maurizio
>>>
>>> On 14/01/2020 15:05, Jorn Vernee wrote:
>>>> Adding Robin to CCs again, this time without a typo in the email 
>>>> address.
>>>>
>>>> Jorn
>>>>
>>>> On 14/01/2020 15:58, Jorn Vernee wrote:
>>>>> Hi all,
>>>>>
>>>>> You might have heard that there is an OpenJDK project named Skara 
>>>>> evaluating and trialing using Git for OpenJDK and GitHub for 
>>>>> hosting the repositories [1]. We have been asked to try out Git, 
>>>>> GitHub and the Skara tooling, as a means of validating, and to 
>>>>> provide feedback about the Project Skara effort. There is already 
>>>>> a number of OpenJDK projects using Git, GitHub and Skara:
>>>>> - OpenJFX
>>>>> - OpenJMC
>>>>> - Loom
>>>>> - Mobile
>>>>> - Skara
>>>>>
>>>>> A transition entails switching to Git as an SCM (see the Git 
>>>>> manual [2]), and the repository would be hosted on GitHub [3]. 
>>>>> After the transition, the current Mercurial repository would no 
>>>>> longer be updated. There is currently already a read-only mirror 
>>>>> in place [4], which you can use to try out Git and some of the 
>>>>> tooling, though submitting pull requests and pushing there are 
>>>>> currently not supported.
>>>>>
>>>>> I suggest that project Panama transition to git, GitHub and Skara 
>>>>> and that we set the target date for the transition to around 2 
>>>>> weeks from now. For example Monday the 27th of January, or 
>>>>> otherwise later if people need more time to prepare. I also 
>>>>> suggest we adopt GitHub's pull request workflow together with the 
>>>>> bots from project Skara.
>>>>>
>>>>> Adopting pull requests and the Skara bots means that the review 
>>>>> process would work partly through GitHub. In particular, all 
>>>>> changes must start out as pull requests. Skara automatically 
>>>>> generates webrevs, "RFR" emails and supports bi-directional 
>>>>> syncing between mailing lists and GitHub for those that prefer 
>>>>> using webrev and the mailing lists. If you are unfamiliar with 
>>>>> GitHub and pull requests, I suggest checking out GitHub's guide 
>>>>> [5]. Note that project Skara also provides CLI tools for 
>>>>> interacting with GitHub for those that prefer working from a 
>>>>> terminal. You can find more info about these tools on the Skara 
>>>>> wiki page [6] or from the Skara README [7].
>>>>>
>>>>> One question I would like to discuss is whether we should split 
>>>>> the current repository into two; one repository for the ffi work 
>>>>> and one repository for the vector API work (named e.g. panama-ffi 
>>>>> and panama-vector). Having these two distinct features in separate 
>>>>> repositories might make it easier for newcomers and followers to 
>>>>> understand where the latest changes are. We would still share the 
>>>>> same mailing list, but having two repositories would separate the 
>>>>> streams of traffic on GitHub, i.e. each project would have it's 
>>>>> own, separate, set of pull requests.
>>>>>
>>>>> If you have any comments or questions regarding this transition, 
>>>>> please reply to this thread.
>>>>>
>>>>> Thanks,
>>>>> Jorn
>>>>>
>>>>> [1] : https://openjdk.java.net/jeps/369 [2] :
>>>>> https://git-scm.com/docs/user-manual
>>>>> [3] : https://github.com/
>>>>> [4] : https://github.com/openjdk/panama [5] :
>>>>> https://guides.github.com/introduction/flow/
>>>>> [6] : https://wiki.openjdk.java.net/display/SKARA/Skara
>>>>> [7] : https://github.com/openjdk/skara
>>>>>
>>>>>
>>