Skip to content

Dev Meetings 2021

Jump to bottom
Vincent Fugnitto edited this page Jan 5, 2022 · 1 revision

Agenda, 2021-12-21

Agenda, 2021-12-14

  • [Ken] Toolbar demo (at end of meeting). See discussion topic
  • [Gabriel B.] Inclusion of 10448
  • [Thomas] File system performance 9514: we can fix it, but it's a big change
  • Release scheduled for December 16th due to holidays

Agenda, 2021-12-07

  • [Colin] Breaking changes to WindowService in 10379.
  • [Colin] Direction of the callhierarchy package.
  • [Ken] Posted discussion topic about upstreaming our toolbar. Plan to demo next week.
  • [Jonas]: Where to host Page Object Model for System Test: PR open to enable PlayWright tests: https://github.com/eclipse-theia/theia/pull/10494
  • [Mark] Refactoring the communication layer by using socket.io. See PR #10514.
  • Project theia-dev mailing list: subscribe and find the archive here

Agenda, 2021-11-30

Agenda, 2021-11-23

Agenda, 2021-11-16

Agenda, 2021-11-09

  • meeting back at usual local time for most of Europe and North America
  • TheiaCon: time to push for registrations. Register here: https://events.eclipse.org/2021/theiacon/
  • Blueprint CI: still not working but good progress made. Mac signing service now works

Agenda, 2021-11-02

  • switching meeting time starting this week, to 3 PM UTC, following time change in Europe. America will follow next week.
  • [Rob] Disk usage for theia-blueprint downloads
    • [Marc] Saw that email too, and created an issue
    • Rob will look into moving older Blueprint installers to the archive storage. Longer term a solution in CI would work best

Agenda, 2021-10-26

Agenda, 2021-10-19

  • [Jonas]: Please urgently update the road map. We will likely have some new visitors next week due to EclipseCon, should be in a good state by then. Please add new items, close or move items from the last milestone

Agenda, 2021-10-12

  • [Colin] Merging -
    1. accidents with (not) squashing (mea culpa). Should we only allow the squash button?
    2. Who merges, and when? With PR's from committers, author is usually left to merge. With PR's from non-committers, reviewing committer has to merge. With PR's from non-committers from organizations with committers, should they be responsible (in the ideal case) for merging after approval?
  • [Jonas] Hackathon, who be willing to be a mentor
  • [Jonas] Public test suite for adopter

Agenda, 2021-10-05

  • [Thomas] 18 (of 38) replies from committers re: secret leaks.
  • [Mark] Localization is finished and waiting for reviewers. See the Epic at #10188 for more information.
  • last week to submit presentation proposals for TheiaCon. Please consider a flash talk: 5 minutes to share something useful is a very good payoff/effort ratio.
  • CI mostly back on track - still an issue with some of the TypeDoc generation
  • [Artem] npm packages naming https://www.npmjs.com/package/@theia/plugin-ext

Agenda, 2021-09-28

  • [Marc] Following the Travis CI potential secrets leak, we have deleted all existing publish token from our npm account. A new token was generated and set on the main Theia repo (eclipse-theia/theia). Please let me know if other, among our repos, also need this token.
  • [Thomas] We've asked committers to either rotate tokens giving access to Theia that may have been leaked on Travis or to confirm they did not store such tokens on Travis. So far, we have 7 responses: what to do with other committers?
  • [Marc] We are still working on fixing npm publish of next versions of @theia packages in the main repo, after rotating the npm token and the improvements to the build system.
  • add your item

Agenda, 2021-09-21

  • [Marc] We are ramping-down our efforts maintaining the theia-ide/theia-apps repo, which pre-dates Theia joining the Eclipse Foundation. Instead we want to concentrate supporting the best, most polished example app based on Theia: Theia Blueprint! See this related community forum post for more info.

Agenda, 2021-09-14

  • [Mark] - I'd like to talk about our approach to localizing Theia. See this issue comment on my currently planned approach.
  • New(ish) PR CI check: "3PP License Check". Uses Eclipse Foundation dash-licenses. PR
  • Marc and Thomas recently recorded episode 4 of Cloud Chat with Jesse Williams. The episode should be available soon. It was the second episode with Theia as the subject - the previous one had Rob as guest: watch on the EF YouTube channel
  • TheiaCon: The Call For Papers is now open for this event happening in mid-November. Please submit your proposals at https://forms.gle/9jtMmv8ruHKdREYs7. Please also retweet and share this tweet to raise awareness, https://twitter.com/theia_ide/status/1437729831819616258. More information will be coming online about the event soon.
  • Call Agenda and Notes: We discussed posting reminders of this Dev Call weekly at https://community.theia-ide.org/, linking to the wiki and soliciting more topics. We can also briefly summarize what happened at the last call.
  • Forum Categories: Also for https://community.theia-ide.org/, we discussed creating categories to make posts more discoverable. Brian will make a proposal to discuss and decide upon later.

