Hugging Face
Models
Datasets
Spaces
Buckets
new
Docs
Enterprise
Pricing
Website
Tasks
HuggingChat
Collections
Languages
Organizations
Community
Blog
Posts
Daily Papers
Hardware
Learn
Discord
Forum
GitHub
Solutions
Team & Enterprise
Hugging Face PRO
Enterprise Support
Inference Providers
Inference Endpoints
Storage Buckets
Log In
Sign Up
Ian Gardner
igardner
6
10
5
Follow
davanstrien's profile picture
hmb's profile picture
2 followers
·
9 following
igardner23
AI & ML interests
mischief
Recent Activity
updated
a collection
3 days ago
Check out later
replied
to
salma-remyx
's
post
12 days ago
If you can’t explain why your AI-generated contribution belongs in the repo, don’t put it in a maintainer’s queue 🙅🏻♀️ Before asking for review, you should be able to answer: 1. What project need does it address? 2. Where does it fit, and does it duplicate existing work? 3. What evidence shows it works, and will you own it through review? If you can’t answer those, you haven’t saved anyone time. You’ve passed the buck to the maintainer. Outrider has made us better contributors by doing more of this work before upstream review by * reading contribution rules, accepted PRs, and open issues * finding needs and integration points * drafting the code, tests, and context. We still decide what deserves to go upstream, verify the claims, coordinate with maintainers and contributors, and stay involved through review. On huggingface/peft, only 4 of 20 Outrider runs opened draft PRs. Two contributions have now merged: ✅ Riemannian-preconditioned LoRA: https://github.com/huggingface/peft/pull/3382 ✅ Super-Tuning: https://github.com/huggingface/peft/pull/3518 We have more contributions in review and far more ideas were filtered out before they reached a maintainer. Full case study: https://remyx.ai/case-study Outrider: https://github.com/remyxai/outrider
replied
to
salma-remyx
's
post
12 days ago
If you can’t explain why your AI-generated contribution belongs in the repo, don’t put it in a maintainer’s queue 🙅🏻♀️ Before asking for review, you should be able to answer: 1. What project need does it address? 2. Where does it fit, and does it duplicate existing work? 3. What evidence shows it works, and will you own it through review? If you can’t answer those, you haven’t saved anyone time. You’ve passed the buck to the maintainer. Outrider has made us better contributors by doing more of this work before upstream review by * reading contribution rules, accepted PRs, and open issues * finding needs and integration points * drafting the code, tests, and context. We still decide what deserves to go upstream, verify the claims, coordinate with maintainers and contributors, and stay involved through review. On huggingface/peft, only 4 of 20 Outrider runs opened draft PRs. Two contributions have now merged: ✅ Riemannian-preconditioned LoRA: https://github.com/huggingface/peft/pull/3382 ✅ Super-Tuning: https://github.com/huggingface/peft/pull/3518 We have more contributions in review and far more ideas were filtered out before they reached a maintainer. Full case study: https://remyx.ai/case-study Outrider: https://github.com/remyxai/outrider
View all activity
Organizations
None yet
igardner
's models
4
Sort: Recently updated
igardner/custom_chat_trained
Updated
Aug 1, 2022
igardner/test
Updated
Jan 2, 2022
igardner/degen_simulation
Updated
Dec 30, 2021
igardner/test_chat
Updated
Sep 9, 2021