As a Developer, Gallium looks far more attractive then MESA. Having one unified standard for N number of API's is frankly every OS should have done a VERY long time ago.
Announcement
Collapse
No announcement yet.
Mesa's Rate Of Git Development Is Slowing
Collapse
X
-
Originally posted by uid313 View PostCould not find a roadmap.
But if you want to contribute:
Join mailing list: http://www.mesa3d.org/lists.html
Read OpenGL documentation: http://www.opengl.org/documentation/
for sure this is the first time iv ever realized it even existed.
"Help Wanted / To-Do List
We can always use more help with the Mesa project. Here are some specific ideas and areas where help would be appreciated:
Driver patching and testing. Patches are often posted to the mesa3d-dev mailing list, but aren't immediately checked into git because not enough people are testing them. Just applying patches, testing and reporting back is helpful.
Driver debugging. There are plenty of open bugs in the bug database.
Remove aliasing warnings. Enable gcc -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing issues in the code.
Windows driver building, testing and maintenance. The Visual Studio project files aren't always updated in a timely manner when new source files are added or old ones are removed. Fixing these tends to delay new Mesa releases.
Maintenance and testing of lesser-used drivers. Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being deprecated starting in Mesa 7.3.
Contribute more tests to glean.
Automatic testing. It would be great if someone would set up an automated system for grabbing the latest Mesa code and run tests (such as glean) then report issues to the mailing list.
If you want to do something new in Mesa, first join the Mesa developer's mailing list. Then post a message to propose what you want to do, just to make sure there's no issues.
Anyone is welcome to contribute code to the Mesa project. By doing so, it's assumed that you agree to the code's licensing terms.
Finally:
Try to write high-quality code that follows the existing style.
Use uniform indentation, write comments, use meaningful identifiers, etc.
Test your code thoroughly. Include test programs if appropriate."
you should probably also add/emphasise routinely benchmark your changes and publicly post your results, write and add to a new and comprehensive test suite to automate testing for correctness, auto bench marking and auto reporting of these results to a single central location these and other changes in the futureLast edited by popper; 25 June 2012, 03:52 PM.
Comment
-
Maintenance and testing of lesser-used drivers. Drivers such as DOS/DJGPP, GGI, etc that aren't being maintained are being deprecated starting in Mesa 7.3.
Am I the only person who realizes how idiotic that is?
Also, the fact MESA needs so many drivers for different architectures is why I hope Gallium replaces it. One interface, one backend.
Comment
-
Originally posted by WorBlux View Postor planning their next moves.
I have not looked at the article very well, but I think it only counts the commits to master and not to other branches.
Comment
-
Originally posted by asdxAgreed, we also need patents like ST3C to become invalid and integrate all that stuff into Mesa by default.
Originally posted by asdxWhy is this happening? How can we help with things?
Originally posted by asdxIs Mesa being backed by companies like Canonical
Originally posted by asdxRed Hat,
Oh, wait. Except that he does. Remember the "UNTESTED CRAP" fiasco?
Originally posted by asdxetc?
A lot of people who are either unaffiliated with a company, or working for some small business, are significant contributors to Mesa and/or the DRM stack. While a "majority" of the work may be done by large enterprises such as Intel, VMware and Red Hat, the individual / small business contributor is a huge part of Mesa.
Originally posted by asdxWho are the major Mesa contributors?
In the approximate descending order by level of commitment (first one is most committed/best contributor IMHO): Red Hat, VMware, Intel, AMD, a few dedicated people who are unemployed or whose day job is unrelated to graphics drivers, Google, PathScale, Oracle, Apple, IBM, and a "long tail" of people from various companies and individuals who have between 1 and 10 commits (in other words, not a whole lot).
Comment
-
Originally posted by allquixotic View Posta few dedicated people who are unemployed or whose day job is unrelated to graphics driversTest signature
Comment
-
Originally posted by bridgman View Post"At school" sounds better than "unemployed". The most common pattern is "working on open source drivers is more interesting than finishing my doctoral thesis"
Comment
-
Originally posted by asdxRed Hat, Intel, VMware and AMD should sue the hell out of HTC over that fucking ST3C patent.
But seeing as HTC likes to make android-devices maybe they should approach them asking if they can have a no-suing-over-this/these-patents-aggreement for the good of the Linux ecosystem. I think it would be a win for HTC too.
Comment
Comment