Efficient priority queues in erlang
Functional Data Structures in Erlang and Elixir
an erlang implementation of the raft consensus protocol
a command-line commonmark / markdown query tool
Visualize how long it takes for people to get comments on their PRs
2018 Advent of Code, done in the greatest language ever
Sourcegraph blog, feature announcements, and website (about.sourcegraph.com)
PR opened NobbZ/erl_exercism
This fixes the deprecation warnings of
erlang:get_stacktrace() in erlang
pr created time in 4 hours
commit sha e34ef592324c2defc6c1501d95e284a81c2b9ae0
Update parse_trans to 3.3.0 This fixes the deprecation warnings of erlang:get_stacktrace() in erlang versions >=21.
push time in 4 hours
Small helper for the erlang track in exercism
fork in 4 hours
@mkoidin Thank you for responding and giving the transparency that you have thus far. I can sympathize with working iwth limited bandwidth, especially given just how many extenuating factors there have been in the time since the original comments. I'm coming at this as a fellow developer who very much "gets it", but also hopes to run a private instance of this software for myself (and possibly my friends and family).
As it is right now, do you think you could give an updated estimate of when/how long open sourcing the server code would take? If not, is there a way us folks could effectively influence the priority of that work?
Additionally, part of the strength of Mozilla is its ardent and often skilled fan community. I don't labor under delusions of person-months, but would you be able to take on volunteer talent operating under an NDA to assist in the open sourcing effort? I'm sure you'd find no shortage of volunteers in this thread, self included.
comment created time in a month
started time in a month