Leebra rustlang
login register

Lemmy is in serious need of more devs [CROSS POST]

3 years ago by provisional to c/rustlang

save

share

report

cross-posted from: https://beehaw.org/post/570507

After the (temporary) defederation announcement of earlier i checked the Lemmy repo to see if there was already a ticket on the federation limiting option like Mastodon’s that people mentioned Lemmy doesn’t yet have. Not only i didn’t find it, i also saw that there’s about 200+ open tickets of variable importance. Also saw that it’s maintained mostly by the two main devs, the difference in commits between them and even the next contributors is vast. This is normal and in other circumstances it’d grow organically, but considering the huge influx of users lately, which will likely take months to slow down, they just don’t have the same time to invest on this, and many things risk being neglected. I’m a sysadmin, haven’t coded anything big in at least a decade and a half beyond small helper scripts in Bash or Python, and haven’t ever touched Rust, so can’t help there, but maybe some of you Rust aficionados can give some time to help essentially all of Lemmy. The same can be said of Kbin of course, although that’s PHP, and there is exacerbated by it being just the single dev.

Aloso 18 points 3 years ago

i also saw that there’s about 200+ open tickets of variable importance

Note that it is normal that the number of open issues grows faster than issues are resolved. For example, rust-lang/rust has 8,963 open issues and 39,803 closed issues. microsoft/TypeScript has 6,001 open issues and 31,397 closed issues. A large number of open issues isn't necessarily concerning, unless high-priority issues (vulnerabilities and critical bugs) stay open for a long time.

save

path: 0 246840, hotness: undefined, score: 18, children: 0
druppel 16 points 3 years ago

I was thinking about learning rust and contribute to open source projects, so it might be a good option. I do have a laundry list of notes about the platform itself though

save

path: 0 226909, hotness: undefined, score: 16, children: 0
G0ldenSp00n 16 points 3 years ago

Definitely planning to contribute, when I get some free time. I probably try to dive into the codebase next week at some point. Still new to learning Rust, but I would love to get some experience in a project like this.

save

path: 0 228149, hotness: undefined, score: 16, children: 0
thesanewriter 15 points 3 years ago

I spent the latter portion of the day learning Rust and starting work on a new Lemmy feature. Hopefully it won't take long to get it fully functional.

save

path: 0 241173, hotness: undefined, score: 15, children: 10
hardypart 14 points 3 years ago

I can't tell if this is satire, lol

save

path: 0 241173 250972, hotness: undefined, score: 14, children: 9
zzzthelastuser 13 points 3 years ago

Sounds sincere to me. I don't think he meant he just started learning rust from hello world the other day and now wants to improve lemmy.

save

path: 0 241173 250972 252889, hotness: undefined, score: 13, children: 8
thesanewriter 16 points 3 years ago

Oh yeah, I'm actually a software engineer. I had experience with C and Java, as well as some higher-level languages like Javascript and Python, so for learning Rust it has mainly moreso been learning which function is in which library and how the syntax for the language works, rather than learning programming fundamentals.

save

path: 0 241173 250972 252889 254392, hotness: undefined, score: 16, children: 7
barsoap 1 point 3 years ago

Oh my sweet summer child :)

Remember that borrowck is not out to hurt you, it wants to help you, guide you towards enlightenment, and does so with grandfatherly kindness: Making you feel completely stupid.

If you hit a wall make sure to check out the Rust book and work through it, or at least read it: Unless your language background is very specific (let's see C/Pascal or such, plus Haskell, plus very obscure research-grade ML dialects with region-based memory management) Rust semantics are going to kick your ass sooner or later.

save

path: 0 241173 250972 252889 254392 276897, hotness: undefined, score: 1, children: 6
paperemail 10 points 3 years ago

I’ll see if there are any issues I can pick up

save

path: 0 232387, hotness: undefined, score: 10, children: 0
PrincipleOfCharity 2 points 3 years ago

I’m not super concerned. It’s been a little over a week since stuff hit the fan. Contributors need time to learn the code base. People are starting to help with the easy stuff, but the two main devs still need to check everything because they are the only ones that can understand how those changes affect long term visions. Also, the urgent fixes are all somewhat-breaking changes which is why it’s looking like the next release is going to be 0.18 instead of 0.17.5. It makes sense to get as many urgent breaking changes in as they can before publishing, and it’s only been 8 days since the last release to identify, code, and test.

save

path: 0 416401, hotness: undefined, score: 2, children: 0
savoy 1 point 3 years ago

I've been meaning to keep practicing Rust to hopefully contribute (since 2020), but I never have enough time :/ I'm hoping towards the end of the year I'll have time to get back into it; I could even have time to start the few side projects I've kept off!

save

path: 0 288468, hotness: undefined, score: 1, children: 0
rustlang
rustlang

@lemmyrs.org

login for more options
709
114
1

Rules [Developing]

Observe our code of conduct

  • Strive to treat others with respect, patience, kindness, and empathy.
  • We observe the Rust Project Code of Conduct.
  • Submissions must be on-topic
  • Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
  • Post titles should include useful context.
  • For Rust questions, use the stickied Q&A thread. [TBD]
  • Arts-and-crafts posts are permitted on weekends.
  • No meta posts; message the mods instead.

Constructive criticism only

  • Criticism is encouraged, though it must be constructive, useful and actionable.
  • If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
  • Keep things in perspective
  • A programming language is rarely worth getting worked up over.
  • No zealotry or fanaticism.
  • Be charitable in intent. Err on the side of giving others the benefit of the doubt.

No endless relitigation

  • Avoid re-treading topics that have been long-settled or utterly exhausted.
  • Avoid bikeshedding.
  • This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.

No low-effort content

  • Showing off your new projects is fine

No memes or image macros

  • Please find other communities to post memes

No NSFW Content

  • There are many other NSFW communities, let’s keep this related to the language

go to feed...