From mark.reinhold at oracle.com  Fri Apr  5 19:02:38 2013
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Fri,  5 Apr 2013 12:02:38 -0700 (PDT)
Subject: JEP 182: Policy for Retiring javac -source and -target Options
Message-ID: <20130405190238.5C0DC1733@eggemoggin.niobe.net>

Posted: http://openjdk.java.net/jeps/182

- Mark


From omajid at redhat.com  Mon Apr  8 21:32:34 2013
From: omajid at redhat.com (Omair Majid)
Date: Mon, 08 Apr 2013 17:32:34 -0400
Subject: Inconsistency between Projects page and Bylaws
Message-ID: <51633772.7050500@redhat.com>

Hi,

I noticed that there is some inconsistency between the bylaws [1] and
the projects page [2] in how Reviewers are nominated. The bylaws say:

"""
A Reviewer for a Project may nominate any of that Project?s Committers
to be a new Reviewer for that Project. Such nominations are approved by
a Three-Vote Consensus of the Project?s Reviewers.
"""

while the projects page says:

"""
Any Project Reviewer may nominate any of the Project's Committers to be
a Project Reviewer of the same Project.
<snip>
    Send a call-for-votes to the Project's OpenJDK mailing list. The
voting method for approval is Lazy Consensus and only current Reviewers
are eligible to vote.
"""

The project page clearly states that "if there is a conflict between
this page and the Bylaws then the Bylaws are considered authoritative."
But I think it makes sense to fix the projects page anyway to avoid
confusion.

Thanks,
Omair

[1] http://openjdk.java.net/bylaws#reviewer
[2] http://openjdk.java.net/projects/#project-reviewer

-- 
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


From iris.clark at oracle.com  Fri Apr 12 18:11:41 2013
From: iris.clark at oracle.com (Iris Clark)
Date: Fri, 12 Apr 2013 11:11:41 -0700 (PDT)
Subject: Inconsistency between Projects page and Bylaws
In-Reply-To: <51633772.7050500@redhat.com>
References: <51633772.7050500@redhat.com>
Message-ID: <afb29c9a-0650-4f1a-b0fb-39810a9f821b@default>

Hi, Omair.

Good catch.  The intention is that the Project overview page [1] always be consistent with the Bylaws.  The statement at the top is there just in case there are errors such as this one.

I've appended the diff I applied to the Project page last night.  Please let me know if I missed anything.

Thanks!
iris

[1]: http://openjdk.java.net/projects

-----

--- a/src/projects/index.html Thu Apr 11 23:35:11 2013 -0700
+++ b/src/projects/index.html Thu Apr 11 23:45:02 2013 -0700
@@ -305,7 +305,7 @@ Reviewer. </p>
<dd> <p> Send a call-for-votes to the Project's OpenJDK <a
href="http://mail.openjdk.java.net">mailing list</a>. The voting method for
- approval is <a href="http://openjdk.java.net/bylaws#lazy-consensus">Lazy
+ approval is <a href="/bylaws#three-vote-consensus">Three-Vote
Consensus</a> and only current <a href="/census">Reviewers</a> are eligible
to vote.</p>
@@ -322,7 +322,7 @@ this nomination. Votes must be cast in
this nomination. Votes must be cast in the open by replying to
this mailing list.
-For Lazy Consensus voting instructions, see [2].
+For Three-Vote Consensus voting instructions, see [2].
<b>&lt;nominator&gt;</b>


-----Original Message-----
From: Omair Majid [mailto:omajid at redhat.com] 
Sent: Monday, April 08, 2013 2:33 PM
To: discuss at openjdk.java.net
Subject: Inconsistency between Projects page and Bylaws

Hi,

I noticed that there is some inconsistency between the bylaws [1] and the projects page [2] in how Reviewers are nominated. The bylaws say:

"""
A Reviewer for a Project may nominate any of that Project?s Committers to be a new Reviewer for that Project. Such nominations are approved by a Three-Vote Consensus of the Project?s Reviewers.
"""

while the projects page says:

"""
Any Project Reviewer may nominate any of the Project's Committers to be a Project Reviewer of the same Project.
<snip>
    Send a call-for-votes to the Project's OpenJDK mailing list. The voting method for approval is Lazy Consensus and only current Reviewers are eligible to vote.
"""

The project page clearly states that "if there is a conflict between this page and the Bylaws then the Bylaws are considered authoritative."
But I think it makes sense to fix the projects page anyway to avoid confusion.

Thanks,
Omair

[1] http://openjdk.java.net/bylaws#reviewer
[2] http://openjdk.java.net/projects/#project-reviewer

--
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


From linuxhippy at gmail.com  Sat Apr 13 08:21:20 2013
From: linuxhippy at gmail.com (Clemens Eisserer)
Date: Sat, 13 Apr 2013 10:21:20 +0200
Subject: Where to find the source of the closed-source browser plugin?
Message-ID: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>

Hi,

I am trying to hunt down some weird bug in the jar-file caching logic of
the closed-source java-plugin, however I wasn't successful in obtaining the
sources.
Of course I prefer icedtea-web, unfourtunatly it isn't installed on all
those windows machines ;)

If I remember correctly there were some special-licensed bundles available
before openjdk arrived, wonder what happend to these.

Thanks for any pointers...

- Clemens


From philip.race at oracle.com  Sat Apr 13 23:12:53 2013
From: philip.race at oracle.com (Phil Race)
Date: Sat, 13 Apr 2013 16:12:53 -0700
Subject: Where to find the source of the closed-source browser plugin?
In-Reply-To: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>
References: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>
Message-ID: <5169E675.2090606@oracle.com>

The source of the plugin has never been available in any form or under 
any license.
SFAIK I know we never even licensed it commercially.

