The RI usually is, those are developed under Glassfish. And every JSR that
uses java.net with Git or SVN also is Open Source. You won't find certain
artifacts, e.g. TCKs for several JSRs (usually Oracle lead;-) or everything
on the ME Embedded side like JSR 360/361. All others are usually Open
Source, and look at JSRs like 107, Oracle as Co Spec Lead also contributed
to that. Or WebSockets, etc.
Should be same, license model of JSON-P and WebSockets are practically
identical, too.
Werner
On Mon, Mar 9, 2015 at 4:49 PM, Jean-Louis Monteiro <
jlmonteiro_at_tomitribe.com> wrote:
> either way is fine.
>
> Unlike Bean Validation or CDI, the specification proposal hasn't been
> tagged as open source for specification, RI and TCK, isn't it?
> If so, not sure github is an option.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Mon, Mar 9, 2015 at 11:58 AM, Rudy De Busscher <rdebusscher_at_gmail.com>
> wrote:
>
>> +1 for Github as main repository
>>
>> On 9 March 2015 at 11:33, Werner Keil <werner.keil_at_gmail.com> wrote:
>>
>>> Seems the 375 repo is so far empty, so unless Oracle policy prevented
>>> it, using GitHub as primary repo (like JSR 107 did) could also be a
>>> question worth asking.
>>>
>>> Or if possible chose GitHub as "leading" repo and mirror it to java.net
>>> instead of the other way round;-)
>>>
>>> On Mon, Mar 9, 2015 at 11:31 AM, Werner Keil <werner.keil_at_gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Seems, Pavel (who may not be observing this list, so I added him) did
>>>> this a few times to mirror java.net (usually Git) repos to GitHub. For
>>>> WebSockets and Tyrus RI or helping "next door number" JSR 374 to do the
>>>> same.
>>>> Maybe he can share his experience with this JSR and Spec Lead, too.
>>>>
>>>> Regards,
>>>> Werner
>>>>
>>>>
>>>> On Sun, Mar 8, 2015 at 10:46 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Sun, Mar 8, 2015 at 10:31 PM, David Blevins <dblevins_at_tomitribe.com>
>>>>> wrote:
>>>>> > That works. If we can get one for misc stuff, prototypes, crazy
>>>>> ideas, presentations or other sharables that'd be awesome.
>>>>> >
>>>>> > Yes, I'd certainly take github if it was on the table. :)
>>>>>
>>>>> We can of course always create a mirror on GitHub. This might make it
>>>>> easier to do some public experiments in forks and it'll give you some
>>>>> extra goodies like diffs and atom feeds etc which I think the Java.net
>>>>> http interface doesn't offer.
>>>>>
>>>>> I created my own one for jsr372 as well (but there it was an
>>>>> absolutely necessity since jsr372 still uses svn).
>>>>>
>>>>> Kind regards,
>>>>> Arjan Tijms
>>>>>
>>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> > -David
>>>>> >
>>>>> > On Mar 8, 2015, at 2:20 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>>>> wrote:
>>>>> >
>>>>> >> Hi David,
>>>>> >>
>>>>> >> I noticed these three repos where mentioned:
>>>>> >>
>>>>> >> * git://java.net/javaee-security-spec~api
>>>>> >> * git://java.net/javaee-security-spec~spec
>>>>> >> * git://java.net/javaee-security-spec~web
>>>>> >>
>>>>> >> I'd personally prefer GitHub though ;)
>>>>> >>
>>>>> >> Kind regards,
>>>>> >> Arjan Tijms
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Sun, Mar 8, 2015 at 10:04 PM, David Blevins <
>>>>> dblevins_at_tomitribe.com> wrote:
>>>>> >>> Hey all,
>>>>> >>>
>>>>> >>> Wondering if we might get a repo we can all work in? Email is
>>>>> great for pasting code examples and potential api classes, but it can be
>>>>> hard to track over time.
>>>>> >>>
>>>>> >>> Possibly something like this:
>>>>> >>>
>>>>> >>> - https://github.com/cdi-spec/cdi
>>>>> >>>
>>>>> >>> Anything that helps us collaborate better seems like a great
>>>>> asset. I personally don't care where it lives (java.net, github,
>>>>> wherever), more after the central collaboration.
>>>>> >>>
>>>>> >>>
>>>>> >>> Thoughts?
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> David Blevins
>>>>> >>> http://twitter.com/dblevins
>>>>> >>> http://www.tomitribe.com
>>>>> >>> 310-633-3852
>>>>> >>>
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>