@@ -110,7 +110,7 @@ QGIS classes that are generated from Qt Designer (ui) files should have a
110
110
//Base// suffix. This identifies the class as a generated base class.
111
111
```
112
112
Examples:
113
- QgsPluginMangerBase
113
+ QgsPluginManagerBase
114
114
QgsUserOptionsBase
115
115
```
116
116
=== Dialogs ===
@@ -276,10 +276,11 @@ once, consider consolidating the code into a single function.
276
276
```
277
277
278
278
This will:
279
- * allow changes to be made in one location instead of in multiple places
280
- * help prevent code bloat
281
- * make it more difficult for multiple copies to evolve differences over time,
282
- thus making it harder to understand and maintain for others
279
+ - allow changes to be made in one location instead of in multiple places
280
+ - help prevent code bloat
281
+ - make it more difficult for multiple copies to evolve differences over time,
282
+ thus making it harder to understand and maintain for others
283
+ -
283
284
284
285
=== Prefer Having Constants First in Predicates ===
285
286
@@ -558,7 +559,7 @@ a ticket in trac (https://trac.osgeo.org/qgis/) first and then attach you
558
559
This makes it easier for us to apply the patches since we don't need to
559
560
navigate to a specific place in the source tree to apply the patch. Also when I
560
561
receive patches I usually evaluate them using kompare, and having the patch
561
- from the top level dir makes this much easier. Below is an example of you you
562
+ from the top level dir makes this much easier. Below is an example of how you
562
563
can include multiple changed files into your patch from the top level
563
564
directory:
564
565
@@ -583,10 +584,10 @@ svn diff > bug7887fix.diff
583
584
584
585
QGIS developers are busy folk. We do scan the incoming patches on bug reports
585
586
but sometimes we miss things. Don't be offended or alarmed. Try to identify a
586
- developer to help you - using the [" Project Organigram" ] and contact them
587
+ developer to help you - using the [Project Organigram http://www.qgis.org/wiki/Project_Organigram ] and contact them
587
588
asking them if they can look at your patch. If you don't get any response, you
588
589
can escalate your query to one of the Project Steering Committee members
589
- (contact details also available on the [" Project Organigram"] ).
590
+ (contact details also available on the Project Organigram).
590
591
591
592
=== Due Diligence ===
592
593
@@ -601,13 +602,13 @@ under the GPL.
601
602
602
603
Write access to QGIS source tree is by invitation. Typically when a person
603
604
submits several (there is no fixed number here) substantial patches that
604
- demonstrate basic competance and understanding of C++ and QGIS coding
605
+ demonstrate basic competence and understanding of C++ and QGIS coding
605
606
conventions, one of the PSC members or other existing developers can nominate
606
607
that person to the PSC for granting of write access. The nominator should give
607
608
a basic promotional paragraph of why they think that person should gain write
608
609
access. In some cases we will grant write access to non C++ developers e.g. for
609
610
translators and documentors. In these cases, the person should still have
610
- demonstrated ability to submit patches and should ideally have submtted several
611
+ demonstrated ability to submit patches and should ideally have submitted several
611
612
substantial patches that demonstrate their understanding of modifying the code
612
613
base without breaking things, etc.
613
614
0 commit comments