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.
Difference between revisions of "Architecture Council/Meetings/March 14 2019"
m |
|||
| Line 6: | Line 6: | ||
| Date & Time: | | Date & Time: | ||
| Thursday '''March 14, 2019''' at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Eclipse+AC+Montly+Meeting&iso=20190314T11&p1=188&ah=1 1100 Ottawa] <br>[[Image:Html.gif]][http://www.google.com/calendar/embed?src=g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com&ctz=Canada/Toronto HTML] | [[Image:Ical.gif]][http://www.google.com/calendar/ical/g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com/public/basic.ics iCal] | | Thursday '''March 14, 2019''' at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Eclipse+AC+Montly+Meeting&iso=20190314T11&p1=188&ah=1 1100 Ottawa] <br>[[Image:Html.gif]][http://www.google.com/calendar/embed?src=g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com&ctz=Canada/Toronto HTML] | [[Image:Ical.gif]][http://www.google.com/calendar/ical/g30r6idsq3rsufe2j3t6k0l0g4%40group.calendar.google.com/public/basic.ics iCal] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| Line 30: | Line 11: | ||
'''Update from EMO (Wayne/Gunnar):''' | '''Update from EMO (Wayne/Gunnar):''' | ||
| − | * No major update from Wayne and Gunnar. We just re-iterated on the improvements of the revised EDP and noted that the new release process in effect. | + | * No major update from Wayne and Gunnar. We just re-iterated on the improvements of the revised EDP and noted that the new release process is in effect. |
* Feedback was provided during the call about the the new release process: | * Feedback was provided during the call about the the new release process: | ||
** projects need better visibility whether a release review is required or not | ** projects need better visibility whether a release review is required or not | ||
| Line 60: | Line 41: | ||
'''Other:''' | '''Other:''' | ||
| − | * Q: Can projects request their own GitHub organization? | + | * ''Q:'' Can projects request their own GitHub organization? |
| − | ** A: Yes, this is supported. Please open a bug via Community > GitHub. However, please note that this requires Webmaster time and needs to be carefully scheduled. | + | ** ''A:'' Yes, this is supported. Please open a bug via Community > GitHub. However, please note that this requires Webmaster time and needs to be carefully scheduled. There will be requirements that must be met (eg., branding, accountability). |
| − | There will be requirements that | + | |
Latest revision as of 12:14, 14 March 2019
| Meeting Title: | Architecture Council Monthly Meeting |
| Date & Time: | Thursday March 14, 2019 at 1100 Ottawa  HTML |  iCal
|
Agenda / Notes
Update from EMO (Wayne/Gunnar):
- No major update from Wayne and Gunnar. We just re-iterated on the improvements of the revised EDP and noted that the new release process is in effect.
- Feedback was provided during the call about the the new release process:
- projects need better visibility whether a release review is required or not
- one suggestion was to provide additional information perhaps within the project handbook
- Wayne would like to make it visible in PMI when creating/editing a release record but this requires more time
- No update on IP tooling infrastructure. There has been a bit of a delay and it's taking longer than expected. Wayne would like to brief the AC at some point. There is no action item for AC right now.
Infrastructure Update (Denis):
- The GitHub Pull-Request validation hook has been replaced with a new GitHub app
- It's more reliable and provides a better experience
- CBI migrations to Jiro (and: what is Jiro)
- the build infrastructure started migrating towards a Kubernetes clusters
- Jiro == Jenkins Instance Running on OpenShift
- project JIPPs will be migrated individually
- projects need to support the migration (please do!)
- acquired additional compute power for the build infrastructure
- freed up JIPP hosts will also join the build infrastructure
- Q: what help is need from projects for JIPP -> Jiro migration
- A: only testing/validating
- Q: will projects be able to provide customized containers?
- A: yes
- limits exists around capacity for projects
- the Kubernetes cluster is used exclusively for build, not for project services/hosting
- Q: is the build Linux only or will other operating system be supported?
- A: not possible yet, Linux only; the Webmasters are hoping to integrate Windows and Mac at some point
For follow up question about Jiro and/or help please reach out via the CBI mailing list
Other:
- Q: Can projects request their own GitHub organization?
- A: Yes, this is supported. Please open a bug via Community > GitHub. However, please note that this requires Webmaster time and needs to be carefully scheduled. There will be requirements that must be met (eg., branding, accountability).
Last meeting: Architecture Council/Meetings/January 10 2019
Action Items
- n/a