On Sat, 2012-04-07 at 10:40 +0300, Stefan Kristiansson wrote:
> On Fri, Apr 06, 2012 at 07:17:09AM -0700, Ouabache Designworks wrote:
> > Stefan.
> >
> > Is there a process document somewhere that spells out the exact steps
> > needed to create and submit a patch? I know that it is familiar to most
> > software engineers but it is not as common in hardware design. Pulling
> > together the groups expectations and knowledge and putting it all in one
> > place would help a lot.
> >
>
> I agree, the closest thing we have to something like that
> right now is this (very incomplete) page:
> http://opencores.org/or1k/Contributor_Guidelines
>
> That should be updated with some general guidelines about patch-submission.
And more specifically this points to the Wiki guideline for Or1ksim
(lots of detail on what is wanted, but not how to submit) and ORPSoC
("succinct").
http://opencores.org/or1k/Or1ksim#Contributing
http://opencores.org/or1k/ORPSoC#Contributing
I've fixed the former (or at least I will have once opencores.org comes
back up), and added a MAINTAINERS file to Or1ksim. I leave it to someone
else to update the rules for ORPSoC (and possibly add something for
OpenRISC).
HTH,
Jeremy
--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.benn...@embecosm.com
Web: www.embecosm.com
_______________________________________________
OpenRISC mailing list
OpenRISC@lists.openrisc.net
http://lists.openrisc.net/listinfo/openrisc
