OpenLLM-France/wikimedia huggingface dataset:
# Georgia Water/Policy/Georgia Erosion and Sedimentation Act/OCGA Sections

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
<< Chapter 2. Water Policy | 2.3. Georgia Water Law | Georgia Erosion and Sedimentation Act
Note: A summary of specific provisions for each code section is here.
Overview of the Act, by code section
12-7-1. Short title. This chapter shall be known and may be cited as the
    "Erosion and Sedimentation Act of 1975, as amended."
12-7-2. Legislative findings; policy of state and intent of chapter. 12-7-3. Definitions. 12-7-4. Adoption of comprehensive ordinances relating to land-disturbing activities;
       delegation of responsibility to planning and zoning commission;
       other local ordinances relating to land development;
       effect of chapter on design professionals.
12-7-5. Adoption of rules and regulations for localities without ordinances. 12-7-6. Best Management Practices;
       minimum requirements for rules, regulations, ordinances, or resolutions.
12-7-7. Permit or notice of intent required for land-disturbing activities;
       approval of application and issuance of permit;
       denial of permit;
       bond requirement.
12-7-7.1. Erosion and sediment control plan prepared; completion; implementation. 12-7-8. Certification of locality as local issuing authority;
       periodic review;
       procedure for revoking certification;
       enforcement actions.
12-7-9. Applications for permits;
       erosion and sediment control plans and data;
       time for issuance or denial.
12-7-10. Referral of application and plan to district; time for action. 12-7-11. . Statement of reasons for denial of permit required;
       conditions for approval;
       suspension, revocation, or modification of permit.
12-7-12. . Orders directed to violators; stop work order procedures. 12-7-13. Injunctions. 12-7-14. Actions to restrain imminent danger;
       emergency orders; duration of effectiveness of orders.
12-7-15. Civil penalty. 12-7-16. Hearings and review. 12-7-17. Exemptions. 12-7-18. Effect of chapter on requirements of the “Georgia Water Quality Control Act.” 12-7-19. Education and training requirements;
       required programs; instructor qualifications; expiration of certification.
12-7-20. Creation of Stakeholder Advisory Board; responsibilities; procedures. 12-7-21. (Repealed effective July 1, 2006)
       Appointment of panel to study controls implemented pursuant to chapter;
       procedure and operation of panel.
12-7-22. Electronic Filing and reporting system.
# Georgia Water/Policy/Georgia Conservation Use Act

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 2. Water Policy
    2.3. Georgia Water Law

### Summary of the Act

"This Georgia law provides significant property tax reductions to qualified landowners who conserve environmentally sensitive lands for ten years. Environmentally sensitive areas include habitats with endangered species, wetlands, floodplains, stream corridors, undeveloped barrier islands, steep slopes and wildlife habitat larger than ten acres.
This program can build landowner awareness of and appreciation for conservation needs and incentives, which in turn can lead to a commitment to more permanent land conservation (e.g., a conservation easement in perpetuity). Unfortunately, rules promulgated under this law make it difficult for landowners to have their lands designated and assessed as “environmentally sensitive lands”. The rules should be modified to make it easier for landowners to take advantage of the tax incentives afforded to those who are willing to protect such lands for ten years."

### References

* Appendix G. Laws and regulations affecting wildlife in Georgia
# Georgia Water/Policy/Georgia Game and Fish Code

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 2. Water Policy
    2.3. Georgia Water Law
Game and Fish Code (O.C.G.A. 27-1-1)

### Summary of the Act

"This legislation provides the ownership of, jurisdiction over, and control of all wildlife to be vested in the State of Georgia. The section declares that custody of all wildlife in the State is vested with the Georgia Department of Natural Resources for management and regulation.
The Wildlife Resources Division is the principal State agency vested with statutory authority for the protection, management and conservation of terrestrial wildlife and fresh water wildlife resources, including fish, game, nongame, and endangered species. All licensing of recreational and commercial fish and wildlife activities, excluding shellfish, is performed by the Wildlife Resources Division.
The Coastal Resources Division issues shellfish permits, regulates marine fisheries activities including the opening and closing of the commercial shrimp harvesting season, areas of shrimp harvest, regulates marine species size and creel limits, and enforces the National Shellfish Sanitation Program.
The Commissioner of the Department of Natural Resources has directed that there will be cooperation and coordination between the Divisions of the Department in the administration of their respective responsibilities."