-phil.

On 4/13/13 1:21 AM, Clemens Eisserer wrote:
> Hi,
>
> I am trying to hunt down some weird bug in the jar-file caching logic of
> the closed-source java-plugin, however I wasn't successful in obtaining the
> sources.
> Of course I prefer icedtea-web, unfourtunatly it isn't installed on all
> those windows machines ;)
>
> If I remember correctly there were some special-licensed bundles available
> before openjdk arrived, wonder what happend to these.
>
> Thanks for any pointers...
>
> - Clemens



From philip.race at oracle.com  Sun Apr 14 01:23:34 2013
From: philip.race at oracle.com (Phil Race)
Date: Sat, 13 Apr 2013 18:23:34 -0700
Subject: Where to find the source of the closed-source browser plugin?
In-Reply-To: <5169E675.2090606@oracle.com>
References: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>
	<5169E675.2090606@oracle.com>
Message-ID: <516A0516.7090909@oracle.com>

On 4/13/13 4:12 PM, Phil Race wrote:
> The source of the plugin has never been available in any form or under 
> any license.
> SFAIK I know we never even licensed it commercially.

To correct myself on the second statement, some platform vendors did 
have commercial licenses
to at least some parts of plugin, but I've no idea if that included 
Windows specific parts of it.

However the main point that the source wasn't generally available remains ..

-phil.

>
> -phil.
>
> On 4/13/13 1:21 AM, Clemens Eisserer wrote:
>> Hi,
>>
>> I am trying to hunt down some weird bug in the jar-file caching logic of
>> the closed-source java-plugin, however I wasn't successful in 
>> obtaining the
>> sources.
>> Of course I prefer icedtea-web, unfourtunatly it isn't installed on all
>> those windows machines ;)
>>
>> If I remember correctly there were some special-licensed bundles 
>> available
>> before openjdk arrived, wonder what happend to these.
>>
>> Thanks for any pointers...
>>
>> - Clemens
>



From linuxhippy at gmail.com  Sun Apr 14 09:19:43 2013
From: linuxhippy at gmail.com (Clemens Eisserer)
Date: Sun, 14 Apr 2013 11:19:43 +0200
Subject: Where to find the source of the closed-source browser plugin?
In-Reply-To: <516A0516.7090909@oracle.com>
References: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>
	<5169E675.2090606@oracle.com> <516A0516.7090909@oracle.com>
Message-ID: <CAFvQSYRNTbrv-32jmD_PSSM4Nx4de7ZH=Byee+J-N4YyXMu2Mg@mail.gmail.com>

Hi Phil,

>> The source of the plugin has never been available in any form or under any
>> license.

Thanks for the clarification - I remembered fixing a WebStart issue as
part of the "JDK Collaboration Project" some years ago, so I thought
the plugin was available under the same terms.

> However the main point that the source wasn't generally available remains ..

This is quite unfortunate, working at bytecode level is something I
don't enjoy a lot ...

Regards, Clemens


From jwrgorman at gmail.com  Tue Apr 16 11:46:17 2013
From: jwrgorman at gmail.com (jwrgorman)
Date: Tue, 16 Apr 2013 04:46:17 -0700 (PDT)
Subject: SolarNetwork: renewable energy management framework
Message-ID: <1366112777496-128167.post@n7.nabble.com>

Hi,

If anyone is interested in a project that involves renewable energy
management - SolarNetwork is a Java-based platform focusing on the
acquisition, storage, visualization and analysis of primarily solar energy
data but open to all renewable energy management.  We use a set of
enterprise frameworks as components, such as Spring and OSGi, but the core
idea is to be able to reliably and affordbably capture renewable energy data
from a host of inverters, charge controllers, battery computers, industrial
switches, and kilowatt-hour meters and persist that data on a web-based
server ?in the cloud? as well as expose web services for both visualization
and control.

Everything needed is on Github here licensed under the GPL:

https://github.com/SolarNetwork/solarnetwork/wiki/Developer-Guide

Thanks, John



--
View this message in context: http://openjdk.5641.n7.nabble.com/SolarNetwork-renewable-energy-management-framework-tp128167.html
Sent from the OpenJDK General discussion mailing list archive at Nabble.com.


From gnu.andrew at redhat.com  Wed Apr 24 17:03:28 2013
From: gnu.andrew at redhat.com (Andrew Hughes)
Date: Wed, 24 Apr 2013 13:03:28 -0400 (EDT)
Subject: Where to find the source of the closed-source browser plugin?
In-Reply-To: <CAFvQSYRNTbrv-32jmD_PSSM4Nx4de7ZH=Byee+J-N4YyXMu2Mg@mail.gmail.com>
References: <CAFvQSYSZwkAccAAL+Oh-=Du2WohrM3+_d35q6qUM29n1gA1Rpw@mail.gmail.com>
	<5169E675.2090606@oracle.com> <516A0516.7090909@oracle.com>
	<CAFvQSYRNTbrv-32jmD_PSSM4Nx4de7ZH=Byee+J-N4YyXMu2Mg@mail.gmail.com>
Message-ID: <1886909540.2834030.1366823008356.JavaMail.root@redhat.com>



----- Original Message -----
> Hi Phil,
> 
> >> The source of the plugin has never been available in any form or under any
> >> license.
> 
> Thanks for the clarification - I remembered fixing a WebStart issue as
> part of the "JDK Collaboration Project" some years ago, so I thought
> the plugin was available under the same terms.
> 
> > However the main point that the source wasn't generally available remains
> > ..
> 
> This is quite unfortunate, working at bytecode level is something I
> don't enjoy a lot ...
> 

It might be easier to just get IcedTea-Web running on Windows ;)

> Regards, Clemens
> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07