-
Notifications
You must be signed in to change notification settings - Fork 17.7k
golang tools
The golang-tools community is a group of people whose main focus and interest is the development of tools for the Go language. It is open to everyone. Tooling topics include (but are not limited to) code analysis, compilers, editor and IDE plugins, language servers, and standard libraries.
The golang-tools working group is useful for:
- getting feedback on ideas
- experimenting with a group of "trusted testers"
- external proof-reading of proposals, blog posts etc
A key goal of the golang-tools group is that all forums of communication, but especially the regular calls, are friendly and welcoming. We want to create an environment in which everyone feels both supported and able to share their opinions and experience, frankly, freely, and openly. The wider Go Code of Conduct, which we observe just like all other Go forums, summarises this well.
Discussion within the community takes place in three main spaces. There are also dedicated golang-tools sessions held at GopherCon each year.
Most day-to-day discussion take place in the #tools
channel on the Gophers Slack (sign-up here).
The golang-tools mailing list contains community updates as well as other forms of announcements.
The community operates a monthly “catch-up” call covering updates about large-impact changes, new tool initiatives, ongoing community projects and much more. The agenda is community-driven and anyone can suggest items that they would like to cover.
Like the other discussion spaces these calls are open to anyone and people new to the community are encouraged to join in and share in the conversation. The details (date, link, phone number, …) for each call are shared via the mailing list as well as the Slack channel.
As of October 2020, all calls/events will be added to the shared calendar.
- 2022-01-12 - Agenda
- 2021-10-06 - Agenda
- 2021-09-15 special edition: supporting type parameters Agenda
- 2021-08-18 - Meeting notes - video
- 2021-06-16 - Meeting notes - video
- 2021-05-12 - Meeting notes - video
- 2021-04-14 - Meeting notes - video
- 2021-03-10 - Meeting notes - video
- 2021-02-10 - Meeting notes - video
- 2021-01-13 - Meeting notes - video
- 2020-11-18 - Meeting notes - video
- 2020-10-21 - Meeting notes - video
- 2020-09-16 - Meeting notes - video
- 2020-08-19 - Meeting notes - video
- 2020-07-22 - Meeting notes - video
- 2020-06-24 - Meeting notes - video
- 2020-05-13 - Meeting notes - video
- 2020-04-08 - Meeting notes - video
- 2020-03-11 - Meeting notes - video
- 2020-01-28 - Meeting notes - video
- 2019-12-03 - Meeting notes - video
- 2019-10-29 - Meeting notes - video
- 2019-09-24 - Meeting notes - video
- 2019-08-27 - Meeting notes - video
- 2019-07-26 - Meeting notes - second session at GopherCon San Diego
- 2019-07-25 - Meeting notes - first session at GopherCon San Diego
- 2019-05-28 - Meeting notes - video
- 2019-04-30 - Meeting notes - video
- 2019-03-26 - Meeting notes - video
- 2019-02-26 - Meeting notes - video
- 2019-01-29 - Meeting notes - video
- 2018-12-11 - Meeting notes - video
- 2018-11-27 - Meeting notes - video
- 2018-11-06 - Meeting Notes
- 2018-10-23 - Meeting Notes - video
- 2018-10-09 - Meeting notes - video
- 2018-09-18 - Meeting notes - video
- 2018-08-28 - Notes from GopherCon "kick off" session
We try to share the load of organizing and running the calls between Gophers inside and outside of Google (generally alternating between Googlers and non-Googlers). Here are the steps required as organizer:
- Using a non-google.com account, ask Paul Jolly for editing access to the shared drive, and then create a folder for the next monthly call, and a put a copy of the previous call's agenda in it. The copy will only be visible by anyone with the link, so change that to allow edits (this last step is not possible with docs owned by @google.com accounts).
- Rename and clear out the agenda for the next call.
- Update this wiki, archiving the previous call and linking the new upcoming call.
- Update the shared calendar with the new event. By convention calls run from 16:30-17:30 London.
- Send reminders 1-2 weeks before the call date to the mailing list and #tools slack channel.
- On the day of the call, remember to ask a Googler to start recording, and then run through the agenda.