( Note doodle poll for follow-up meeting week of August 20-27:
https://doodle.com/poll/424g8efu9zzbiu8m
)
Attendees
Fujitsu: Kenji Kazamura
IBM: Dan Bandera
Oracle: Will Lyons
Payara: Steve Millidge
Red Hat: Scott Stark (joined towards end of meeting)
Tomitribe: Richard Monson-Hafael
Simon Maple
Ivar Grimstad
The discussion focused on review of Mike Milinkovich's email sent
on August 2 and appended below.
IBM, Fujitsu, Simon, Ivar felt Mike's email proposal was
reasonable.
Oracle's feedback was that the steady-state budget should be
closer to $1.5M. Will request input on budgets for similar
initiatives in other foundations as comparisons for Mike's budget
proposal.
Red Hat and Payara are concerned on the ability to execute based
on lack of progress on legal matters. Would like to see a
proposal to resolve the current roadblocks to evolving the javax
namespace.
Payara and Tomitribe felt the overall magnitude of the budget felt
large, but would like more input based on the expertise of the
large vendors.
Tomitribe would like to see a plan for ramping up participant
contributions.
Attendees agreed to review the proposal below within their
organizations and be prepared to discuss these proposals during a
meeting the week of August 20-27. A doodle poll has been opened
to schedule this meeting.
https://doodle.com/poll/424g8efu9zzbiu8m
Will
On 8/2/18 9:49 AM, Mike Milinkovich
wrote:
All,
For the Jakarta EE budget call today I would like to make
the conversation more concrete than it has been up to this
point.
- The Specification Process is in some disarray. So as of
this moment, we cannot commit to a specific release date
for innovative new Jakarta EE technologies in 2019. Given
that, we think that it does not make sense to approach
this budget conversation with any number higher than
Option 1, as shown below. So that means a $1.5M target
budget.
- Given the members around the table, the dues provided to
use should total $1.0M and $1.2M, leaving us with a $450K
to $250K gap that is going to have to be filled with
additional recruitment. But until that recruitment
happens, we have less than the anticipated budget to
spend.
- Based on the above we (the EMO) will construct a budget
that is a simple 50-50 split between headcount and program
spend. But to do that will require to Steering and
Marketing Committees to do more work on prioritization
than they have done to date. This makes the Program Plan
conversation more relevant, as we think that's the vehicle
to drive the prioritization conversation.
- We will be looking for a three year commitment from the
members in order to provide for the certainty we need to
hire staff. This will require the development of a Jakarta
EE WG participation agreement.
- Of course, all of the above will require each company to
obtain internal budget approvals for the amounts.
Looking forward to our discussion.
|
Corporate Revenue
|
OPTION 1:
Annual Fees
$1.5M Target Budget
|
OPTION 2:
Annual Fees $2.5M Target Budget
|
OPTION 3:
Annual Fees
$3M Target Budget
|
|
Annual Corporate Revenues greater than $1 billion
|
$300,000
|
$500,000
|
$600,000
|
|
Annual Corporate Revenues greater than $500 million but less than or equal to $1 billion
|
$200,000
|
$300,000
|
$400,000
|
|
Annual Corporate Revenues greater than $100 million but less than or equal to $500 million
|
$100,000
|
$200,000
|
$300,000
|
|
Annual Corporate Revenues greater than $10 million but less than or equal to $100 million
|
$50,000
|
$75,000
|
$100,000
|
|
Annual Corporate Revenues less than or equal to $10 million
|
$25,000
|
$25,000
|
$25,000
|
![Avast logo]() |
This email has been checked for
viruses by Avast antivirus software.
www.avast.com
|
_______________________________________________
jakarta.ee-steering mailing list
jakarta.ee-steering@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-steering
