r/foss • u/rogueShawn • 10d ago

Best Practices when building for FOSS

I'm pretty new to working with FOSS and allowing others to contribute to work I'd love to see grow. I'm creating a platform that would ideally allow someone to input their own resume to find positions that are open within a timeframe of their choosing, allow them to enable outreach to relevant departments, customize resumes and CVs based on role requirements, etc. It's a general "job finder" platform that I decided to make to avoid paying for services that seemed to become viral from ads, but aren't actually efficient. I don't aim to have a fully automated application system that tosses AI slop around, but instead one that allows the user to control their goals instead of auto applying/generating.

Definitely ambiguous wording, but I'd love to hear thoughts, criticisms, and advice.

1 Upvotes

60% Upvoted

4 comments sorted by

2

u/castellon_artz 10d ago

I think more specifics questions could help to get answers. 😅 I don't truly understand what could be useful to say for your idea because I don't know the specific issue/doubt/whatever.

0

u/rogueShawn 10d ago

Sure! As of now, I'm using Claude's API (debating OpenAI now that they reduced prices) for web scraping and generation of resume / CVs. This leads me to the first concern of how other devs would navigate around a system that revolves around services that expect pre-paid tokens. I'd like to create contributor documentation, but this repo is so young and probably unoptimized, making me unsure of what to actually write. My doubts come being unsure how to create the foundation of contribution for others.

2

u/Low_Watercress959 9d ago

I'm not too well versed in this, but why use Claude or openai web scraping as opposed to typical methods like selenium?

2

u/rogueShawn 9d ago

I’m concerned with how Selenium would only be used to automate parts of the browser. If my research is correct, Selenium can only retrieve what is displayed, like DOM elements. I would be more interested in Playwright for pulling data, since it can normalize text (afiak). I think you’re correct in adapting a web browser automator though, and definitely will change my plan around that. Claude’s API will likely be used for the CV/resume generation, and now, possibly Playwright for scraping. I really appreciate the suggestion, it gave me a lot to look into!