### References

* Appendix G. Laws and regulations affecting wildlife in Georgia
# Georgia Water/Policy/Georgia Erosion and Sedimentation Act/Specific provisions

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
<< Chapter 2. Water Policy | 2.3. Georgia Water Law | Georgia Water/Laws/Erosion and Sedimentation Act
Note: Intent for this page is to add a summary of the specific provisions of each code section. See also: list of code sections.
Specific provisions of the Act, by code section
12-7-1. Short title.
    This chapter shall be known and may be cited as the "Erosion and Sedimentation Act of 1975,
as amended." 12-7-2. Legislative findings; policy of state and intent of chapter. 12-7-3. Definitions. 12-7-4. Adoption of comprehensive ordinances relating to land-disturbing activities;
       delegation of responsibility to planning and zoning commission;
       other local ordinances relating to land development;
       effect of chapter on design professionals.
12-7-5. Adoption of rules and regulations for localities without ordinances. 12-7-6. Best Management Practices;
       minimum requirements for rules, regulations, ordinances, or resolutions.
12-7-7. Permit or notice of intent required for land-disturbing activities;
       approval of application and issuance of permit;
       denial of permit;
       bond requirement.
12-7-7.1. Erosion and sediment control plan prepared; completion; implementation. 12-7-8. Certification of locality as local issuing authority;
       periodic review;
       procedure for revoking certification;
       enforcement actions.
12-7-9. Applications for permits;
       erosion and sediment control plans and data;
       time for issuance or denial.
12-7-10. Referral of application and plan to district; time for action. 12-7-11. . Statement of reasons for denial of permit required;
       conditions for approval;
       suspension, revocation, or modification of permit.
12-7-12. . Orders directed to violators; stop work order procedures. 12-7-13. Injunctions. 12-7-14. Actions to restrain imminent danger;
       emergency orders; duration of effectiveness of orders.
12-7-15. Civil penalty. 12-7-16. Hearings and review. 12-7-17. Exemptions. 12-7-18. Effect of chapter on requirements of the “Georgia Water Quality Control Act.” 12-7-19. Education and training requirements;
       required programs; instructor qualifications; expiration of certification.
12-7-20. Creation of Stakeholder Advisory Board; responsibilities; procedures. 12-7-21. (Repealed effective July 1, 2006)
       Appointment of panel to study controls implemented pursuant to chapter;
       procedure and operation of panel.
12-7-22. Electronic Filing and reporting system.
# Georgia Water/Policy/Georgia Growth Strategies Commission

Linda DiSantis — Economic Development Task Force of Governor Joe Frank Harris’ Growth Strategies Commission.

### References

G7 Governnor's Commission on Planned Growth
G620 Office of Planning and Budget, formerly Governor's Budget Bureau .G7 Growth Strategies Commission
# Georgia Water/Policy/Local Ordinances

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

## Local Ordinances, by Subject
### Stormwater Management

* Model Ordinances for Stormwater Management for Metropolitan North Georgia Water Planning District (Atlanta area).
# Georgia Water/Policy/Georgia Environmental Policy Act

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 2. Water Policy
    2.3. Georgia Water Law

### Summary of the Act

