Re: [edk2] Platform Specific Contribution

Subject: Re: [edk2] Platform Specific Contribution

From: Andrew Fish <afish@apple.com>

To: edk2-devel@lists.sourceforge.net

Date: 2013-07-30 17:11:38

> 
> 
>> Where everyone seems to agree is the platform package naming structure needs fixing. I'm happy with Andrew's suggestion, elaborated by Ryan.
>> 
>> I also agree with Olivier's suggestion of a root "Driver" directory.
>> 
>> While we're at it, we could also bring FatPkg and BaseTools into the EDK2 mainline. The former has an additional licensing term (see https://svn.code.sf.net/p/edk2-fatdriver2/code/trunk/FatPkg/License.txt) but I don't think that's a good enough reason to keep it separate. I guess the separation might be due to historical FAT licensing issues (e.g. each company having to seek their own license) but the Microsoft FAT license now explicitly allows use of FAT in any U(EFI) implementation so users of this package are no longer exposed to onerous licensing terms.
> 
> IANAL, but additional licensing terms must be taken very seriously. It
> makes it a different license. That particular clause is very
> definitely not an open-source term because it restricts the purpose
> that the code can be used for. I too would love to see the FAT package
> pulled into the main tree, but I think the license really needs to be
> resolved first.
> 

TINLA but the license is the license and it has been graciously contributed by the owner of the IP. It was also very nice of Microsoft to publish a spec so the driver could be constructed properly. 

Especially if we end up with a monolithic git tree maybe we should have a script to pull the different targets (and versions of things that are needed). The script could pull FAT project too. 

Thanks,

Andrew Fish

>> BaseTools development seems to be suffering from being in a different repository and there doesn't seem to be a good reason for it to be separate. Perhaps it would get more attention as part of the main repository?
> 
> Pretty please? Yes?
> 
> g.
> 
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel