llvm / community.o Goto Github PK
View Code? Open in Web Editor NEWCommunity.o website and other resources
Community.o website and other resources
The idea is that having a dockerfile available will remove a number of potential build issues that newcomers could struggle with.
At the moment, our sponsors donate money. This is great, and we really don't want that to stop.
Discussions at the 2024 EuroLLVM community.o workshop made it sound like we are a little short of volunteers. One idea was to allow sponsors to donate time instead of money.
Benefits:
Risks:
Next steps:
Could the project aim to have one or a few mentors explicitly mentioned on every “good first issue” github issue, so that people can find out who could help them with getting started on a specific issue?
lnihlen documented much of the process by doing this herself on the llvm forums. It would be great to have this information on a live doc that includes the work it takes, who to follow up with if it requires manual work and if it's a similar process for folks who may only want to e.g. change their email address.
The path to code owner is not documented.
We should revisit project wide policies/documentation on how code owners are nominated, how someone can set out on a path to become a code owner, and determine how to ensure that we are casting a wide net of candidates.
We need to create a list of roles within the community that provide entry points in the community and documentation on how to fulfill these roles.
Examples:
It would be great to have a bigger presence for welcoming newcomers on the main page. Tangentially this is something a professional web designer can help out with too.
At the EuroLLVM 2024 community.o workshop, many newcomers point out that a lot of areas in LLVM are underdocumented. The backend was highlighted as especially lacking.
One idea we had was that maybe the best way to improve documentation is that when the documentation isn't good enough for what you need to work on; you (as a newcomer) should write up a pull request with documentation describing how you think how it works. Even if it's wrong, that's the best way to get the people with more experience to point you in the right direction. And as a side-effect, the project's documentation improves. This should be documented clearly as a "the most powerful way to get the documentation you need to be created".
Of course, this is at odds with newcomers often feeling "social anxiety" to do anything publicly.
How could we help overcome this?
From our community.o workshop discussion:
I think the reason that most community.o issues don't get a lot of active contribution, despite good will from the llvm community in general, is that most contributors are either students or paid employees. As such, they have to "dance with the ones that brought them," and so community contribution would need to take up mostly personal time. It isn't fair to ask folks to work on community stuff with their personal time.
Some video games rely on strong community interaction, and the games industry has developed a skillset for community managers. These folks are critical for the success of online games, and are paid employees who keep busy managing their online communities. I'm not certain if there's a similar set of paid professionals with experience in open source, but I think the Foundation would have the most success on advancing community issues by having a person who is accountable for advancing the work.
The LLVM project consists of mainly a huge C++ code base.
Navigating and bit-by-bit understanding a huge C++ code base is one of the key skills people need to be able to contribute code most effectively.
Could the project document/recommend a few approaches to learn this skill?
It would be great for a bot to detect PRs, especially by newcomers, who haven't gotten a reaction.
The bot should:
This came out of Euro LLVM 2024 newcomer improvement roundtable
Problem is that getting toy tutorial to run is hard.
Toy tutorial could be self-contained in a separate repository; s.t. it is obvious how to do self-contained enlist, build and run it, w/o guessing. Result would be a new repository with a documentation somewhere that starts with enlisting into LLVM and finishes with running chapter one of tutorial.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.