#We're going to start a weekly call to
karmic sage
@vivid summit did this get scheduled? No rush if it hadn't, just wanted to make sure that I hadn't missed anything
vivid summit
<@488409085998530571> did this get scheduled? No rush if it hadn't, just wanted...
not yet. Team retreat this week so we're a bit slower. Will communicate here 🙂
buoyant heron
@karmic sage Yes, you can mark yourself as interested here. Our first one will be in two weeks. We hope to see you there!
https://discord.com/events/707636530424053791/1290853953776390175
karmic sage
Great. I'll add an issue to GH, but one of the things that I want to have talked about is "making the typescript sdk feel like typescript"
buoyant heron
Great. I'll add an issue to GH, but one of the things that I want to have talked...
Great, thanks for the heads up! We'll use this time for open discussion too.
karmic sage
My point is more of a meta discussion that touches on a bunch of the existing GH issues.
I'll go make the meta issue now and link in everything that sorta implies
.. actually do you want a specific GH issue for this type of meta discussion, or keep it to more specific issues ?
inland pecan
I am very interesed in this!
buoyant heron
.. actually do you want a specific GH issue for this type of meta discussion, or...
Sorry for the delay. It could be an issue or a GitHub discussion since GitHub discussions are usually used for those type of things.
@ivory wave which one do you think is best?
vivid summit
I prefer sticking to issues if possible
We don't use discussions much so it kind of becomes an island IMO
the risk is that we have open ended issues we don't know when to close. But that's easier to deal with than "nobody reads it because it's in an unfamiliar place "
karmic sage
@vivid summit do you think that it makes sense to create an issue for the 'meta' issue that links the existings issues that it describes, or should we just leave the conversations in the individual issues ?
the risk is that we have open ended issues we don't know when to close.
I agree.... this would be more of a talking point for the meeting rather than something that is specifically actionable
vivid summit
<@488409085998530571> do you think that it makes sense to create an issue for th...
if it helps understand the high level problem and discuss overall solutions, in a way that the individual smaller issues can't, then yes 👍
buoyant heron
@karmic sage did you have a chance to make the issue? @ivory wave and I are creating a rough agenda, so I want to make sure your issue is included.
karmic sage
Oops...I'll do that up now
Looking through the issues that are already there and this quote from Tom is pretty much what my issue was going to be
The global idea is to make the TS SDK DX much more natural to a TS engineer.
https://github.com/dagger/dagger/issues/8676