Bug 45232 - Lima: A free software driver for ARM's Mali GPUs
Summary: Lima: A free software driver for ARM's Mali GPUs
Status: RESOLVED INVALID
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: Project Creation Requests (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-25 07:24 UTC by Luc Verhaegen
Modified: 2012-01-29 00:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Luc Verhaegen 2012-01-25 07:24:28 UTC
project name: lima

Goal: providing open source support for ARM Mali GPUs.

I trust that this goal is in line with http://www.freedesktop.org/wiki/MissionStatement and that there are therefor no concerns towards accepting this.

Needed:
* mailinglist: lima@x.org
* bugzilla: only one component now, will need expansion in future.

No git space or files are needed at this point. I hope that this too is acceptable, i definitely see nothing disallowing that in http://www.freedesktop.org/wiki/NewProject
Comment 1 Daniel Stone 2012-01-26 15:09:38 UTC
The list would be lima@lists.x.org, strictly speaking, but is that really needed? Most drivers (including AMD) seem to get along just fine without a project-specific mailing list, and we have no end of now-dead lists on fd.o.

Also, you'll have to specify the desired product name, component name, short descriptions for both, and the default owner + QA contact for Bugzilla.
Comment 2 James Cloos 2012-01-26 16:07:42 UTC
> Most drivers (including AMD) seem to get along just fine without a
> project-specific mailing list,

Just to play devil’s advocate, xorg-driver-ati@lists.x.org is far from unused... ☺
Comment 3 Luc Verhaegen 2012-01-26 20:43:01 UTC
Daniel, I am rather thrilled that exactly you answered here.

Do you remember when we asked you whether you could help us create a radeonhd mailing list in XDC Cambridge in 2007? Do you remember what you answered then? Well, in case you do not remember, it was pretty much along the lines of what you stated just now.

Did not the radeonhd mailinglist become a huge success overnight, to the extent where i got personal attacks for refusing to create a separate mailinglist for user questions and one for devel stuff. Did not the fork/competing project, immediately grab the aforementioned mailinglist, which had, until that point, only been used for bugreports?

And did you not, repeatedly, give the radeonhd project crap for having gone with a suse mailing list, which we got in the space of 5 minutes? Do you really want me to go and dig out the 1-2 mailing list events where you do so, and the 1-2-more irc events?

Really, of all people who could answer here, i am most thrilled that _you_ did so. Thank you.
Comment 4 Daniel Stone 2012-01-26 20:50:05 UTC
Alright, cool, I'm not touching this bug anymore.  Life's too short.

(Whoops on the AMD thing though, that was a genuine mistake.  My bad.)
Comment 5 Luc Verhaegen 2012-01-27 04:58:52 UTC
Yes, well, there were several "Whoops"es, including several very well documented ones, for which your life definitely was not short enough.
Comment 6 Luc Verhaegen 2012-01-27 08:35:49 UTC
I am sorry, i should've know that attempting this would lead to such nasty exchanges again. There is way too much history there for me to ignore, and to stop me from reacting like that. I should've known better.

Getting a mailing list at fd.o still seems difficult. For any project like lima, it is important to get a mailing list around the time details become public. I'll create a mailinglist somewhere else for now, and we can always move to fd.o in future if there is the will.
Comment 7 Dave Airlie 2012-01-29 00:06:03 UTC
The fd.o admin is on holidays for another week or two, its actually his decision not Daniel. By now I'd have though Daniel would have learned to just STFU.

Reopen the bug for the fd.o admin to make a proper decision.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.