"The Georgia Environmental Policy Act (GEPA) requires that all State agencies and activities prepare an Environmental Impact Report as part of the decision-making process for all activities that may have an impact on the environment. Alternatives to the proposed project or activity must be considered as part of the report.
The Act states that any proposed governmental action which may “significantly adversely affect the quality of the environment”, including the state’s air, water, land, plants, and animals, requires an Environmental Effects Report. As outlined in the Act, an Environmental Effects Report describes the environmental impact and any adverse environmental effects of the action, alternative actions, mitigation measures proposed to avoid or minimize impact, and other effects of the action.
The government agency responsible for the action authors the report and provides it to the director of the Environmental Protection Division (EPD) in the DNR. A notice that the report has been prepared is to be published in the legal organ of each county in which the action is to take place, which may lead to a public hearing regarding the action. The Act requires the director of the EPD to issue guidelines to assist government agencies in the preparation of environmental effects reports."

### References

* Appendix G. Laws and regulations affecting wildlife in Georgia
# Georgia Water/Policy/Issues/Ground Water

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 2. Water Policy
       2.4.3. Ground Water Policy in Georgia

### Policy Issues

* Limit total allowed withdrawal (from all users)
* Manage aquifer recharge
* Consider ground water pumping effects on spring flow

### Example policy from other states

* Idaho -- "It is the policy of Idaho that average withdrawals from an aquifer should not exceed the reasonably anticipated rate of future recharge to that aquifer." (p.3)
* Idaho -- "It is the policy of Idaho that managed recharge be encouraged, pursuant to state law. Comment: Managed aquifer recharge may enhance spring flows and maintain desirable aquifer levels." (p.4)
* Idaho -- "It is the policy of Idaho that the hydrogeologic relationships between ground water supplies and spring flows continue to be quantified to allow for the determination of optimal development of the water resources. Comment: Spring flow is part of the natural discharge from an aquifer. Pumped ground water withdrawals from an aquifer change the original recharge-discharge relationship and affect spring flows. Where this relationship exists, it must be sufficiently quantified to allow for optimal utilization of the ground water supply while protecting established senior rights which depend on spring flows discharging from the aquifer." (p.4)
# GNU C Compiler Internals/Links 3 4

* GCC website
* ^ http://www.gccsummit.org
* ^ http://research.alexeysmirnov.name/gem
| Prev: GCC Hacks | Links | Next: Contributors |
# GNU C Compiler Internals/Introduction
## What is GCC?

GNU Compiler Collection (GCC) is a free software project that includes compilers for Ada, C, C++, Fortran, Java, and Objective-C, as well as libraries for these languages. It is capable of generating executables for a variety of platforms including x86, ARM, MIPS, PowerPC, etc.

## History of GCC

The homepage of GCC is http://gcc.gnu.org. The modern history of GCC begins with the GCC 2.95 release. This version was released on July 31, 1999. GCC 3.0 which is considered modern history for the C++ compiler was released on June 18, 2001. Additional branches were created later on. As of now, the active development branches are GCC 3.4 with a latest release on November 30, 2005, and GCC 4.0 released last time on September 28, 2005. GCC 4.1 was released on Feb 28 2006. GCC 4.2 is the development branch of GCC. The source code repository is available online. GCC 4.2 (the trunk) is the only place where real development happens and new features can go.
GCC has become popular in industry and academia. The availability of its source code allows one to add new features to the compiler. GCC is used in several source-code based security projects, that is, in the tools that instrument the source code of the program to make it more secure. However, very few documents describing the GCC internals have been published so far.
When new functionality is implemented, the source code of GCC is modified directly. However, these compiler extensions are difficult to distribute because GCC is a really big program. A framework for creating modular extensions would greatly simplify the development of compiler extensions.
GCC 4.0 and above includes SSA optimizers and should be used for further high level optimizations and transformations. The RTL level should only be used for target specific optimizations and optimizations which are low level such as scheduling. Any GCC before 4.0 is in some minds an old dated compiler which was showing its age.

## Purpose of this book

The purpose of this book is to address the demands of GCC hackers. We start with a description of GCC 3.4.1 architecture focusing on the source code parser. We chose this version of GCC because we used this version mostly. Then we address the problem of extension development. We present the GCC Extensibility Modules (GEM) project in the next chapter. GEM provides a number of hooks throughout GCC source code. It is implemented as a patch to GCC. A GEM-based compiler extension is developed as a stand-alone program. When the extension is completed, only its source code is distributed compared with distributing the source code of the GCC if GEM is not used. We give examples that demonstrate GEM programming at the end of the book.
| Take home: | What this book is: a guide to GCC internals for extension programmers. GEM framework for developing modular extensions is introduced. What this book is not: a programming language reference, GCC installation manual. |
# GNU C Compiler Internals/Return Address Defense 4 1
## Return Address Defense

