Christopher Guindon's bloghttps://blogs.eclipse.org/blogs/christopher-guindon
enEclipse IoT Website Redesignhttps://blogs.eclipse.org/post/christopher-guindon/eclipse-iot-website-redesign
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The <a href="https://iot.eclipse.org">Eclipse IoT</a> website redesign is now live! This project was a <a href="https://github.com/EclipseFdn/iot.eclipse.org/pull/339">huge undertaking</a> for us; we added 5,245 lines of code, closed <a href="https://github.com/EclipseFdn/iot.eclipse.org/projects/3#column-6757970">15 issues</a>, removed 82,361 lines of code and made <a href="https://github.com/EclipseFdn/iot.eclipse.org/pull/339/commits">84 commits</a>.</p>
<p><img src="https://www.chrisguindon.com/uploads/iot-2020.png" alt="Eclipse IoT Homepage" /></p>
<p>Yes, you got that right, the end result was <strong>-77,116 lines of code</strong> because we took the opportunity to clean up our codebase.</p>
<p>To kickoff this initiative, the community help us define the <a href="https://github.com/EclipseFdn/iot.eclipse.org/issues/179">goals</a> for this project:</p>
<ol>
<li><strong>Improve our information architecture</strong>: <br />
Led by <a href="https://accounts.eclipse.org/users/fdesbiens">Frédéric Desbiens</a>, the Eclipse IoT community created a new <a href="https://github.com/EclipseFdn/iot.eclipse.org/files/3591212/iot.eclipse.org.new.structure.v2.pdf">structure</a> for the website.</li>
<li><strong>Contribute to the recruitment of new members and adopters</strong>: <br />
<a href="https://iot.eclipse.org/adopters/">Adopters</a> and <a href="https://iot.eclipse.org/membership/">Members</a> are now top-level menu items. We also created a new “<a href="https://iot.eclipse.org/adopters/how-to-be-listed-as-an-adopter/">How to be Listed as an Adopter</a>” page.</li>
<li><strong>Ensure the website cathers to both technical and non-technical visitors</strong>: <br />
We made some big improvements to our <a href="https://iot.eclipse.org/community/">Community</a> and <a href="https://iot.eclipse.org/community/resources/">Resources</a> sections. These sections cathers to both technical and non-technical users since you can find Case-Studies, Market Reports, Videos, White Papers and some additional information on how you can stay informed about what&rsquo;s currently going on with Eclipse IoT.</li>
<li><strong>Drive adoption for our technologies</strong>: <br />
We now fetch project information from the <a href="https://projects.eclipse.org">Eclipse PMI</a> each time we push a change to the website. Our stale project page is now a thing of the past!</li>
</ol>
<p>In an effort to communicate our project plans with our community, we created a public <a href="https://github.com/EclipseFdn/iot.eclipse.org/projects/3">GitHub project</a> with <a href="https://github.com/EclipseFdn/iot.eclipse.org/milestones">two milestones</a>.</p>
<p>Being open and transparent allows us to natually inform our communities about our efforts and we think it&rsquo;s a great way for us to collaborate and share tasks. As the project manager, this workflow allows me to ensure that the project is moving forward as planned.</p>
<p>We also created a set of <a href="https://www.eclipse.org/artwork/zip_file_v2/Eclipse-IoT-Brand-Guidelines.pdf">brand guidelines</a> for the Eclipse IoT Working Group. These guidelines include the brand font (Roboto), logo variations, color swatches, and acceptable logo treatments. This will help us consistently deploy the brand across different digital and print channels as well as Eclipse IoT events.</p>
<p>Overall, I am very happy with this new redesign! A huge thank you to <a href="https://accounts.eclipse.org/users/epoirier">Eric Poirier</a>, <a href="https://accounts.eclipse.org/users/mjoanisse4m4">Matt Joanisse</a>, a graphic designer hired by the Foundation to work on the site, <a href="https://accounts.eclipse.org/users/cwitt">Christie Witt</a>, <a href="https://accounts.eclipse.org/users/jspeedn7e">Joe Speed</a>, <a href="https://accounts.eclipse.org/users/fdesbiens">Frédéric Desbiens</a> and <a href="https://accounts.eclipse.org/users/malowe">Martin Lowe</a>!</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/eclipse-iot-website-redesign/">https://www.chrisguindon.com/post/eclipse-iot-website-redesign/</a></div></div></div>Tue, 24 Mar 2020 14:12:32 +0000Christopher Guindon6784 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/eclipse-iot-website-redesign#commentsModernizing our GitHub Sync Toolsethttps://blogs.eclipse.org/post/christopher-guindon/modernizing-our-github-sync-toolset
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I am happy to announce that my team is ready to deploy a new version of our <a href="https://github.com/EclipseFdn/eclipsefdn-github-sync">GitHub Sync Toolset</a> on November 26, 2019 from 10:00 to 11:00 am EST.</p>
<p>We are not expecting any disruption of service but it&rsquo;s possible that some committers may lose write access to their Eclipse project GitHub repositories during this 1 hour maintenance window.</p>
<p>This toolset is responsible for syncronizing Eclipse committers accross all our GitHub repositories and on top of that, this new release will start syncronizing contributors.</p>
<p>In this context, a contributor is a GitHub user with read access to the project GitHub repositories. This new feature will allow committers to assign issues to contributors who currently don&rsquo;t have write access to the repository. This feature was requested in 2015 via <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=483563">Bug 483563</a> - Allow assignment of GitHub issues to contributors.</p>
<p>Eclipse Committers are reponsible for maintaining a list of GitHub contributors from their <a href="https://projects.eclipse.org/">project</a> page on the Eclipse Project Management Infrastructure (PMI).</p>
<p>To become an Eclipse contributor on a GitHub for a project, please make sure to tell us your <strong>GitHub Username</strong> in your <a href="https://accounts.eclipse.org/user/edit">Eclipse account</a>.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/modernizing-our-github-sync-script/">https://www.chrisguindon.com/post/modernizing-our-github-sync-script/</a></div></div></div>Tue, 19 Nov 2019 20:10:46 +0000Christopher Guindon6746 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/modernizing-our-github-sync-toolset#commentsShow Your Support for Open Source IoT at the Eclipse Foundationhttps://blogs.eclipse.org/post/christopher-guindon/show-your-support-open-source-iot-eclipse-foundation
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded">
<p>The <a href="https://iot.eclipse.org">Eclipse IoT</a> working group is launching a campaign to identify the adopters of Eclipse IoT open source projects. Companies — whether or not they are working group members — can be listed as <a href="https://iot.eclipse.org/adopters/">adopters</a>.</p>
<p>Adopters are organizations that voluntarily show their support for the Eclipse IoT projects they have adopted (i.e. shipping commercial products based on the projects and/or using the projects for non-commercial or internal reasons).</p>
<p>You can add your organization logo to our list of adopters by submitting a <a href="https://github.com/EclipseFdn/iot.eclipse.org/pulls">pull request</a> or by creating an <a href="https://github.com/EclipseFdn/iot.eclipse.org/issues/new?template=adopter_request.md">issue</a>. You can attach files to an issue by dragging and dropping them in the text editor of the form.</p>
<p>If you plan on submitting a pull request, you will need to make the following changes to the website codebase:</p>
<ol>
<li>Add a colored and a white organization logo to <a href="https://github.com/EclipseFdn/iot.eclipse.org/tree/master/static/assets/images/adopters">static/assets/images/adoptors</a>. We expect that all submitted logos to be transparent svg.</li>
<li>Update the adopter data file: <a href="https://github.com/EclipseFdn/iot.eclipse.org/blob/master/data/adopters.yml">data/adopters.yml</a> If your organization wishes to express support for multiple projects, you will need to add your organization&rsquo;s YAML definition to the adopters list of each of the relevant project nodes.</li>
</ol>
<p>Your participation in this initiative will publicly show your support for open source innovation.</p>
<h3 id="list-eclipse-iot-adopters-on-an-eclipse-project-website">List Eclipse IoT adopters on an Eclipse project website</h3>
<p>Eclipse projects can showcase the logos of their adopters on their project websites. We built a JavaScript plugin to make this process easier. If you are a project committer, here are quick instructions on how to use the <a href="https://iot.eclipse.org/assets/js/eclipsefdn.adopters.js">eclipsefdn-adopters.js</a> on your Eclipse project website:</p>
<h4 id="usage">Usage</h4>
<p>Include the plugin&rsquo;s JS in the <head> section of the page:</p>
<pre><code class="language-html">&lt;script src=&quot;//iot.eclipse.org/assets/js/eclipsefdn.adopters.js&quot;&gt;&lt;/script&gt;
</code></pre>
<p>Load the plugin:</p>
<pre><code>&lt;script&gt;
eclipseFdnAdopters.getList({
project_id: &quot;[project_id]&quot;
});
&lt;/script&gt;
</code></pre>
<p>Create an HTML element containing the chosen selector:</p>
<pre><code>&lt;div class=&quot;eclipsefdn-adopters&quot;&gt;&lt;/div&gt;
</code></pre>
<ul>
<li>By default, the selector&rsquo;s value is <code>eclipsefdn-adopters</code>.</li>
</ul>
<h4 id="options">Options</h4>
<pre><code>&lt;script&gt;
eclipseFdnAdopters.getList({
project_id: &quot;[project_id]&quot;,
selector: &quot;.eclipsefdn-adopters&quot;,
ul_classes: &quot;list-inline&quot;,
logo_white: false
});
&lt;/script&gt;
</code></pre>
<table>
<thead>
<tr>
<th>Attribute</th>
<th>Type</th>
<th>Default</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>project_id</code></td>
<td><em>String</em></td>
<td></td>
<td><strong>Required</strong>: Select adopters from a specific project ID.</td>
</tr>
<tr>
<td><code>selector</code></td>
<td><em>String</em></td>
<td><code>.eclipsefdn-adopters</code></td>
<td>Define the selector that the plugin will insert adopters into.</td>
</tr>
<tr>
<td><code>ul_classes</code></td>
<td><em>String</em></td>
<td></td>
<td>Define classes that will be assigned to the ul element.</td>
</tr>
<tr>
<td><code>logo_white</code></td>
<td><em>Boolean</em></td>
<td><code>false</code></td>
<td>Whether or not we use the white version of the logo.</td>
</tr>
</tbody>
</table></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/show-your-support-for-open-source-iot-at-the-eclipse-foundation/">https://www.chrisguindon.com/post/show-your-support-for-open-source-iot-at-the-eclipse-foundation/</a></div></div></div>Thu, 14 Nov 2019 16:35:00 +0000Christopher Guindon6744 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/show-your-support-open-source-iot-eclipse-foundation#commentsEclipse Foundation Contributor Validation Servicehttps://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-contributor-validation-service
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>In an effort to <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=540694">provide a more robust solution</a> to our Contributor Validation Service on GitHub, we created the <a href="https://github.com/apps/eclipse-eca-validation">Eclipse ECA Validation</a> Github App that can be installed on any GitHub account, organization or repository.</p>
<p>The goal of this new GitHub App is to make sure that every contributor is covered by the necessary legal agreements in order to contribute to all Eclipse Foundation Projects including <a href="https://www.eclipse.org/projects/efsp/#efsp-projects">specification projects</a>.</p>
<p>For example, all contributors must be covered by the <a href="https://www.eclipse.org/legal/ECA.php">Eclipse Foundation Contributor Agreement</a> (ECA) and they must include a &ldquo;Signed-off-by&rdquo; footer in commit messages. When contributing to an Eclipse Foundation Specification Project, contributors must be covered with version 3.0.0 or greater of the ECA.</p>
<figure class="thumbnail">
<img src="https://www.chrisguindon.com/uploads/validation-feedback.jpg"/>
</figure>
<p>We created a GitHub App to improve the following problems:</p>
<ol>
<li>Reduce our maintenance burden by simplifying the installation process.</li>
<li>Increase our API rate limit.</li>
<li>Create a better experience for users by allowing the App to be installed on non-Eclipse project repositories such as the <a href="https://github.com/EclipseFdn/iot.eclipse.org">Eclipse IoT website</a> and the <a href="https://github.com/jakartaee/jakartaee.github.io">Jakarta EE website</a>.</li>
</ol>
<p>Finally, we made some improvements to our “details” page. We added a “revalidate” button to allow Eclipse users to trigger a revalidation without pushing new changes to the pull-request and we added some useful links to allow users to return to GitHub or to sign the <a href="https://accounts.eclipse.org/user/eca">ECA</a>.</p>
<figure class="thumbnail">
<img src="https://www.chrisguindon.com/uploads/details-page.jpg"/>
</figure>
<p>We are planning to install our new Eclipse ECA Validation Github App to all our Eclipse Projects on GitHub this week and I am hoping that these changes will improve the way our users are contributing via Github.</p>
<p>If you are using our new Github App and you wish to contribute feedback, please do so on <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=540694">Bug 540694</a> - Github IP validation needs to be more robust.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/github-eclipse-eca-validation-service/">https://www.chrisguindon.com/post/github-eclipse-eca-validation-service/</a></div></div></div>Mon, 25 Feb 2019 23:20:46 +0000Christopher Guindon6674 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-contributor-validation-service#commentsEclipse Foundation Hosted Services Privacy and Acceptable Usage Policyhttps://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The Eclipse Foundation recently made available a new <a href="https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf">policy</a>
to make sure that our projects and hosted services are compliant with
the General Data Protection Regulation (GDPR).</p>
<p>The <a href="https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf">Eclipse Foundation Hosted Services Privacy and Acceptable Usage Policy</a> will provide guidance to folks who operate a virtual server or a website hosted either directly
by the Eclipse Foundation or provided via the Eclipse Foundation’s funding in support
of an Eclipse Foundation open source project.</p>
<p>We want to ensure that all such services meet the highest standards of privacy and transparency,
and to ensure that any collected data is used strictly in support of the activities of its open source projects.</p>
<p>There are two changes that we would like to highlight. First <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=534384#c6">we have updated our position</a>
on <a href="https://analytics.google.com/analytics/web/">Google Analytics (GA)</a>. Projects will now be allowed to create their own GA property,
provided they agree to the conditions listed in our new <a href="https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf">policy</a>.</p>
<p>Secondly we are better defining the responsibilities of the projects or committers
responsible for hosting a service or website with the Eclipse Foundation.</p>
<p>Hosted services and Eclipse Projects can adopt this new policy by creating an issue on Eclipse Bugzilla under <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&amp;component=Hosted%20Services%20Privacy%20and%20Acceptable%20Usage%20Policy">Community &gt; Hosted Services Privacy and Acceptable Usage Policy</a>
where they acknowledge reading and understanding the policy.</p>
<p>Those who wish to store Personally Identifiable Information (PII) must create and include a Data Protection Impact Assessment (DPIA) document.
The DPIA must describe what kinds of PII data will be collected and their purpose. This will have to be updated as your services evolve by
uploading a new version on Eclipse Bugzilla.</p>
<p>If a service wishes to retain PII for longer than 1 year, they must produce a <a href="https://www.chrisguindon.com/uploads/data-retention-policy-template.pdf">Data
Retention Policy (DRP)</a> that indicates how long they plan to keep each pieces of PII data
and why they need to keep them for that long.</p>
<p>For the complete list of requirements &amp; conditions, please make sure to read the <a href="https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf">Eclipse Foundation Hosted Services Privacy and Acceptable Usage Policy</a>.</p>
<p>Please let us know if you have any questions or concerns regarding this new policy by sending
your questions to <a href="mailto:privacy@eclipse.org">privacy@eclipse.org</a>.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy/">https://www.chrisguindon.com/post/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy/</a></div></div></div>Wed, 07 Nov 2018 20:30:00 +0000Christopher Guindon6659 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy#commentsNew improvements to the Eclipse Packaging websitehttps://blogs.eclipse.org/post/christopher-guindon/new-improvements-eclipse-packaging-website
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>In my previous <a href="https://www.chrisguindon.com/post/quicksilver-eclipse-org-redesign/">blog post</a>, we announced a new look and feel for the Eclipse Foundation website. The <a href="https://www.chrisguindon.com/post/quicksilver-eclipse-org-redesign/#future-plans">plan</a> was to roll out our new design to <a href="https://www.eclipse.org">eclipse.org</a> first and then gradually migrate our other web properties.</p>
<p>Since then, we migrated our <a href="https://github.com/eclipsefdn/hugo-solstice-theme">Hugo theme</a>, <a href="https://wiki.eclipse.org/Main_Page">Eclipsepedia</a>, <a href="https://www.eclipse.org/forums/">Eclipse Community Forums</a> and a few other Drupal sites, such as the <a href="https://accounts.eclipse.org/">Eclipse User Profile</a> and the <a href="https://blogs.eclipse.org/">Eclipse Foundation Blog</a> to the Quicksilver look and feel!</p>
<p>This week, I am happy to announce an update to the <a href="https://www.eclipse.org/downloads/packages/">Eclipse Packaging</a> website. For those who don&rsquo;t know, the Eclipse Packaging website is used to publish download links for the Eclipse Installer and Eclipse Packages.</p>
<p>I am very proud of the work done here since the original site desperately needed some TLC. I’m hoping the new look and feel will improve the way the Eclipse IDE is downloaded by the community!</p>
<p><img src="https://www.chrisguindon.com/uploads/before-and-after.jpg" alt="Eclipse.org new home page" title="Eclipse.org new home page" /></p>
<p>New features include:</p>
<ul>
<li>A website redesign based off the Quicksilver look and feel.</li>
<li>The links to the <a href="https://www.eclipse.org/downloads/packages/installer">Eclipse Installer</a>, <a href="https://www.eclipse.org/downloads/packages/">Eclipse Packages</a> and Eclipse Developer Builds are more accessible via a new submenu beneath our breadcrumbs.</li>
<li>Created a new <a href="https://www.eclipse.org/downloads/packages/installer">Eclipse Installer download page</a> page with instructions.</li>
<li>Made improvements to our breadcrumb links which allow users to easily find every <a href="https://www.eclipse.org/downloads/packages/release">Eclipse release</a> on the Eclipse Packaging site.</li>
<li>The <em>More Downloads</em> sidebar includes links to Eclipse Packages instead of the release train landing page.</li>
<li>Links to the Eclipse Installer is available in the sidebar.</li>
</ul>
<p>Finally, this migration is also a win for the Eclipse Foundation staff. These changes to the Eclipse Packages site allow us to streamline the Eclipse Release process and no longer requires us to manually submit Gerrit patches to publish a release.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/eclipse-epp-website-improvements/">https://www.chrisguindon.com/post/eclipse-epp-website-improvements/</a></div></div></div>Thu, 02 Aug 2018 14:30:00 +0000Christopher Guindon6635 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/new-improvements-eclipse-packaging-website#commentsEclipse Marketplace Client, Photon Edition not opening in certain caseshttps://blogs.eclipse.org/post/christopher-guindon/eclipse-marketplace-client-photon-edition-not-opening-certain-cases
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The Eclipse Marketplace Client, Photon edition has a bug where it fails to open in certain cases. If nothing happens when you try to access the Eclipse Marketplace via <strong>&ldquo;Help &gt; Eclipse Marketplace&rdquo;</strong>, please update the Marketplace Client plug-in by doing the following:</p>
<p><img src="https://www.chrisguindon.com/uploads/mpc-update.png" alt="Marketplace Client not opening in Photon" title="Marketplace Client not opening in Photon" /></p>
<ol>
<li>Go to Help &gt; Install New Software</li>
<li>Paste the Marketplace Client update site url into the &ldquo;Work with&rdquo; field: <strong><a href="http://download.eclipse.org/mpc/photon">http://download.eclipse.org/mpc/photon</a></strong></li>
<li>Select the &ldquo;EPP Marketplace Client&rdquo; checkbox</li>
<li>Follow the wizard and restart your Eclipse to finish the installation.</li>
</ol>
<p>We are working on providing an update to the Eclipse Photon release to distribute the fix through automatic updates and package downloads. In the meantime, please update manually if you are affected by this bug.</p>
<p>If you have any questions about this update process, please send an email to <a href="mailto:mpc-dev@eclipse.org">mpc-dev@eclipse.org</a>. For more technical details, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=536385">bug 536385</a>.</p>
<p>Blog post co-authored with <a href="https://www.eclipse.org/user/creckord">Carsten Reckord</a>.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/marketplace-client-not-opening-in-photon/">https://www.chrisguindon.com/post/marketplace-client-not-opening-in-photon/</a></div></div></div>Fri, 29 Jun 2018 14:30:00 +0000Christopher Guindon6633 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/eclipse-marketplace-client-photon-edition-not-opening-certain-cases#commentsQuicksilver: eclipse.org new look and feelhttps://blogs.eclipse.org/post/christopher-guindon/quicksilver-eclipseorg-new-look-and-feel
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded">
<p><img src="https://www.chrisguindon.com/uploads/eclipse-org-homepage.jpg" alt="Eclipse.org new home page" title="Eclipse.org new home page" /></p>
<p>I am pleased to announce a new look and feel for <a href="https://www.eclipse.org">www.eclipse.org</a>, codenamed <strong>Quicksilver</strong>, and a new logo for the Eclipse Foundation which Mike Milinkovich, the Executive Director of the Eclipse Foundation, has <a href="https://mmilinkov.wordpress.com/2018/04/10/eclipse-foundation-new-logo/">blogged</a> about.</p>
<p>The main goal of the redesign is to highlight the Eclipse Foundation as more than just the IDE it started with. We want the site to reflect the fact that the Foundation now represents a collection of working groups, open source projects, vendors and individual committers all collaborating in the same space to create innovative technologies.</p>
<p>We hope we have the balance right, making sure it remains easy for the millions of developers who visit our site to get to their desired downloads easily and quickly.</p>
<p>A Quicksilver prototype is available now via our <a href="https://staging.eclipse.org">public staging server</a>. This server is protected with basic access authentication. The username is <strong>testuser</strong> and <strong>plaintext</strong> is the password.</p>
<p>The main focus of this redesign was on the following pages:</p>
<ul>
<li><a href="https://staging.eclipse.org">Eclipse Foundation Homepage</a></li>
<li><a href="https://staging.eclipse.org/org/workinggroups/">Eclipse Working Groups</a></li>
<li><a href="https://staging.eclipse.org/org/value/">Business Value</a></li>
<li><a href="https://staging.eclipse.org/org/">Content pages</a></li>
</ul>
<p>You can participate and contribute to this project by submitting feedback on <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=533394">Bug 533394 - Quicksilver: eclipse.org new look and feel</a>.</p>
<p>Quicksilver is going to be available on <strong>April 19th, 2018</strong> for <a href="https://www.eclipse.org">www.eclipse.org</a> only. We will continue the rollout across our broader web properties over the coming weeks.</p>
<p>Technology-wise, Quicksilver is an extension of Solstice. Since this is not a complete overhaul of our existing codebase, we’re expecting the transition from Solstice to Quicksilver to be fairly straightforward. Website maintainers for Eclipse projects and working groups should know that the colors are going to change but we don’t expect to break any existing Eclipse project websites.</p>
<h2 id="future-plans">Future plans</h2>
<p>We plan on changing our look and feel gradually. The following tasks are going to get done after the initial release of Quicksilver:</p>
<ul>
<li>Drupal themes for <a href="https://marketplace.eclipse.org">Eclipse Marketplace</a>, <a href="https://projects.eclipse.org">Eclipse PMI</a> and <a href="https://accounts.eclipse.org">Eclipse User Profiles</a></li>
<li>New Hugo theme for static websites</li>
<li>Mediawiki theme for <a href="https://wiki.eclipse.org">Eclipsepedia</a></li>
<li>New theme for <a href="http://planeteclipse.org/planet/">Planet Eclipse</a></li>
<li>Updated header and footer for <a href="https://bugs.eclipse.org/bugs/">Eclipse Bugzilla</a>, <a href="https://git.eclipse.org/r/">Gerrit</a>, <a href="https://ci.eclipse.org/">Eclipse CI</a> and <a href="https://git.eclipse.org/c/">Eclipse Git repositories</a></li>
<li>New FUDforum theme for the <a href="https://eclipse.org/forums/">Eclipse Community Forums</a>.</li>
</ul>
<p>A lot of work needs to get done before this becomes available but I am very proud of the work we did so far for this project.</p>
<p>A huge thank you to Eric Poirier, Stephanie Swart, Thabang Mashologu, and the entire Eclipse Foundation staff!</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/quicksilver-eclipse-org-redesign/">https://www.chrisguindon.com/post/quicksilver-eclipse-org-redesign/</a></div></div></div>Tue, 10 Apr 2018 14:30:00 +0000Christopher Guindon6615 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/quicksilver-eclipseorg-new-look-and-feel#commentsSay Goodbye to the Eclipse Foundation Nova Themehttps://blogs.eclipse.org/post/christopher-guindon/say-goodbye-eclipse-foundation-nova-theme
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded">
<p>The Eclipse Foundation is planning on removing a few deprecated components from <a href="https://git.eclipse.org/r/plugins/gitiles/www.eclipse.org/eclipse.org-common">eclipse.org-common</a> in an effort to reduce our code base for <a href="https://www.eclipse.org/">www.eclipse.org</a>.</p>
<p>We are using <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526827">Bug 526827 - Fall clean up of eclipse.org-common</a> to track the following tasks:</p>
<ul>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=468336">Bug 468336 - Remove support for the Nova theme in eclipse.org-common</a></li>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526824">Bug 526824 - Remove yui from eclipse.org-common</a></li>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526825">Bug 526825 - Remove Services_JSON from eclipse.org-common</a></li>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526826">Bug 526826 - Remove JQuery from eclipse.org-common</a></li>
</ul>
<p>I believe this &ldquo;clean up&rdquo; exercise is our first step towards the execution of my long term plan for migrating our code base to follow recommendations from the <a href="http://www.php-fig.org/">PHP Framework Interop Group</a>. I will be writing about this subject in a future blog post but for now, you can take a look at <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=496514">Bug 496514 - PHP sites maintained by the EF should follow recommendations from the Framework Interop Group</a>.</p>
<h3 id="bug-468336-remove-support-for-the-nova-theme-in-eclipse-org-common">Bug 468336 - Remove support for the Nova theme in eclipse.org-common</h3>
<p>During the summer of 2014, my team was responsible for implementing the redesign of <a href="https://www.eclipse.org/">www.eclipse.org</a> via <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=432342">Bug 432342 - Eclipse.org Website Redesign 2014</a>. We created a new look and feel called <strong>Solstice</strong> and since then, we&rsquo;ve been busy migrating all of our web properties.</p>
<p><img src="https://www.chrisguindon.com/uploads/01-solstice.jpg" alt="Solstice look and feel" title="Solstice look and feel" /></p>
<p>Today, I am happy to announce that it’s finally time to retire the Eclipse Nova theme. We are planning on removing the Nova theme from <a href="https://git.eclipse.org/r/plugins/gitiles/www.eclipse.org/eclipse.org-common">eclipse.org-common</a> on <strong>December 5th, 2017</strong>.</p>
<p>The Solstice look and feel will become the default theme for all web pages that are currently being served with Nova.</p>
<p>This change will be affecting the following websites:</p>
<ul>
<li><a href="http://eclipse.org/10years/">Celebrating 10 years of Eclipse</a></li>
<li><a href="http://eclipse.org/amp/">Agent Modeling Platform</a></li>
<li><a href="http://eclipse.org/bpel/">PEL Designer Project</a></li>
<li><a href="http://eclipse.org/bpmn2-modeler/">BPMN2 Modeler</a></li>
<li><a href="http://eclipse.org/cdo/">CDO</a></li>
<li><a href="http://eclipse.org/cdt/">Eclipse CDT (C/C++ Development Tooling)</a></li>
<li><a href="http://eclipse.org/damos/">Damos</a></li>
<li><a href="http://eclipse.org/egf/">EGF</a></li>
<li><a href="http://eclipse.org/emf-refactor/">EMF Refactor</a></li>
<li><a href="http://eclipse.org/equinox/">Equinox</a></li>
<li><a href="http://eclipse.org/facet/">EMF Facet</a></li>
<li><a href="http://eclipse.org/fmc/">FMC - Fundamental Modeling Concepts</a></li>
<li><a href="http://eclipse.org/gef3d/">GEF3D</a></li>
<li><a href="http://eclipse.org/gemini/">Gemini</a></li>
<li><a href="http://eclipse.org/gemini/dbaccess/">Gemini DBAccess</a></li>
<li><a href="http://eclipse.org/gemini/jpa/">Gemini JPA</a></li>
<li><a href="http://eclipse.org/henshin/">Henshin</a></li>
<li><a href="http://eclipse.org/jwt/">Java Workflow Tooling (JWT)</a></li>
<li><a href="http://eclipse.org/libra/">Libra</a></li>
<li><a href="http://eclipse.org/m2e-wtp/">Maven Integration for WTP</a></li>
<li><a href="http://eclipse.org/mangrove/">Mangrove - SOA Modeling Framework</a></li>
<li><a href="http://eclipse.org/mmt/">Model to Model Transformation (MMT)</a></li>
<li><a href="http://eclipse.org/modeling/gmp/">Graphical Modeling Project (GMP)</a></li>
<li><a href="http://eclipse.org/modeling/mdt/">Model Development Tools (MDT)</a></li>
<li><a href="http://eclipse.org/mpc/">Marketplace Client</a></li>
<li><a href="http://eclipse.org/osee/">OSEE: The Open System Engineering Environment</a></li>
<li><a href="http://eclipse.org/pulsar/">Pulsar</a></li>
<li><a href="http://eclipse.org/r4e/">R4E</a></li>
<li><a href="http://eclipse.org/rt/">RT</a></li>
<li><a href="http://eclipse.org/skalli/">Skalli</a></li>
<li><a href="http://eclipse.org/soa/">SOA Platform Project</a></li>
<li><a href="http://eclipse.org/stem/">The Spatiotemporal Epidemiological Modeler (STEM) Project</a></li>
<li><a href="http://eclipse.org/tigerstripe/">Tigerstripe</a></li>
<li><a href="http://eclipse.org/tycho/">Tycho - Building Eclipse plug-ins with maven</a></li>
<li><a href="http://eclipse.org/uomo/">UOMo</a></li>
<li><a href="http://eclipse.org/vex/">Vex - A Visual Editor for XML</a></li>
</ul>
<p>Please use <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=468336">Bug 468336 - Remove support for the Nova theme in eclipse.org-common</a> to discuss any concerns regarding this change.</p></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/say-goodbye-to-the-eclipse-nova-theme/">https://www.chrisguindon.com/post/say-goodbye-to-the-eclipse-nova-theme/</a></div></div></div>Wed, 15 Nov 2017 14:30:00 +0000Christopher Guindon4254 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/say-goodbye-eclipse-foundation-nova-theme#commentsEclipse Foundation Webdev Report [Q3 2017]https://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-webdev-report-q3-2017
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded">
<p>A few months ago, I created a discussion on <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=519264">Eclipse Bugzila</a> about creating a new blog for the Eclipse Foundation Webdev team. The idea is to raise awareness about what we are currently working on and hopefully, in return, we will get some feedback from the community.</p>
<p>I am new to the blogging world and I am really excited to kick off this new challenge with this report.</p>
<p>My blog posts will be on the following topics:</p>
<ol>
<li>Quarterly reports on web developpement at the foundation;</li>
<li>Maintenance window calendar;</li>
<li>Web developpement tips and tricks for Eclipse projects;</li>
<li>Discussion on new features.</li>
</ol>
<p>Here&rsquo;s a top-level list of items that we worked on in Q3 2017:</p>
<ul>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#api-eclipse-org">Api.eclipse.org</a>
<ul>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-516914-create-public-documentation-for-api-eclipse-org-rest-api">Bug 516914 - Create public documentation for api.eclipse.org REST Api</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-502485-activity-tab-error-reports-from-aeri">Bug 502485 - Activity tab - Error reports from AERI</a></li>
</ul></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#eclipse-org">Eclipse.org</a>
<ul>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=519264">Bug 519264 - Create an Eclipse Foundation webdev blog</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#infra-2507-donate-campaign-plan-fall-2017">Infra 2507 - Donate Campaign Plan - Fall 2017</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-521084-add-epl-2-0-to-the-website">Bug 521084 - Add epl-2.0 to the website</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-261658-status-eclipse-org">Bug 261658 - status.eclipse.org</a></li>
</ul></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#marketplace">Eclipse Marketplace</a>
<ul>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-520850-possible-adware-in-marketplace-plugin-eclipse-class-decompiler">Bug 520850 - Possible adware in marketplace plugin (Eclipse Class Decompiler)</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-501861-selecting-a-favorite-on-eclipse-marketplace-is-slow">Bug 501861 - Selecting a favorite on Eclipse Marketplace is slow</a></li>
</ul></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#eclipse-project-management-infrastructure-pmi">Eclipse Project Management Infrastructure (PMI)</a>
<ul>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-519694-remove-solr-on-projects-eclipse-org">Bug 519694 - Remove solr on projects.eclipse.org</a></li>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=469321">Bug 469321 - Portal Shutdown plan: Transfer all portal functionality to PMI, website</a></li>
</ul></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#eclipse-working-groups">Eclipse Working Groups</a>
<ul>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-520121-need-a-new-conference-website-for-foss4g-na-2018">Bug 520121 - Need a new conference website for FOSS4G NA 2018</a></li>
<li><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/#bug-514542-create-initial-website-for-openpass">Bug 514542 - Create initial website for openPASS</a></li>
</ul></li>
</ul>
<hr />
<h2 id="api-eclipse-org">Api.eclipse.org</h2>
<h3 id="bug-516914-create-public-documentation-for-api-eclipse-org-rest-api">Bug 516914 - Create public documentation for api.eclipse.org REST Api</h3>
<p><img src="https://www.chrisguindon.com/uploads/api-eclipse-org.jpg" alt="Documentation for api.eclipse.org" title="Documentation for api.eclipse.org" /></p>
<p>The documentation for <a href="https://api.eclipse.org">api.eclipse.org</a> was all over the place and we needed to <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=516914">fix</a> that.</p>
<p>Some documentation was available on our <a href="https://wiki.eclipse.org/Eclipse_USS">wiki page</a> but most of it was written in our source code and in a Google document. We decided to resolve this issue by converting our GDOC to static HTML.</p>
<p>After trying out <a href="https://swagger.io/">SWAGGER</a> and <a href="https://raml.org/">RAML</a>, we decided to use <a href="https://apiblueprint.org/">API Blueprint</a> to generate our API docs.</p>
<p>API Blueprint is a documentation-oriented web API description language. The API Blueprint is essentially a set of semantic assumptions laid on top of the Markdown syntax used to describe a web API. In addition to the regular Markdown syntax, API Blueprint conforms to the GitHub Flavored Markdown syntax.</p>
<p>If you are interested in this project, our documentation source code is available on <a href="https://github.com/chrisguindon/eclipse_api">GitHub</a>.</p>
<h3 id="bug-502485-activity-tab-error-reports-from-aeri">Bug 502485 - Activity tab - Error reports from AERI</h3>
<p><img src="https://www.chrisguindon.com/uploads/accounts-eclipse-org-aeri-reports.jpg" alt="Error reports from AERI" title="Error reports from AERI" /></p>
<p>As of June 2015, with the Eclipse Mars simultaneous release, all Eclipse packages are shipped with the <a href="https://wiki.eclipse.org/EPP/Logging">Automated Error Reporting client</a> (called AERI).</p>
<p>Ever since AERI became a part of the Eclipse packages, eclipse.org has seen a steady stream of incoming error reports. Eclipse users currently send around 70,000 reports per week. That is a total of 3 million reports in the past 12 months!</p>
<p>This quarter, we added a new <strong>Error Reports</strong> tab for each user profile on <a href="https://accounts.eclipse.org">accounts.eclipse.org</a>. This tab allows users to review reports they submitted.</p>
<p>You can try it out now by <a href="https://accounts.eclipse.org">log in</a> with your Eclipse account.</p>
<hr />
<h2 id="eclipse-org">Eclipse.org</h2>
<h3 id="infra-2507-donate-campaign-plan-fall-2017">Infra 2507 - Donate Campaign Plan - Fall 2017</h3>
<p><img src="https://www.chrisguindon.com/uploads/donate.jpg" alt="October Donation Campaign" title="Eclipse Foundation: October Donation Campaign" /></p>
<p>On September 29, we launched the <a href="https://ianskerrett.wordpress.com/2017/09/29/annual-donation-campaign-end-user-support-for-the-eclipse-foundation/">October Donation Campaign</a>. The goal is to have over 1000 individual donations to the Eclipse Foundation and help support the overall community.</p>
<p>We implemented a new <a href="https://www.eclipse.org/donate/">donation</a> page that allows donors to give back using their credit card. I expect this to be useful for user&rsquo;s who can&rsquo;t or won&rsquo;t use Paypal or Bitpay.</p>
<p>We investigated a few options to incorportate credit card donations and we chose <a href="https://www.stripe.com">Stripe</a>. Regarding it&rsquo;s implementation, we are using the <a href="https://www.drupal.org/project/stripe">Drupal Stripe</a> module with the latest <a href="https://github.com/stripe/stripe-php">Stripe PHP API Library</a>.</p>
<p>A few days before pushing this to production we noticed that the Drupal Stripe module did not support web proxies. This was a last minute oversight because our testing servers did not require us to use a web proxy to connect to Stripe&rsquo;s API.</p>
<p>I created an issue on drupal.org to <a href="https://www.drupal.org/node/2912208">enable web proxy support</a> and I am hoping the contribute a patch to fix this very soon.</p>
<p>You can help support the overall Eclipse community by <a href="https://www.eclipse.org/donate/">donating now</a> to the Eclipse Foundation.</p>
<h3 id="bug-521084-add-epl-2-0-to-the-website">Bug 521084 - Add epl-2.0 to the website</h3>
<p>On August 24, The <a href="https://www.eclipse.org/org/press-release/20170829eplv2.php">Eclipse Foundation announced</a> that version 2 of the <a href="https://www.eclipse.org/legal/epl-2.0/">Eclipse Public License (EPL v2)</a> was approved by the Eclipse Foundation Board of Directors and the <a href="https://opensource.org/">Open Source Initiative</a> (OSI).</p>
<p>I was tasked by <a href="https://mmilinkov.wordpress.com/2017/04/07/eplv2-a-new-version-of-the-eclipse-public-license/">Mike Milinkovich</a> to format the final <a href="https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.html">HTML</a> and <a href="https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt">plain text</a> document for this new version.</p>
<p>I was really excited to create these digital documents that will be included in many open source projects in the future.</p>
<p>For more information, you can visit the Eclipse Foundation <a href="https://www.eclipse.org/org/press-release/20170829eplv2.php">press release</a>.</p>
<h3 id="bug-261658-status-eclipse-org">Bug 261658 - status.eclipse.org</h3>
<p><img src="https://www.chrisguindon.com/uploads/status-eclipse-org.jpg" alt="status.eclipse.org" title="Eclipse Foundation: Status page." /></p>
<p>Denis, our IT Director, built this very nifty <a href="https://status.eclipse.org">status page</a> and by doing so, won the award for closing the oldest <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=261658">bug</a> this quarter!</p>
<p>The status page measures performance of various Eclipse.org services from our monitoring agent in Portland, Oregon (many thanks to <a href="https://osuosl.org/">OSU Open Source Lab</a>).</p>
<p>If you are experiencing issues with some of our services, please take a look at our <a href="https://status.eclipse.org">Service Status</a> page for more information.</p>
<hr />
<h2 id="marketplace">Marketplace</h2>
<h3 id="bug-520850-possible-adware-in-marketplace-plugin-eclipse-class-decompiler">Bug 520850 - Possible adware in marketplace plugin (Eclipse Class Decompiler)</h3>
<p>It was <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=520850">brought to my attention</a> that a listing on Eclipse Marketplace, called Eclipse Class Decompiler, contained binary code that could be used for adware and could potentially download files to Eclipse workspaces.</p>
<p>This issue was initially reported in a blog post from a community member. After a bit of testing with <a href="https://portswigger.net/burp/freedownload">Burp Suite Free Edition</a>, I was able to confirm his findings. It was clear that this plugin included code that was not appropriate for the Eclipse users and community.</p>
<p>We removed the listing from Eclipse Marketplace and the Eclipse Foundation strongly suggests any Eclipse user to uninstall this plugin from their workspace.</p>
<p>To remove this plugin, please do the following:</p>
<ol>
<li>Go to Help &gt; About Eclipse &gt; Installation Details</li>
<li>Select the feature(s) belonging to the entry</li>
<li>Press &ldquo;Uninstall&rdquo;</li>
<li>Follow the wizard</li>
</ol>
<p>If you have any questions, please send an email to <a href="mailto:emo@eclipse-foundation.org">EMO</a>.</p>
<h3 id="bug-501861-selecting-a-favorite-on-eclipse-marketplace-is-slow">Bug 501861 - Selecting a favorite on Eclipse Marketplace is slow</h3>
<p>Two years ago, we decided to move Eclipse Marketplace Favorites to <a href="https://api.eclipse.org/#eclipse-uss">Eclipse USS</a>. This move allowed the <a href="https://projects.eclipse.org/projects/technology.packaging.mpc">Eclipse Marketplace Client (MPC)</a> to leverage the <a href="https://projects.eclipse.org/projects/technology.usssdk">Eclipse User Storage Service SDK</a> to add/remove user favorites.</p>
<p>The Eclipse User Storage Service SDK provides an idiomatic Java library for easy use of the USS by Eclipse RCP-based applications. The USS SDK transparently handles the authentication and login capabilities required to use the USS from an Eclipse installation.</p>
<p>Unfortunately, this move created a <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=501861">regression</a> on our website because it required the page to reload each time a favorite was added or removed.</p>
<p>To speed up this action, our team decided to <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=501933">enable the implicit grant flow</a> for the Marketplace API endpoint on <a href="https://api.eclipse.org">api.eclipse.org</a>.</p>
<p>The implicit grant flow is used to obtain access tokens and is optimized for public clients. These clients are typically implemented in a browser using a scripting language such as JavaScript.</p>
<p>This update allowed us to create a <a href="https://github.com/EclipseFdn/jquery-eclipsefdn-api">jQuery library</a> for adding/removing favorites. This new library can add and remove favorites without a page reload each time.</p>
<p>You can test this new change now on the <a href="https://marketplace.eclipse.org">Eclipse Marketplace</a> website.</p>
<hr />
<h2 id="eclipse-project-management-infrastructure-pmi">Eclipse Project Management Infrastructure (PMI)</h2>
<h3 id="bug-519694-remove-solr-on-projects-eclipse-org">Bug 519694 - Remove solr on projects.eclipse.org</h3>
<p><img src="https://www.chrisguindon.com/uploads/projects-eclipse-org-solr.jpg" alt="New project search page" title="New project search page" /></p>
<p>We&rsquo;ve been using <a href="http://lucene.apache.org/solr/">Apache Solr</a> for a few years now to run the Eclipse Projects search page. The search result page was very quick to load but our users often reported issues regarding the results.</p>
<p>Since Solr was a service that the Eclipse IT team needed to maintain, I considered <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=519694">removing Solr</a> from projects.eclipse.org and replacing it with a simple Drupal view.</p>
<p>It didn&rsquo;t take long before it was obvious that this new page did a better job at meeting the needs of our community.</p>
<p>This was a win/win for both the Eclipse IT team and our community. We now have a better search results page for our users and the Eclipse IT team can drop the support of Solr instances for this website.</p>
<p>You can try this new search page now on <a href="https://projects.eclipse.org">projects.eclipse.org</a>.</p>
<hr />
<h2 id="eclipse-working-groups">Eclipse Working Groups</h2>
<h3 id="bug-520121-need-a-new-conference-website-for-foss4g-na-2018">Bug 520121 - Need a new conference website for FOSS4G NA 2018</h3>
<p><img src="https://www.chrisguindon.com/uploads/foss4g-2018.jpg" alt="FOSS4G North America 2018" title="FOSS4G North America 2018" /></p>
<p>This year&rsquo;s <a href="https://2018.foss4g-na.org/">FOSS4G NA conference</a> is a collaborative effort involving <a href="http://www.osgeo.org/">OSGeo</a> and <a href="https://www.locationtech.org/">LocationTech</a>. The conference provides opportunities for the FOSS4G community to learn, explore, share, and collaborate on the latest ideas and information.</p>
<p>The conference is next year from May 14 to the 16 in St. Louis.</p>
<p>The <a href="https://2018.foss4g-na.org/">FOSS4G - North America 2018</a> website is now available and you can follow <a href="https://twitter.com/foss4gna">@foss4gna</a> on twitter or the latest news.</p>
<h3 id="bug-514542-create-initial-website-for-openpass">Bug 514542 - Create initial website for openPASS</h3>
<p><img src="https://www.chrisguindon.com/uploads/openpass.jpg" alt="OpenPASS Working Group" title="OpenPASS Working Group" /></p>
<p>The goal of the Eclipse OpenPASS Working Group is to support the development of advanced driver assistance systems (also known as autonomous driving systems) providing tools and adapters for standardized openly-available and vendor-neutral platforms for simulation of traffic scenarios.</p>
<p>Eric Poirier did a great job at building this new website using Drupal and the Eclipse Solstice look and feel.</p>
<p>The <a href="http://openpass.eclipse.org/">OpenPASS Working Group</a> website is now available!</p>
<hr />
<h2 id="summary">Summary</h2>
<p>I am very proud of the work that my team did this quarter and I am looking forward to new and exciting projects for Q4.</p>
<p>I am still working on a final list of MBO&rsquo;s for Q4 2017 but here&rsquo;s a shortlist of what&rsquo;s on my radar:</p>
<ol>
<li>Migrate our Conference platform to <a href="https://www.drupal.org/project/cod">COD 7.x-2.x</a>.</li>
<li>Build a new conference website for Eclipse France 2018.</li>
<li>Pursue the work done so far with <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=469321">Bug 469321</a> - Portal Shutdown plan: Transfer all portal functionality to PMI, website, etc.</li>
<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=421727">Bug 421727</a> - Use mysqli extension instead.</li>
<li>Archive some EclipseCon websites to static HTML to reduce maintenance.</li>
<li>Migrate mailing list subscriptions to accounts.eclipse.org.</li>
</ol></div></div></div><div class="field field-name-field-blog-original-source field-type-link-field field-label-above"><div class="field-label">Source:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/">https://www.chrisguindon.com/post/q3-2017-eclipse-foundation-webdev-report/</a></div></div></div>Tue, 03 Oct 2017 14:30:00 +0000Christopher Guindon4255 at https://blogs.eclipse.orghttps://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-webdev-report-q3-2017#comments