Agenda, 2021-09-07

Agenda, 2021-08-31

Agenda, 2021-08-24

Agenda, 2021-08-17

No agenda items:

Notes:

  • Jonas & Marc absent
  • Paul Maréchal is going to move some code related to building theia-electron to the theia-cli package and asked whether there where any objections. None were raised.

Agenda, 2021-08-10

  • [Marc] "git commit messages" - should we aim to improve them? Is it enough to have the ability to map a commit to its PR/issue? Is the ability to access this information offline important to anyone? e.g. without having to use GitHub
  • Paul: Node/Electron upgrades: how to proceed now and forward.
  • Jonas: Start-up Performance: https://github.com/eclipse-theia/theia/issues/9869
  • Jonas: Any more feedback about ES 6 upgrade: Transpiling to ES6 https://github.com/eclipse-theia/theia/pull/9436
  • Add your item...

Agenda, 2021-08-03

  • Created a project vulnerability reporting policy, based on the Eclipse Foundation's. PR. TL;DR: we should now allow vulnerabilities to be reported publicly, e.g. through GH issues or discussions. The issue and PR templates have been updated to reflect that.
  • Should we rebuild releases on doc changes? What are the criteria?
  • [Jonas] We are investigating the plugin initialization process for performance improvements
  • [Jonas] We will revisit the developer documentation

Agenda, 2021-07-27

  • [Jonas]: Number of breaking changes, documentation. Seems an issue for adopters. Suggestions:

    • Migration guide for all adopters
    • Chain of adopters / early adopters
    • Blueprint nightly against latest
    • Yeoman nightly against latest
    • Define responsible people to watch these test builds
    • More integration tests Documentation needed flag / Migration guide necessary flag during review

  • [Thomas]: Supported platforms (OS version, Processor, etc.): do we have a policy?

  • Release 1.16.0 scheduled for Thursday, the 29th of July.

Agenda, 2021-07-13

Agenda, 2021-07-06

