-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: add minutes for meeting 29 May 2024 (#276)
Signed-off-by: Michael Dawson <midawson@redhat.com>
- Loading branch information
Showing
1 changed file
with
72 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
# Node.js Next 10 Years team Meeting 2024-05-29 | ||
|
||
## Links | ||
|
||
* **Recording**: <https://www.youtube.com/watch?v=kMDaRW1LGyg> | ||
* **GitHub Issue**: <https://github.com/nodejs/next-10/issues/275> | ||
|
||
## Present | ||
|
||
* Michael Dawson (@mhdawson) | ||
* Ulises Gascon (@UlisesGascon) | ||
* Marco Ippolito (@marco-ippolito) | ||
* Darcy | ||
|
||
## Agenda | ||
|
||
## Announcements | ||
|
||
* Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
||
* Marco: survey has closed, thats to everybody who responded, over 3000 reponses. | ||
|
||
### nodejs/next-10 | ||
|
||
* Planning for next deep dive - Funding [#273](https://github.com/nodejs/next-10/issues/273) | ||
* Suggested agenda | ||
Funding for contributors | ||
* How can the project accept and handle contributions of $ | ||
* Use of crowdfunding in the project | ||
* Would we sign up to programs like OpenJS sustainability program, how would we spend $ | ||
* How to support linking people who want to pay to get a specific features/task completed | ||
* We agreed on date/time | ||
* Added to Node.js calendar | ||
* Marco will open discussion item to flag to collaborators | ||
* Michael tagged two related issues that were opened recently with a link to the deep dive info | ||
|
||
* Brainstorm next deep dive topics [#268](https://github.com/nodejs/next-10/issues/268) | ||
* Marco opened two issues | ||
* one on collaborator environment, some feedback from Rafael | ||
* <https://github.com/nodejs/next-10/issues/271> | ||
|
||
<https://github.com/nodejs/next-10/issues/274> | ||
|
||
* Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) | ||
* closed this issue as we discussed and PR in core is open | ||
|
||
* Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) | ||
* defer until Ambassador program launches/or not to decide on next step. | ||
|
||
* Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) | ||
* survey closed, more than 3000 recipients | ||
* Michael/Marco to go through the write in questions, Michael will send invite, and add Marco, and Ulises to see if we can get together to start on that. | ||
|
||
* Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) | ||
* Covered under the discussion of the Funding deep dive | ||
|
||
* Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) | ||
* Marco, some discussion on trouble delivering news externally | ||
* Michael, kind of have the feeling a bit more coverage, | ||
* Ulises, have releases, link for most commented issues, as well as issue teams can post news | ||
to, still not too many teams publishing info | ||
* Discussion is here - <https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9578212> | ||
* Some discussion about use of a “notable issue” tag, as even lower bar to get news out. | ||
* Maybe get some statistics of use of the feed | ||
|
||
## Q&A, Other | ||
|
||
## Upcoming Meetings | ||
|
||
* **Node.js Project Calendar**: <https://nodejs.org/calendar> | ||
|
||
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |