Hello, Chris's "keynote" at the LLVM Developers' Conference included a call for code owners, and my company has a heavy dependency on Bitcode, I propose taking ownership of: lib/Bitcode/* include/Bitcode/* This means that I'll be committed to documenting (yay) the implementation and responsible for reviewing patches and commits, as well as overall code quality and maintenance. It's a small section of the overall tree, and I realize that it is a critical portion that touches virtually the whole project. If someone else already "owns" this part, please let me know. Looking at the commits of BitcodeReader.cpp, the folks that have the most invested are: lattner - 101 djg - 32 dpatel - 30 void - 27 resistor - 22 johannes - 14 nicholas - 12 foad - 12 hernande - 10 baldrick - 9 I <3 bitcode and would love to be responsible for it. That being said, my next step would be to prove it through writing documentation and submitting more patches that align with the design philosophies of the project. Thanks for your attention! Joe ______________________________ Joe Abbey Director of Software Development Arxan Technologies jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com<http://www.arxan.com/> Protecting the App Economy™ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121110/21a578cf/attachment.html>
On Nov 10, 2012, at 10:43 AM, Joe Abbey <jabbey at arxan.com> wrote:> Hello, > > Chris's "keynote" at the LLVM Developers' Conference included a call for code owners, and my company has a heavy dependency on Bitcode, I propose taking ownership of: > > lib/Bitcode/* > include/Bitcode/* > > This means that I'll be committed to documenting (yay) the implementation and responsible for reviewing patches and commits, as well as overall code quality and maintenance. It's a small section of the overall tree, and I realize that it is a critical portion that touches virtually the whole project.This sounds like a great idea to me. Unless someone objects in the next few days, consider it yours :). Please update docs/DeveloperPolicy to list yourself in the owners section. Thanks Joe, -Chris> > If someone else already "owns" this part, please let me know. Looking at the commits of BitcodeReader.cpp, the folks that have the most invested are: > > lattner - 101 > djg - 32 > dpatel - 30 > void - 27 > resistor - 22 > johannes - 14 > nicholas - 12 > foad - 12 > hernande - 10 > baldrick - 9 > > I <3 bitcode and would love to be responsible for it. That being said, my next step would be to prove it through writing documentation and submitting more patches that align with the design philosophies of the project. > > Thanks for your attention! > > Joe > ______________________________ > Joe Abbey > Director of Software Development > Arxan Technologies > jabbey at arxan.com www.arxan.com > Protecting the App Economy™ > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121110/cf1cedee/attachment.html>
Hi Joe,> Chris's "keynote" at the LLVM Developers' Conference included a call for code > owners, and my company has a heavy dependency on Bitcode, I propose taking > ownership of: > > lib/Bitcode/* > include/Bitcode/* > > This means that I'll be committed to documenting (yay) the implementation and > responsible for reviewing patches and commits, as well as overall code quality > and maintenance.just to be clear, I don't think you are obliged to do everything yourself, you can always ask someone else to review a particular patch and so on. It's more that your job is to ensure that patches do get timely review, that documentation does get written, the code is cleaned and refactored etc. Ciao, Duncan.
On Nov 11, 2012, at 12:44 AM, Chris Lattner wrote:> > On Nov 10, 2012, at 10:43 AM, Joe Abbey <jabbey at arxan.com> wrote: > >> Hello, >> >> Chris's "keynote" at the LLVM Developers' Conference included a call for code owners, and my company has a heavy dependency on Bitcode, I propose taking ownership of: >> >> lib/Bitcode/* >> include/Bitcode/* >> >> This means that I'll be committed to documenting (yay) the implementation and responsible for reviewing patches and commits, as well as overall code quality and maintenance. It's a small section of the overall tree, and I realize that it is a critical portion that touches virtually the whole project. > > This sounds like a great idea to me. Unless someone objects in the next few days, consider it yours :). Please update docs/DeveloperPolicy to list yourself in the owners section. Thanks Joe,Is there a particular sub-system size that makes sense to mark as owned? I have been reworking the library call simplification infrastructure recently and will be happy to sign up as an owner for that. -- Meador Inge CodeSourcery / Mentor Embedded http://www.mentor.com/embedded-software
On Nov 11, 2012, at 4:30 AM, Duncan Sands <baldrick at free.fr> wrote:> Hi Joe, > >> Chris's "keynote" at the LLVM Developers' Conference included a call for code >> owners, and my company has a heavy dependency on Bitcode, I propose taking >> ownership of: >> >> lib/Bitcode/* >> include/Bitcode/* >> >> This means that I'll be committed to documenting (yay) the implementation and >> responsible for reviewing patches and commits, as well as overall code quality >> and maintenance. > > just to be clear, I don't think you are obliged to do everything yourself, you > can always ask someone else to review a particular patch and so on. It's more > that your job is to ensure that patches do get timely review, that documentation > does get written, the code is cleaned and refactored etc.Yep, I'll be sure to make sure I don't make Bitcode my precious. Updated CODE_OWNERS.TXT in r167881 Joe
> I <3 bitcode and would love to be responsible for it. That being said, my > next step would be to prove it through writing documentation and submitting > more patches that align with the design philosophies of the project.You will probably find this useful when it comes time to write new documentation: <http://www.llvm.org/docs/SphinxQuickstartTemplate.html> -- Sean Silva On Sat, Nov 10, 2012 at 1:43 PM, Joe Abbey <jabbey at arxan.com> wrote:> Hello, > > Chris's "keynote" at the LLVM Developers' Conference included a call for > code owners, and my company has a heavy dependency on Bitcode, I propose > taking ownership of: > > lib/Bitcode/* > include/Bitcode/* > > This means that I'll be committed to documenting (yay) the implementation > and responsible for reviewing patches and commits, as well as overall code > quality and maintenance. It's a small section of the overall tree, and I > realize that it is a critical portion that touches virtually the whole > project. > > If someone else already "owns" this part, please let me know. Looking at > the commits of BitcodeReader.cpp, the folks that have the most invested are: > > lattner - 101 > djg - 32 > dpatel - 30 > void - 27 > resistor - 22 > johannes - 14 > nicholas - 12 > foad - 12 > hernande - 10 > baldrick - 9 > > I <3 bitcode and would love to be responsible for it. That being said, my > next step would be to prove it through writing documentation and submitting > more patches that align with the design philosophies of the project. > > Thanks for your attention! > > Joe > ______________________________ > Joe Abbey > Director of Software Development > Arxan Technologies > jabbey at arxan.com www.arxan.com > Protecting the App Economy™ > > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >