11–20 of 279 posts
FWIW, we've got a #redux channel in the Reactiflux Discord where I and a couple other Redux maintainers hang out and answer an ongoing stream of questions. Not sure having specific "office hours" slots would work well for us, but we're happy to answer questions whenever we're around.
The very short consulting can be pretty intense. People come fast and furious and want answers. They sometimes are folks who really badly need a larger consulting or training engagement from a specialist, but can't afford it. So they sometimes come hard, sometimes frantically, looking for miracle fixes. I thought they could be fun, but you really had to be on your toes to do it well. And you need to set really clear…
Assuming that everybody has the luxury to have additional office hours available is a bit far from reality in my opinion.
I mean, if you can offer office hours for an open source project you probably are already so popular that you are able to work on it fulltime, right? And if you're not that popular, you cannot offer office hours due to your daytime job; as you would have to decrease the rest of your remaining free time that you probably need to sleep and eat.
Paranoid me is a little nervous about putting up a scheduling link publicly, but here goes:
I work on Typesense [1], which is an open source alternative to Algolia and an easier to use alternative to ElasticSearch. If you want to talk search and/or Typesense - DMs and Office Hours open: https://calendly.com/jason-typesense/typesense-office-hours
Anyone can run office hours for any of their open source projects they want - that sounds great! But I won't and I don't feel any sort of obligation to do so, so I don't think 'should' is really appropriate here.
I think the 'should' is targeted at developers who want their projects to grow (which is not all open-source developers).
So many conference talks' second slide is a "numbers" slide wit how many github stars, active contributors and other vanity metrics. It strikes me that the point is not just to convey that the project has an ecosystem behind it (with the implication there being that you can get free feature development and support), but to hit some sort of weird OKR-ish goal set.
FWIW, we've got a #redux channel in the Reactiflux Discord where I and a couple other Redux maintainers hang out and answer an ongoing stream of questions. Not sure having specific "office hours" slots would work well for us, but we're happy to answer questions whenever we're around.
Mark’s Twitter feed is also entirely redux based. ;p
I also tweet about a lot of React stuff:
https://twitter.com/acemarke/status/1365874077177700361
https://twitter.com/acemarke/status/1366102388399087619
and on rare occasions, things that are _not_ React or Redux related :)
We’ve been working with the Nuxt.js team and iterating on the product for over a year. It has become a full featured live chat, and invoicing system, with a contact widget for onboarding clients.
Feel free to email me at dylan@otechie.com if you’re interested