Martin Roth wrote:
> Thanks Peter,
>
> Is there a time limit that you think is appropriate to request
> maintenance for?
Ideally no mainboard directory has any copy-pasted code, and every
contributor who adds a board has already been or follows up by
eliminating some hack outside their immediate
> True, however we can still set expectation even if there is no way to enforce
> it. This would be more of a social norm than a hard requirement, but it does
> help to know that if you are e.g. pushing an entire board into coreboot, that
> to keep it in tree you are expected to do amount of
- Original Message -
> From: "Julius Werner"
> To: "Timothy Pearson"
> Cc: "Martin Roth" , "Peter Stuge" ,
> "coreboot"
> Sent: Thursday, May 2, 2019 5:23:58 PM
> Subject: Re: [coreboot] Re: What maintenance
codebase. :)
>
> - Original Message -
> > From: "Martin Roth"
> > To: "Peter Stuge"
> > Cc: "coreboot"
> > Sent: Thursday, May 2, 2019 4:16:41 PM
> > Subject: [coreboot] Re: What maintenance is expected from coreboot
> &g
tuge"
> Cc: "coreboot"
> Sent: Thursday, May 2, 2019 4:16:41 PM
> Subject: [coreboot] Re: What maintenance is expected from coreboot developers
> & companies
> Thanks Peter,
> Is there a time limit that you think is appropriate to request
> maintenance
Thanks Peter,
Is there a time limit that you think is appropriate to request
maintenance for?
Obviously it's not reasonable to request that they maintain it
forever, but is 2 years after the initial push reasonable? 3 years?
What level of maintenance would be expected? Would we just
Martin Roth wrote:
> I'd like to discuss the issue of what's expected from developers after
> code is added to the coreboot tree.
Thanks for bringing this up.
> It seems like there's a feeling
> that if a company pushes code to coreboot, or hires someone to push
> code to coreboot that there's
7 matches
Mail list logo