A prerequisite to understanding the proposed extension is the following paper:
Tzi-Cker Chiueh, Fu-Hau Hsu,"RAD: A Compile-time Solution to Buffer Overflow Attacks," 21st IEEE International Conference on Distributed Computing Systems (ICDCS), Phoenix, Arizona, USA, April 2001.
http://www.ecsl.cs.sunysb.edu/tr/TR96.pdf
The paper proposed to instrument function prolog and epilog. The return address is saved in a well-protected buffer so that overwriting stack frame does not hurt it. The copy of the address is cross-checked with the one on the stack to detect a possible attack.
Implementing the proposed method has a number of difficulties. Different architectures have different stack frame layout. For example, the x86 prolog has the code to save clobbered registers which is generated in the machine-specific component of GCC. Therefore, instrumenting prolog at the RTL level will not take into account those registers because their number is unknown at that time. There are two approaches to this problem. The first is to instrument prolog at the machine level which is not portable across different architectures. The second approach is to instrument the call-site instead.
The idea of the proposed implementation is to find the approximation of the return address using the address of a code label immediately following the call instruction. It is also possible to find the address on the stack where the return address is written using the number of actual arguments that are pushed on the stack. In case of x86 frame layout, the space is reserved at the frame creation time, therefore the stack pointer not modified when a function is called. The return address approximation and the stack pointer are saved in a well-protected buffer, similarly to the original RAD approach. The following code snippet illustrates the idea:
When the instrumented code is executed, the control flow is directed to a label after the original call instruction. At that point, a call instruction saves the current EIP value and directs the control flow back to label L1. Therefore, the return address approximation argument is already on stack. We also need to push the ESP as the second argument. Function rad_prolog adds the pair to a safe buffer. The arguments are popped and the original function is called. The added call instruction is jumped over upon return.
We also need to instrument function epilog. GIMPLE level works in this case because there is a TRY_FINALLY_EXPR code. The most recent pair of return address and its location in the well-protected buffer are used to validate the return address on the stack. An alarm is generated in case the two values mismatch.
This extension does not use any machine-specific information. Therefore, it is portable across different architectures, even though we were unable to test it under anything except x86.
# GNU C Compiler Internals/Security Hacks 4 1
## Return address protection (RAD)

Rad

## Repair of control-hijacking attacks (DIRA)

Dira

## Array bounds checking using segmentation hardware (CASH)

Cash

## Detecting integer overflows (DIVINE)

Divine

## Dynamic Information Flow Tracking (GDIF)

Gdif
# GNU C Compiler Internals/Links 4 1

* GCC website
* ^ http://www.gccsummit.org
* ^ http://research.alexeysmirnov.name/gem
| Prev: GCC Hacks | Links | Next: Contributors |
# GNU C Compiler Internals/Links

* GCC website
* ^ http://www.gccsummit.org
* ^ http://www.ecsl.cs.sunysb.edu/gem
| Prev: GCC Hacks | Links | Next: Contributors |
# Free Knowledge Culture Calendar/February 14

Today in 1989 the .ZIP file format was released into the public domain. After a lawsuit against Phil Katz as a third party developer of an (improved) implementation of the then predominant ARC format, his better and free ZIP format supplanted ARC and sealed the end of the plaintiff company SEA.
← previous day · following day →
# Free Knowledge Culture Calendar/February 19

