Re: [myhdl-list] MEP guidelines
Brought to you by:
jandecaluwe
From: Jan D. <ja...@ja...> - 2011-05-18 18:58:57
|
On 05/06/2011 05:03 PM, Günter Dannoritzer wrote: > Hi, > > I would like to suggest, adding some guidelines about the MEP process. > Seeing that the text of an already implemented MEP got changed, I think > it would be helpfull to have some guidelines how the MEP process is > intended. > > I think, that especially an already implemented MEP should be kept for > reference as is and not changed later in time. There is the chance, that > the original notion of the implementation gets altered by editing the > MEP it originated from. Now that we have the guidelines, let me comment on that particular edit itself, which I found very problematic. First, the document in question was clearly marked as "Final". I think that makes it obvious that one should be very careful when editing, regardless of any guidelines. Second, the edit was about an issue that the editor was clearly struggling with. He had received several references, as well as repeated advice to study an introductory text to HDL-based design. Still, he felt confident enough to make a drastic edit. Most importantly, the edit content was completely wrong, both in the details and in the concepts. My conclusion: wiki's don't work, at least not the "democratic" access rights part of them. As a result, I'm changing the policy to grant edit access to myhdl.org. Instead of a simple request, I will require a demonstrated level of experience with MyHDL. I have already implemented this by restoring content as appropriate, updating the page about access request, and updating the existing access rights. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com Analog design automation: http://www.mephisto-da.com World-class digital design: http://www.easics.com |