Contributing to the #FreeBSD ports collections sometimes feels a bit hopeless. You put in a bit of work to update an existing port or add a new one, submit it, and then ...... nothing.For weeks, months sometimes.Until you've all but forgotten you made the contribution, and out of the blue you get an email that the patch was accepted or rejected.Not the most motivating way of getting involved I must say.
7 Comments
charlesrocket@defcon.social · 0 pts · 56d
@gmc it’s hard sometimes, one of my ports was in that limbo for a few years
gmc@snac.chasmcity.net · 0 pts · 56d
Ouch, I haven't experienced it that bad yet!
CC: @charlesrocket@defcon.social
charlesrocket@defcon.social · 0 pts · 56d
@gmc to be fair, sometimes it’s less than couple hours. it all depends on the lang/stack of the port and committers’ availability
gmc@snac.chasmcity.net · 0 pts · 56d
I've never had it that fast either :)
CC: @charlesrocket@defcon.social
charlesrocket@defcon.social · 0 pts · 56d
@gmc not common, but possible) if you need some help getting things done—feel free to ping, maybe i could assist with a push. id say right away submit with the phabricator as the last resort. it has a bit of a graveyard reputation (tho stuff still gets merges)
gmc@snac.chasmcity.net · 0 pts · 55d
Not sure what phabricator is, I just followed the documented procedure and submitted to bugs.freebsd.org. I've currently got 3 in the queue:
That last one is brand new, I just submitted that minutes ago :) The first one has been in there for > 1.5 months now, and the middle one is also relatively new (a week old now).
CC: @charlesrocket@defcon.social
charlesrocket@defcon.social · 0 pts · 55d
@gmc phabricator is just an alternative to bugzilla/github. heads-up, ports had an incident, so i expect no movements for a while (tho everything is resolved by now iirc)