On this day in 1971 the first warrant to search computer storage is issued in San Jose, California, for a trade secret theft investigation. It kicked off a new era of digital forensics and led to people protecting local personal data with (“warrant-proof”) encryption. The effectiveness of cryptography against comprehensive state surveillance capabilities is the basis of crypto-anarchism. For others it is a flaw in the desired unrestricted access of investigative authorities and intelligence agencies. As a result, there are regular calls for bans on strong encryption, justified by polemical reference to either terror or child pornography, and bigger waves of criminalization of the use of strong cryptography that have become known as the Crypto Wars. They make defending personal use of strong encryption an ongoing necessity. Even the strongest advocates of freedom of information make an exception for individual privacy, which is another important foundation for the free development of one’s personality.
← previous day · following day →
# Free Knowledge Culture Calendar/February 2

Today in 2003 the ReactOS project made its first release. However, the first version with a working GUI came almost a year later and development is still in alpha stage.
← previous day · following day →
# Free Knowledge Culture Calendar/February 12

Today in 2007 version 1.0 of the Definition of Free Cultural Works was released.
← previous day · following day →
# Free Knowledge Culture Calendar/February 13

Today in 1258 Mongols conquered Baghdad, killing scientists and philosophers and destroying the House of Wisdom and over thirty other public libraries, concluding the Islamic Golden Age and the Translation Movement.
← previous day · following day →
# Free Knowledge Culture Calendar/February 15

Today in 1995 was the high-profile arrest of Kevin Mitnick. After being mistreated by the judiciary following an earlier arrest, he disappeared and was on the run for two and a half years. In a world that had become afraid of hackers, his judge was convinced that he could start a nuclear war from a phone. After years of imprisonment without trial or bail hearing, beatings and months of solitary confinement, he was convicted of computer and wire fraud and received a sentence that was higher than that of many killers.
← previous day · following day →
# Free Knowledge Culture Calendar/February 20

Today in 1991 the first public version of Python (v0.9.0) was released.
← previous day · following day →
# Free Knowledge Culture Calendar/February 16

Today in 1978 the first bulletin board system went online. One by one, people could call the system and read and leave messages, as if using a shared answering machine, harnessing the potential of combining affordable computers and modems. For nearly 20 years, BBSs were the primary way for computer users to get online, share software, join online communities, ...
← previous day · following day →
# Free Knowledge Culture Calendar/February 17

Today in 2012 The Document Foundation was incorporated, a neutral foundation for the development of OpenOffice. Because Oracle resisted the concept, the office suite was forked. Although Oracle showed some effort and made OpenOffice an Apache project, influential Linux distributions and most users switched to LibreOffice.
← previous day · following day →
# Free Knowledge Culture Calendar/February 18

Today in 2000 Geekcorps was incorporated.
← previous day · following day →
# High School Chemistry/Chemistry in the Laboratory

* Making Observations
* Making Measurements
* Using Data
* How Scientists Use Data
← Using Algebra in Chemistry · Making Observations →
This material was adapted from the original CK-12 book that can be found here. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License
# High School Chemistry/Electron Configurations and the Periodic Table

* Electron Configurations of Main Group Elements
* Orbital Configurations
* The Periodic Table and Electron Configurations
← Writing Electron Configurations · Electron Configurations of Main Group Elements →
This material was adapted from the original CK-12 book that can be found here. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License
# High School Chemistry/Electron Configurations for Atoms

* The Electron Spin Quantum Number
* Pauli Exclusion Principle
* Aufbau Principle
* Writing Electron Configurations
← Shapes of Atomic Orbitals · The Electron Spin Quantum Number →
This material was adapted from the original CK-12 book that can be found here. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License
# High School Chemistry/Electrochemistry

* Eytmology of Oxidation
* Oxidation - Reduction
* Balancing Redox Equations
* Electrolysis
* Galvanic Cells
← Gibbs Free Energy · Origin of the Term Oxidation →
This material was adapted from the original CK-12 book that can be found here. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License
# High School Chemistry/Covalent Bonding

* The Covalent Bond
* Atoms that Form Covalent Bonds
* Naming Covalent Compounds
← Inorganic Nomenclature · The Covalent Bond →
This material was adapted from the original CK-12 book that can be found here. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License