Agenda, 2021-06-29

  • Release tomorrow, June 30th
  • [Jonas]: End of Q2/2021 is in one week, please update Roadmap now: (https://github.com/eclipse-theia/theia/wiki/Eclipse-Theia-Roadmap). I will move items by default
  • [Jonas]: New Gallery on Theia website, please add products to it! https://theia-ide.org/ [Jonas]: Online "try now" version?
  • [Marc] Progress review has started. I am the project's representative. We are piloting a new way of doing these reviews, driven by EMO. This is the chance to demonstrate we've been following the rules (generally) and to make small improvements to our process, wherever necessary.
    • vulnerability management - need to add SECURITY.md in repo root and to state the project's policy (within the bounds of the EF policy). e.g. report new vulnerabilities to the EF security team rather than opening a GH issue.
  • [Thomas] Monaco update: what about the IP side?

Agenda, 2021-06-22

  • [Marc] OOO for family emergency. Please go ahead with meeting if needed.
  • [Jonas]: End of Q2/2021 is in one week, please update Roadmap now: (https://github.com/eclipse-theia/theia/wiki/Roadmap)
  • [Jonas]: Online "try now" version?
  • [Jonas]: who has access to the Theia Twitter handle?

Agenda, 2021-06-15

  • [Thomas Mäder] Monaco update (https://github.com/eclipse-theia/theia/pull/9154) are we ready to merge?
    • Outcome: we try to resolve conversations and retest until the end of the week.
  • [Thomas Mäder] Pull request are piling up again: let's produce less and review more!
  • Release: which date should we schedule the next release?
  • [Jonas Helming] Where to host example applications/distributions/products (e.g. CDT like)
  • [Jonas Helming] Merge community day slot with ECDT

Agenda, 2021-06-08

Agenda, 2021-06-01

Agenda, 2021-05-25

Minutes, 2021-05-18

  • Are involved companies willing to discuss security considerations for online hosting? (Rob)
    • Private channel created on slack. Artem and Marc have asked to join right away. Committers that want to join can ping Rob
      • Rob will check with Wayne that's fine
    • Potential Eclipse Theia security flaws should be reported as per the EF policy
    • We ought to have a simple example of Blueprint, securely deployed in "cloud configuration", using the browser version of the app. Maybe we can start by documenting how to do this, or commonly faced challenges at least
  • Paul: Refactor/simplify child process infrastructure for terminals and tasks?
    • RH ok so long as they have time to adapt
    • Arm has a use-case where they'd like the terminal to be excluded from the browser version of a Theia app.
      • Paul will keep this in mind. He thinks his refactor will make it easier to do so, but extra work will be required

Agenda, 2021-05-11

Minutes, 2021-05-04

  • [Monaco update] Dan is making good progress in his PR, in collaboration with a few committers. RH is going to assist further (Thomas).
    • This is a strategic contribution - this Monaco update needs to be done periodically or it will lock us to supporting an older version of LSP, among other things.
    • The IP aspect needs to be kept in mind. Wayne has given a suggested way forward. Dan is starting to look into opening the required CQ(s), with Amiram's help (need to be a committer).
    • We are looking for reviewers, to take ownership of a subset of the tests that will need to be run, to validate the PR.. For now you can write your name besides an item, by editing the PR's description. If you do not have write-access, please post a message on the PR and a committer will edit for you.

Minutes, 2021-04-27

  • [Igor @vinokurig] Secret API (plugins API) https://github.com/eclipse-theia/theia/issues/9348 problem in encrypting data.
  • [Artem] please, add your topics to the agenda in advance. It would allow people to decide if they need to join before the call begins.

Minutes, 2021-04-20

  • [Brian] cloud dev tools call next week, seeking someone to talk about Theia, for ~5 mins (other EF projects will be covered as well). Maximilian will talk about blueprint, so that part is covered. This call is for the wide community, and open to public. This is an opportunity to raise awareness. also get people involved, give a quick project update, mention latest opportunities for collaboration/contributions.
    • Marc volunteers, unless someone want to do it.
  • Misc blueprint updates:
    • Ericson working on a few things:
      • browser version of blueprint, suitable for easy integration e.g. in Docker images
      • will propose new set of bundled extensions, taking advantage of vscode extension packs to make it easy to install several related extensions, at runtime. We can create such packs if they don't already exist or are not suitable for open-vsx. e.g. for Java extensions currently bundled with Blueprint.
      • In Blueprint Theia extension, add example, how to programmatically contribute links in the Help menu. e.g. link to documentation site, where to report issues.
      • create/use a Blueprint-specific global configuration folder (i.e. in user's home) instead of default .theia. This should prevent configuration clashes between several Theia-based apps, all using the same global folder.
    • Brian reports there are bugs on Mac version, see #71,#62, #70
  • [Theia website] The "Try in Gitpod" or such link takes one to the Gitpod annoucement, that they're switching away from Theia. Not ideal from a marketing PoV. The web site will soon be featured in (I think) an EF article or blog, which will likely drive traffic, and users to click-around on the site.
    • Brian to talk with Gitpod to see if possible, to remove announcement when clicked from our site.
    • Add a link to a Red Hat service that uses Theia

Minutes, 2021-04-13

Minutes, 2021-04-06

  • Suggestion which came up in ECDTools working group: Extend roadmap with "Help wanted" epics
  • The foundation no longer mandates sign-offs on commits. Do we want to also drop the requirement for the project?
  • Website?

Minutes, 2021-03-30

Minutes, 2021-03-30

Minutes, 2021-03-23

minutes, 2021-03-16

  • This week and next the meeting will be 1h later in North America, since we switched to daylight saving time last weekend. Europe to follow in a couple of weeks, and then we all go back to normal local meeting time.
  • [Jonas Helming]: Convert answered questions from bugs to discussions?
  • [Jonas Helming]: Online Hackathon for contributors? => see issue https://github.com/eclipse-theia/theia/issues/9219
  • [Valerii Svydenko] We're considering including this C# extension: https://open-vsx.org/extension/muhammad-sammy/csharp. Does anyone have experience with the extension?

Minutes, 2021-03-09

  • [Jonas Helming] Proposal for a pragmatic roadmap process:
  • Part 1 - Issues: We create a milestone in GitHub for every release. Developers should assign tickets to the current milestone if they intend to work on it during this period. It is OK to move things or not to complete, but developers should reflect the latest state in the tickets. Additionally, we could create a milestone "next" for the important stuff. This way we communicate with the community what the committers plan to work on and also what we find important to do.
  • Part 2 - Wiki Page: A wiki page to which all parties can contribute their high-level goals, e.g. per quarter. Does not have to be detailed, but just bullets. Topics can be one-time things such as "Improve embedded support via memory view", but also recurring such as "Improve stability" or "Improve VS Code API coverage". The goals should be discussed in the dev meeting once per quarter. The discussion should also collect suggestions on how to drive the project forward. Goals could be potentially mapped to issue labels, so we could add links to filtered searches.

  • [Thomas Mäder] We still have tags like "Java" in github issues. But we don't ship those extensions anymore. Should we remove them? I guess any old issues related to the old "languages" packages should be closed, as well, right? => yes

    • Consensus on language extension-related bugs was that we should just close those. I assume that would include removing the related issue labels
    • Also discussed closing old feature requests. If we believe that they'll never get implemented, just close them as "won't fix". Issue creators will get a notification from GitHub and can reopen if appropriate.

  • [Akos Kitta]: Remark on 👆 just close them as "won't fix". Issue creators will get a notification from GitHub and can reopen if appropriate.

    • OPs cannot reopen the issues if it was closed by owners/contributors. This is a very common mistake and worsens the contributor experience.

Minutes, 2021-03-02

  • [sticky][Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
    • Volunteers:
      • Colin Grant (Ericsson)
      • ???
  • Looking for a committer to help perform the project's release review. See: issue #9120. Technically the Foundation could ask us to stop performing releases until this is done.
  • Paul: core change to re-export some packages instead of relying on implicit dependencies.
  • [EF] theia-website CQ resolved
  • CQ opened for dry-run of using dash-licenses to validate dependencies licenses has been resolved. So as of a few months ago, our npm runtime dependencies look good. Next step: integrate the tool our CI and let it guide us to register CQs for dependencies it finds suspicious.
  • Project Roadmap: none official ATM, though some ongoing activities are implicitly known to us. Desirable to have one though. Jonas suggests a pragmatic approach, where we create the roadmap as part of our daily process.
    • labels for each release
    • committers mark items they intend to work-on on every release
    • ... (please complete)
  • Others small things all committers can start to do more-of is to help with triage of incoming issues and PRs. It helps and is a good way to gain knowledge in the project. Grooming the issues backlog is also a good way to help, e.g. re-testing older issues and closing if no longer applicable or valid.
  • random thought: would it be possible to add an aspect of gamification to the project's contributions? e.g. have "achievements" that are aligned with the project's needs? "most active committer in area ", "most active committer on the forums", "committer with most Pull Request review comments", ...
  • Brian wants to learn more about the project and will do some 1 on 1 interviews with committers. Those who want can reach-out: [email protected]

Minutes, 2021-02-23

  • [sticky][Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
    • Brian K. reiterated the importance of promptly registering CVEs for security flaws and that these should be a high priority for the project(s)
    • Volunteers:
      • Colin Grant (Ericsson)
      • ???
  • [Jonas] Is there a blocker, for Theia to adopt ES6? Jonas wants to investigate more closely if we could switch and is curious whether we know of any issues. Related issue
  • Last week's corrupted wiki was apparently a GH bug - making the wiki shorter by moving older entries did not help. It seems back to normal now.
  • Release 1.11.0 Thursday 25th
    • Paul looking into automating for the official releases. We do the next releases automatically but have no corresponding release commit (which we want for official releases).
  • Theia Blueprint: Looks ready for beta release.
    • blocker: theia-website has updated documentation that is not deployed yet - Netlify account used is a personal one (owner: Jan K.) and the people currently involved do not have access. Jonas to reach-out to Jan to try to get access for the short term. For the longer term, Brian mentioned that the EF uses Netlify, so maybe the Foundation has a Team account that could also be used by projects? Else maybe other infrastructure that could be used instead of it?
  • Monaco update: Dan and Artem and a few others are working on this (PR submitter and reviewers). Right now publishing the result to npm is blocking the process.
    • [Marc] to send an email to Sharon to see if moving this repo in our EF project makes sense. If so we can do it maybe for next time
    • [Marc] For now I'll add an npm publish token so it can be used in GH Action to publish. from the current theia-ide GH org. [Done]: name NPM_TOKEN

Minutes, 2021-02-16

  • [sticky][Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
  • Issue with this wiki: most of the time the rendering is broken, containing HTML. This seems intermittent, sometimes fixing itself with a reload. I have created an archive page, for the entries 2018-2020, but the reduced page size did not seem to help, so for now I keep the older entries here too.
  • [Jonas] The project has a big backlog of reported issues, many of the older ones are no longer relevant, in whole or in parts. What to do with these? Some ideas:
    • add a dev-meeting sticky to remind us, use a bot to auto-close the issues after a certain time (differing opinions about how much this helps)
    • something that could be tackled gradually if many committers are willing to help a bit
  • [Jonas] Feature suggestion, like activities in Eclipse: Provide API to filter unwanted contributions from frontend extensions
    • reminds of an old issue about being able to compose Theia applications in a more granular way,e.g. excluding some extensions that are required by default, for vscode extensions support.
  • Q: how to publish theia-generator-extension? We've been using np which does almost everything for you. All that's required extra is a publish token.

Minutes, 2021-02-09

  • [Colin|Ken] Demo: cpp-debug memory view improvements
  • [Rob] Is there an example for writing a frontend theiaPlugin that works in the browser? My tests have shown this doesn't seem supported.
  • Move of 3 theia-ide repos, to the Eclipse Theia project (theia-website, generator-theia-extension and vscode-builtin-extensions)
    • The 3 repos have been moved under the eclipse-theia GH org. A couple are pending deeper IP analysis and may require more action on our part.

Minutes, 2021-02-02

  • [Marc] is bluejeans not working for others too? "Sorry no meetings out here" - [Colin: me too]
    • issue
    • most likely, the meeting owner has deleted the meeting from their Blue Jeans account
    • AI for Artem - look at it and update the link
      • thanks Artem!
  • [sticky][Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
  • [Colin+Ken] We've done some internal work on upgrading the theia-cpp-extensions memory view UI and would like to gauge interest in upstreaming our changes.
    • demo next week, after other dev-meeting items are done.
  • [ci] Recent issue with vscode-builtins addressed by going with a slightly more recent version. Will try to re-publish v1.44.2 under the identity of open-vsx.
  • [Reviews] Paul is wondering what the others think about asking for more doc during reviews, to help understand the content
    • good idea when a reasonable person would not easily understand something
    • even more important for implicit dependencies, where one just "needs to know"

Minutes, 2021-01-26

  • [sticky][Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
    • so far no volunteer
  • Move of 3 repos to the EF project: one last re-licensing hurdle with relatively minor Red Hat contributions from 2 of the repos. Trying to push through - considering removing the contributions - they could in theory be re-submitted under the new license.
    • Florent to try to unblock
  • [Maximilian] Status of Theia Installer
  • [Maximilian] Proposed rename of theia-example repo to theia-blueprint
  • v1.10.0 release Thursday
  • [Rob] Announced they will be contributing a new extension, that will permit to run a debug adapter in the browser context. The plan is to provide a mock debug adapter that can be used to test the new feature.
    • We can discuss the details in an upcoming PR

Minutes, 2021-01-19

  • [Marc] There was a mistake in the agenda date's: Jan 20th instead of 19th. We've never done this meeting on any other day, so I think most probably ignored the date and joined anyway. But some may have missed the meeting, thinking it was happening the next day. Sorry about that. Maximilian did not join because of this and I hope can join next week instead.
  • [Thomas Mäder] File watcher bug: https://github.com/Axosoft/nsfw/issues/60 let's fix it if we can.
    • interesting problem. Paul M has worked on nsfw some and may contribute the discussion and help test an eventual PR
  • PR Ready to review: Support CustomEditor API (see issue)
    • quite a big PR, but will help with vscode extensions compatibility, to everyone's benefit.
  • [PR] Always set exact version when publishing
    • changes a bit the way latest version are published. If you have a product based on latest, you may want to have a look and test.
    • Please post on the PR if you'd like more time to test - else we'll aim to merge it tomorrow
  • Move of 3 theia-ide repos, to the Eclipse Theia project
  • [Marc] I'm looking for volunteers among the committers willing to occasionally help with security vulnerability report handling in the project, as per the related EF policy.
  • Monaco update: a contributor from SAP wants to try to contribute this. There is no easy step-by-step tutorial one can follow, but looking at how this was previously done can be a good guide.
    • Last year Roman Nikitenko took care of it, and can share knowledge and I hope review in-depth
      • Doing timely Monaco update is vital so that Eclipse Theia can keep-up with vscode. An older Monaco prevents us from supporting newer LSP versions and newer vscode extension's API.
      • It seems knowing how to do/test this ought to be something spread over several committers, to avoid depending too much on a single person and the bottleneck-effect this can have.
    • we can discuss on issue #8969

Minutes, 2021-01-12

  • Move of 3 theia-ide repos, to the Eclipse Theia project (theia-website, generator-theia-extension and vscode-builtin-extensions)
    • Re-licensing almost finished. I think we can go ahead and submit the repos for IP checks
  • [Marc] still lagging behind handling open-source "pings" - sorry about that (lots of internal things to do). If urgent, please ping again or email

Project Management

Documentation

Clone this wiki locally