Farcaster Devs

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

I think MM should add a proper issue tracker for support. What worked when we were a handful of devs and the MM team was small does not work any more.

I don't want to @ mention everyone in the MM team that I think might be relevant, whenever I have an issue. I can DC them, but it's the same problem. And in both cases, I don't know if they've seen my request, if they intend to deal with it or not, etc.

Pls, give us an issue tracker we can feel sure that the right person will check.

@dwr.eth @v

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

do you have an example of someone doing this well? would be useful for me to see a working setup

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

I don't have something to suggest. Zendesk? There are 100s of ticketing systems out there, but I've never managed one myself to have an opinion on pros and cons.

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links | opinions are my own

If the problem is with the open sourced part, maybe yes.

I wonder if GitHub issues could be possible when the monorepo is made public?

The alternative is me pinging you on DCs that you have not replied to a question I asked one week ago, and you probably copy-pasting it to someone else in the team, or telling me that oh, yes, you have to reach out to X. 

(btw, there are is one issue blocking me, that I have mentioned in public. And one I that I noticed and may be related to the first, that I DCed you about, and I don't have an answer, or a way to know if it's my fault, if it's something that is being taken care of, or that nobody cares and I have to find a solution on my own. So... 🤔 )

fear is that managing something like zendesk would be a full time role

I generally like the idea but also think the bottom up / stochastic process we have now where things naturally percolate up is as much a feature as a bug for where we're at as a company

not opposed, it's possible something like GH with upvotes and user responses could sufficiently self-organize but seeing a good reference would be helpful in knowing what next steps to take. researching 100s of ticketing systems doesn't seem like a concrete step