Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Architecture Council/Meetings/June 28 2018"

(Agenda / Notes)
Line 29: Line 29:
 
== Agenda / Notes  ==
 
== Agenda / Notes  ==
  
* Update EMO (Wayne)
+
'''Update EMO (Wayne)'''
* Update Infra (Denis)
+
* Changes to AC calls
+
* Next call date
+
* Plan for EDP Revision (Gunnar & Wayne)
+
  
 +
Photon went out. The feedback tracked so far is very positive.
  
Feel free to edit, but '''<font color="red">not during the call!</font>'''
+
The Eclipse Foundation does have a Security Policy. In the past the majority of vulnerabilities reported affected the Eclipse.org websites. Because the number of runtime projects is increasing, the diversity of vulnerabilities is increasing.
  
Last meeting: [[Architecture Council/Meetings/May 17 2018]] -- open actions see [[#Action_Items]]
+
OpenJ9 is in need of a semi-private Git repository as they are working on security issues. The Webmaster team is working on a solution which would be available to other projects, too.
  
=== General Notes ===
+
In general, any vulnerability which can be used to exploit users' systems or data is worth promoting as CVE. The Eclipse Foundation can issue CVEs and will report then.
  
...
+
Wayne will update process and documentation over the upcoming days. He is also looking for help from the AC when managing (assessing, impact, importance, etc.) with security issues.
 +
 
 +
 
 +
'''Webmaster Update (Mikaël)'''
 +
 
 +
Jenkins Enterprise is now running on a small cluster. The Webmaster team started testing migrations of JIPPs. For now only early adopters will be migrated. Eventually all JIPPs will be migrated into the new service.
 +
 
 +
A question was raised whether Jenkins Enterprise can build GitHup Pull Requests. Mikaël answered yes and also mentioned that the functionality is already available today. Please open a bug for the Webmaster team to have the pull request plug-in installed and configured for your GitHub repository if you need it.
 +
 
 +
 
 +
'''Changes to AC calls (Gunnar)'''
 +
 
 +
Gunnar asked for feedback on the previous two update items. Going forward he'd like to have them as standing items on the call agenda. The feedback was very positive. The general comments indicate that these updates are very useful.
 +
 
 +
Going forward we are going to streamline the call a bit. It will by default run for up to 30 minutes. We'll keep the remaining 30 minutes as an overflow for discussion. Attendees are welcome to drop out earlier if they don't need/want to participate in the overflow time.
 +
 
 +
 
 +
'''Next call date (Gunnar)'''
 +
 
 +
Given the short distance and summer vacation time, we cancelled the July call. Our next call will be August 9, 2018.
 +
 
 +
 
 +
'''Plan for EDP Revision (Gunnar & Wayne)'''
 +
 
 +
The plan has been finalized. The focus of the next major revision will be anything around releases. It has been indicated that the burden to release more frequently is too high currently. During the discussion Wayne raised the idea of separating release reviews from releases. The IP Log review is coupled with a release review event but not with a release event. Formal release reviews must happen once or at most twice per year. Releases can be issues more frequently, though. Of course, projects should be able to always request a formal release review for every release they do.
 +
 
 +
Gunnar explained that there is an AsciiDoc version of the EDP document at [https://github.com/eclipse-architecture/eclipse-development-process/blob/develop/eclipse_development_process.adoc github.com/eclipse-architecture/eclipse-development-process]. We'll work with pull requests against that document. Going forward, the calls will be used to collect and discuss ideas. We'll switch to the mailing list and pull requests for in deep discussion on solutions/proposed changes.
 +
 
 +
 
 +
Last meeting: [[Architecture Council/Meetings/May 17 2018]] -- open actions see [[#Action_Items]]
  
 
== Action Items  ==
 
== Action Items  ==
  
n/a
+
* Wayne and Gunnar to groom the the backlog in Bugzilla and get all bugs aligned for the EDP plan.
  
  

Revision as of 03:38, 29 June 2018

Meeting Title: Architecture Council Monthly Meeting
Date & Time: Thursday June 28, 2018 at 1100 Ottawa
Html.gifHTML | Ical.gifiCal
Dial in: Join from PC, Mac, Linux, iOS or Android: https://eclipse.zoom.us/j/438487984

Or iPhone one-tap :

   US: +16699006833,,438487984#  or +14086380968,,438487984# 

Or Telephone:

   Dial(for higher quality, dial a number based on your current location):
       US: +1 669 900 6833  or +1 408 638 0968  or +1 646 876 9923 
       Canada: +1 647 558 0588 
       France: +33 (0) 1 8288 0188 
       Germany: +49 (0) 30 3080 6188 
       United Kingdom: +44 (0) 20 3695 0088 
       Switzerland: +41 (0) 31 528 0988 
       Sweden: +46 (0) 8 4468 2488 
       Denmark: +45 89 88 37 88 
       Netherlands: +31 (0) 20 241 0288 
   Meeting ID: 438 487 984
   International numbers available: https://eclipse.zoom.us/zoomconference?m=zZBWgLOe1JIIW8E3tapxg4jzZNmjTfbO

Agenda / Notes

Update EMO (Wayne)

Photon went out. The feedback tracked so far is very positive.

The Eclipse Foundation does have a Security Policy. In the past the majority of vulnerabilities reported affected the Eclipse.org websites. Because the number of runtime projects is increasing, the diversity of vulnerabilities is increasing.

OpenJ9 is in need of a semi-private Git repository as they are working on security issues. The Webmaster team is working on a solution which would be available to other projects, too.

In general, any vulnerability which can be used to exploit users' systems or data is worth promoting as CVE. The Eclipse Foundation can issue CVEs and will report then.

Wayne will update process and documentation over the upcoming days. He is also looking for help from the AC when managing (assessing, impact, importance, etc.) with security issues.


Webmaster Update (Mikaël)

Jenkins Enterprise is now running on a small cluster. The Webmaster team started testing migrations of JIPPs. For now only early adopters will be migrated. Eventually all JIPPs will be migrated into the new service.

A question was raised whether Jenkins Enterprise can build GitHup Pull Requests. Mikaël answered yes and also mentioned that the functionality is already available today. Please open a bug for the Webmaster team to have the pull request plug-in installed and configured for your GitHub repository if you need it.


Changes to AC calls (Gunnar)

Gunnar asked for feedback on the previous two update items. Going forward he'd like to have them as standing items on the call agenda. The feedback was very positive. The general comments indicate that these updates are very useful.

Going forward we are going to streamline the call a bit. It will by default run for up to 30 minutes. We'll keep the remaining 30 minutes as an overflow for discussion. Attendees are welcome to drop out earlier if they don't need/want to participate in the overflow time.


Next call date (Gunnar)

Given the short distance and summer vacation time, we cancelled the July call. Our next call will be August 9, 2018.


Plan for EDP Revision (Gunnar & Wayne)

The plan has been finalized. The focus of the next major revision will be anything around releases. It has been indicated that the burden to release more frequently is too high currently. During the discussion Wayne raised the idea of separating release reviews from releases. The IP Log review is coupled with a release review event but not with a release event. Formal release reviews must happen once or at most twice per year. Releases can be issues more frequently, though. Of course, projects should be able to always request a formal release review for every release they do.

Gunnar explained that there is an AsciiDoc version of the EDP document at github.com/eclipse-architecture/eclipse-development-process. We'll work with pull requests against that document. Going forward, the calls will be used to collect and discuss ideas. We'll switch to the mailing list and pull requests for in deep discussion on solutions/proposed changes.


Last meeting: Architecture Council/Meetings/May 17 2018 -- open actions see #Action_Items

Action Items

  • Wayne and Gunnar to groom the the backlog in Bugzilla and get all bugs aligned for the EDP plan.


Next Meeting

Back to the top