Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-vision] Developer's Platform Vision Meeting, Jan 14 at 11:30 ET.

Minutes from today's meeting.

In attendance:

Wayne Beaton
Dani Megert
Martin Lippert

(thanks for joining).

We kept it short today.

The vision statement is done. We can reopen that discussion if there is will do so, but we really do need to move onto strategy.

Our strategy in the Mars time frame is primarily on desktop Eclipse and Orion. Che is starting the initial contribution process, so they'll likely be in a bigger part of our focus in "N" time frame.

We are shifting focus from enabling extenders to enabling users. This does not mean that we're abandoning extenders by any means, but rather that we are going to focus attention on the "little things" that drive our user community crazy. By changing this focus, we hope to increase the coolness factor and grow the pool of potential contributors. The hope is that we'll be able to leverage the resulting good will to tackle bigger things in future years.

The Platform team is working with the Oomph team to ensure that the development environment is provisioned correctly. The contribution documentation [1] will be updated accordingly.

I've been doing some testing of my own. I've opened a handful of bugs against Oomph (with assistance from the error reporter). The most troubling bug I've encountered is that Oomph seems to fail silently when you don't specify Git/Gerrit credentials correctly. On an even more worrisome note, my machine seems to grind to a halt while it's trying to replicate with invalid credentials.

In the process doing my testing, I tackled Bug 162006 [2] and have contributed a patch via Gerrit. I'm a little concerned that there has been no feedback on either (I did only submit the patch five days ago, so I'm not quite ready to push the panic button).

Aside: I think that I may have sorted out that it is a best practice with Oomph to restrict the number of repositories you clone as part of the provisioning process to just those that you need. Consider environments transient; build them in the form that you need them as you need them and destroy them when you're done. Maybe this is obvious.

The Oomph installer will be "front and centre" as the primary download on our download page. Existing packages will also be present, but will be presented less prominently. It is my hope/expectation that the package downloads will disappear completely over time (years) as people overwhelmingly start to depend on the installer. We need this to happen for M5 to ensure that more testing occurs and start the socialization process.

Use the term "Great Fix" rather than "Great Bug". "Great Fix" is more positive and is more suggestive of actual code contribution.

I've created an "Every Detail Matters" [3] and "Great Fix" page [4]. I've also started stirring up trouble on Bug 457087 [5]. Based on some initial push back, I'm expecting some controversy with regard to feature names. Specifically, I am of the opinion that project names are generally code names and thus should not be included in any UI (descriptive names such as "Java development tools" are an obvious exception). There's more in the wiki [6].

The Platform team already runs Bug Days. We need to leverage this and expand our advertising of it.

Orion is mature technology. I'm not sure if they participate in the bug day activities, but if not they should be encouraged to do so.

We're not sure if there's anything that we can do regarding Flux at the moment.

We will continue to have bi-weekly meetings, starting at 11am ET on Wednesday. These meetings are intended to be a checkpoint to make sure that we're on track and keep everybody informed of progress. I'll put a meeting notice on the mailing list.

We need to identify a Web Tools contact to join this effort.

Action items (all Wayne):

* Identify a Web Tools representative;
* Complete the "Every Detail Matters" page;
* Complete the "Great Fix" page and start the advertising process (get committers on board);
* Ensure that the web team is pushing the Oomph-based installer front and centre for M5;

Let me know if I've missed or misrepresented anything.

Wayne

[1] https://wiki.eclipse.org/Platform_UI/How_to_Contribute
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=162006
[3] https://wiki.eclipse.org/Every_Detail_Matters
[4] https://wiki.eclipse.org/Every_Detail_Matters/Great_Fix
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457087
[6] https://wiki.eclipse.org/SimRel/Feature_Categories

On 13/01/15 10:38 PM, Wayne Beaton wrote:
We're meeting tomorrow (Wednesday) at 11:30 ET for thirty minutes.

Phone numbers

North America 1-866-569-4992
Germany 49-692-2224-6059
France 33-(0)-17-070-8535
UK 0800-033-7806
Switzerland 41-44-580-2115
Sweden 46-85-063-8386
Italy 003-902-3604-8268

Then enter the participant conference extension: 430, then enter pin 4718
Alternatively, SIP clients can call 430@xxxxxxxxxxxxxxxxxxxx, then enter pin 4718

Here is the vision statement:

Our vision is to build leading desktop and cloud-based development solutions, but more importantly to offer a seamless development experience across them. Our goal is to ensure that developers will have the ability to build, deploy, and manage their assets using the device, location and platform best suited for the job at hand. Eclipse projects, the community, and ecosystem will all continue to invest in and grow desktop Eclipse. Full-function cloud-based developer tools delivered in the browser will emerge and revolutionize software development.

Continued focus on quality and performance, out-of-the-box experience, Java 9, and first class Maven, Gradle, and JVM Languages support also figure prominently in our vision of a powerful developer’s platform.

There is more background in the article I wrote for the November newsletter [0]

Agenda:

We only have thirty minutes for this meeting, so we'll move things along as quickly as possible.

* Implementation strategy
* "Great Bugs" for Mars
* Meeting schedule; timing of this meeting.
* Who else do we need to invite?

Strategy notes/thoughts:

* Most of our energy in the Mars time-frame will be focused on desktop
* What do we need to do for Orion and Flux in the Mars time-frame?
* Grow "coolness" to grow field of contributors/attract contribution
* Focus on the user
* Every Detail Matters for Mars [1]
* Website improvements (make packages easier to find)
* Installation (Ooomph) [2] (make packages easier to install; make the Oomph-based installer the main download)
* Reduce Friction for Committers [3]
* What are we going to do about Maven?

Action Items:

* Engage the Web Tools PMC (representative needed for this group)
* Create/provision/on-board Gradle [4]
* On-board Che [5]

Wayne

[0] https://www.eclipse.org/community/eclipse_newsletter/2014/november/article4.php
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457087
[2] https://projects.eclipse.org/proposals/eclipse-plug-ins-gradle
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435599
[4] https://projects.eclipse.org/proposals/eclipse-plug-ins-gradle
[5] https://projects.eclipse.org/projects/technology.che

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon 2015

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon
          2015

Back to the top