diff options
| -rw-r--r-- | doc/developers.bb | 4 | ||||
| -rw-r--r-- | doc/features.bb | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/developers.bb b/doc/developers.bb index ec816db7c..bec9914c8 100644 --- a/doc/developers.bb +++ b/doc/developers.bb @@ -1,4 +1,4 @@ -[b]Red Developer Guide[/b]
+[b]$Projectname Developer Guide[/b]
We're pretty relaxed when it comes to developers. We don't have a lot of rules. Some of us are over-worked and if you want to help we're happy to let you help. That said, attention to a few guidelines will make the process smoother and make it easier to work together. We have developers from across the globe with different abilities and different cultural backgrounds and different levels of patience. Our primary rule is to respect others. Sometimes this is hard and sometimes we have very different opinions of how things should work, but if everybody makes an effort, we'll get along just fine.
@@ -39,7 +39,7 @@ All code contributed to the project falls under the MIT license, unless otherwis Code changes which fix an obvious bug are pretty straight-forward. For instance if you click "Save" and the thing you're trying to save isn't saved, it's fairly obvious what the intended behaviour should be. Often when developing feature requests, it may affect large numbers of community members and it's possible that other members of the community won't agree with the need for the feature, or with your proposed implementation. They may not see something as a bug or a desirable feature.
-We encourage concensus building within the community when it comes to any feature which might be considered controversial or where there isn't unanimous decision that the proposed feature is the correct way to accomplish the task. The first place to pitch your ideas is to [url=https://zothub.com/channel/one]Channel One[/url]. Others may have some input or be able to point out facets of your concept which might be problematic in our environment. But also, you may encounter opposition to your plan. This doesn't mean you should stop and/or ignore the feature. Listen to the concerns of others and try and work through any implementation issues.
+We encourage consensus building within the community when it comes to any feature which might be considered controversial or where there isn't unanimous decision that the proposed feature is the correct way to accomplish the task. The first place to pitch your ideas is to [url=https://zothub.com/channel/one]Channel One[/url]. Others may have some input or be able to point out facets of your concept which might be problematic in our environment. But also, you may encounter opposition to your plan. This doesn't mean you should stop and/or ignore the feature. Listen to the concerns of others and try and work through any implementation issues.
There are places where opposition cannot be resolved. In these cases, please consider making your feature [b]optional[/b] or non-default behaviour that must be specifically enabled. This technique can often be used when a feature has significant but less than unanimous support. Those who desire the feature can turn it on and those who don't want it - will leave it turned off.
diff --git a/doc/features.bb b/doc/features.bb index 8d51d9853..e8d1cd687 100644 --- a/doc/features.bb +++ b/doc/features.bb @@ -191,8 +191,8 @@ Similar to any other modern blogging system, social network, or a micro-blogging [b]Previewing/Editing[/b]
Post can be previewed prior to sending and edited after sending.
-[b]Voting/Concensus[/b]
-Posts can be turned into "concensus" items which allows readers to offer feedback, which is collated into "agree", "disagree", and "abstain" counters. This lets you gauge interest for ideas and create informal surveys.
+[b]Voting/Consensus[/b]
+Posts can be turned into "consensus" items which allows readers to offer feedback, which is collated into "agree", "disagree", and "abstain" counters. This lets you gauge interest for ideas and create informal surveys.
[b]Extending $Projectname[/b]
|