general-en

patcon 2022-04-01 16:05:27

Ahhhhh so neat! And SO true:

> may paint an illusion that anyone can pitch their ideas

patcon 2022-04-01 16:12:00

When I did my compare/contrast section of my http://link.g0v.network/patcon-g0v-report I thought I got a lot of the key differences between Toronto's weekly hacknights and Taiwan's bimonthly hackathons, but I totally missed thinking about how "project support" and "project kick-off" philosophies need to differ...!

The bi-monthly weekend hackathons have a lot of perks (family friendly, ability for busy people to feel like they can keep up, etc) but it sounds like it makes it so that new project pupport is REALLY important, because if they don't launch well, then it's 2 months before they get a chance to learn again. This makes me appreciate how important it is to have someone like yourself sitting in on projects to help them learn in the best possible way 🤔

patcon 2022-04-01 16:15:23

With weekly hacknights, our main concern is to make ppl feel like they're having fun and meeting nice ppl. We are happy to let new project leads make mistakes and "do it wrong", so long as they know that doing it wrong is ok, and just come back next week and try again. Old-timers will often sit in on new projects and support, but that can happen on the first or second or third week pitching.

Our main critical task isn't making sure that they pitch or run their project well on week 1, but rather that they feel welcome to come back, no matter how it seems to go. So we try to tell them that failure is ok, because you can change things next week, or maybe new ppl will be here next week, and the same thing you did this week will work next week (aka it's kinda random) 😊

patcon 2022-04-01 16:17:15

And we try to share with them the importance of their first participant, bc that person makes it less scary for others to join. So if you get along with them, and they're willing, maybe just work on making them fall in love with the project on week #1. and then try to get _them_ to pitch the next week (so they have ownership and feel compelled to come back)

patcon 2022-04-01 16:19:33

I am starting to think that Toronto and Taiwan as BOTH right about this, and that we should try to figure out how to have both weekly hacknights and bimonthly hackathons. Toronto runs weekly hacknights and an annual hackathon, and these work together MAGICALLY: weekly hacknights for community building and socializing, and annual hackathons for big partnerships and fundraising (opportunity for supporters to sponsor us for waaaaay more than it takes to run the event, which lasts us through the year)

ael 2022-04-03 10:21:09

#vtaiwan used to be a weekly meetup taking new participants as their fist step involving more in g0v community with old-timers. @lisa, What do you think?

There are some weekly meetups of g0v projects, but they are independent projects, which many choose Wednesday night as the meetup night.

Besides a community building event, bi-monthly hackathons, from my perspective, are to gather diverse specialties to brainstorm project ideas and recruit contributors in a 100 ppl pool, which would be hard to attract that many talents at once in weekly ups.

As for “the best practice,” perhaps it is only me that being controlling lol I totally agree with you that making participants feel welcomed and engage the first participant are important, which they, #ohshown participants, already did.

It is okay to get it straight in the first few weeks and through the entire project. You are right. I was afraid that without proper planing the project, the next time they can consult old-timers would be 2 months later and participants may be too frustrated by then.

ael 2022-04-03 10:24:24

Another reason was that they decided to fork #disfactory codebases, which was a project I participated in as the product manager. I was very confused how come forking a factory-reporting platform would be the best practice for a Black Bear reporting system

ky 2022-04-03 15:28:32

Well, I think it’s not very healthy to make a certain project became an entrance of g0v community ha, but I agreed that it’s important to have a weekly newbie friendly event.
Code for San Jose have a weekly orientation event to explain existing projects, I think that will be great and I think I might make a proposal recently.

patcon 2022-04-13 04:11:39

I am 💯 interested in any conversations about this sorta thing and this aorta dynamic

patcon 2022-04-01 16:05:27

Ahhhhh so neat! And SO true:

> may paint an illusion that anyone can pitch their ideas

patcon 2022-04-01 16:12:00

When I did my compare/contrast section of my http://link.g0v.network/patcon-g0v-report I thought I got a lot of the key differences between Toronto's weekly hacknights and Taiwan's bimonthly hackathons, but I totally missed thinking about how "project support" and "project kick-off" philosophies need to differ...!

The bi-monthly weekend hackathons have a lot of perks (family friendly, ability for busy people to feel like they can keep up, etc) but it sounds like it makes it so that new project pupport is REALLY important, because if they don't launch well, then it's 2 months before they get a chance to learn again. This makes me appreciate how important it is to have someone like yourself sitting in on projects to help them learn in the best possible way 🤔

patcon 2022-04-01 16:15:23

With weekly hacknights, our main concern is to make ppl feel like they're having fun and meeting nice ppl. We are happy to let new project leads make mistakes and "do it wrong", so long as they know that doing it wrong is ok, and just come back next week and try again. Old-timers will often sit in on new projects and support, but that can happen on the first or second or third week pitching.

Our main critical task isn't making sure that they pitch or run their project well on week 1, but rather that they feel welcome to come back, no matter how it seems to go. So we try to tell them that failure is ok, because you can change things next week, or maybe new ppl will be here next week, and the same thing you did this week will work next week (aka it's kinda random) 😊

patcon 2022-04-01 16:17:15

And we try to share with them the importance of their first participant, bc that person makes it less scary for others to join. So if you get along with them, and they're willing, maybe just work on making them fall in love with the project on week #1. and then try to get _them_ to pitch the next week (so they have ownership and feel compelled to come back)

patcon 2022-04-01 16:19:33

I am starting to think that Toronto and Taiwan as BOTH right about this, and that we should try to figure out how to have both weekly hacknights and bimonthly hackathons. Toronto runs weekly hacknights and an annual hackathon, and these work together MAGICALLY: weekly hacknights for community building and socializing, and annual hackathons for big partnerships and fundraising (opportunity for supporters to sponsor us for waaaaay more than it takes to run the event, which lasts us through the year)

ael 2022-04-03 10:21:09

#vtaiwan used to be a weekly meetup taking new participants as their fist step involving more in g0v community with old-timers. @lisa, What do you think?

There are some weekly meetups of g0v projects, but they are independent projects, which many choose Wednesday night as the meetup night.

Besides a community building event, bi-monthly hackathons, from my perspective, are to gather diverse specialties to brainstorm project ideas and recruit contributors in a 100 ppl pool, which would be hard to attract that many talents at once in weekly ups.

As for “the best practice,” perhaps it is only me that being controlling lol I totally agree with you that making participants feel welcomed and engage the first participant are important, which they, #ohshown participants, already did.

It is okay to get it straight in the first few weeks and through the entire project. You are right. I was afraid that without proper planing the project, the next time they can consult old-timers would be 2 months later and participants may be too frustrated by then.

ael 2022-04-03 10:24:24

Another reason was that they decided to fork #disfactory codebases, which was a project I participated in as the product manager. I was very confused how come forking a factory-reporting platform would be the best practice for a Black Bear reporting system

ky 2022-04-03 15:28:32

Well, I think it’s not very healthy to make a certain project became an entrance of g0v community ha, but I agreed that it’s important to have a weekly newbie friendly event.
Code for San Jose have a weekly orientation event to explain existing projects, I think that will be great and I think I might make a proposal recently.

patcon 2022-04-13 04:11:39

I am 💯 interested in any conversations about this sorta thing and this aorta dynamic