You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2024. It is now read-only.
Thanks you for your interest in contributing to Microsoft Caboodle! In this document we'll outline what you need to know about contributing and how to get started.
3
+
Thanks you for your interest in contributing to Xamarin.Essentials! In this document we'll outline what you need to know about contributing and how to get started.
4
4
5
5
## Code of Conduct
6
6
@@ -12,7 +12,7 @@ You will need to complete a Contribution License Agreement before any pull reque
12
12
13
13
## Contributing Code
14
14
15
-
Check out [A Beginner's Guide for Contributing to Microsoft Caboodle](https://github.com/xamarin/Caboodle/wiki/A-Beginner's-Guide-for-Contributing-to-Microsoft-Caboodle).
15
+
Check out [A Beginner's Guide for Contributing to Xamarin.Essentials](https://github.com/xamarin/Xamarin.Essentials/wiki/A-Beginner's-Guide-for-Contributing-to-Xamarin.Essentials).
16
16
17
17
## Documentation - mdoc
18
18
@@ -25,48 +25,48 @@ Every pull request which affects public types or members should include correspo
25
25
26
26
### Bug Fixes
27
27
28
-
If you're looking for something to fix, please browse [open issues](https://github.com/xamarin/Caboodle/issues).
28
+
If you're looking for something to fix, please browse [open issues](https://github.com/xamarin/Xamarin.Essentials/issues).
29
29
30
30
Follow the style used by the [.NET Foundation](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/coding-style.md), with two primary exceptions:
31
31
32
32
- We do not use the `private` keyword as it is the default accessibility level in C#.
33
33
- We will **not** use `_` or `s_` as a prefix for internal or private field names
34
34
- We will use `camelCaseFieldName` for naming internal or private fields in both instance and static implementations
35
35
36
-
Read and follow our [Pull Request template](https://github.com/xamarin/Caboodle/blob/master/PULL_REQUEST_TEMPLATE.md)
36
+
Read and follow our [Pull Request template](https://github.com/xamarin/Xamarin.Essentials/blob/master/PULL_REQUEST_TEMPLATE.md)
37
37
38
38
### Proposals
39
39
40
-
To propose a change or new feature, review the guidance below and then [open an issue using this template](https://github.com/xamarin/Caboodle/issues/new).
40
+
To propose a change or new feature, review the guidance below and then [open an issue using this template](https://github.com/xamarin/Xamarin.Essentials/issues/new).
41
41
42
42
#### Non-Starter Topics
43
43
The following topics should generally not be proposed for discussion as they are non-starters:
44
44
45
45
* Large renames of APIs
46
46
* Large non-backward-compatible breaking changes
47
-
* Platform-Specifics which can be accomplished without changing Microsoft Caboodle
47
+
* Platform-Specifics which can be accomplished without changing Xamarin.Essentials
48
48
* Avoid clutter posts like "+1" which do not serve to further the conversation
49
49
50
50
#### Proposal States
51
51
##### Open
52
52
Open proposals are still under discussion. Please leave your concrete, constructive feedback on this proposal. +1s and other clutter posts which do not add to the discussion will be removed.
53
53
54
54
##### Accepted
55
-
Accepted proposals are proposals that both the community and core Microsoft Caboodle agree should be a part of Microsoft Caboodle. These proposals are ready for implementation, but do not yet have a developer actively working on them. These proposals are available for anyone to work on, both community and the core Microsoft Caboodle team.
55
+
Accepted proposals are proposals that both the community and core Xamarin.Essentials agree should be a part of Xamarin.Essentials. These proposals are ready for implementation, but do not yet have a developer actively working on them. These proposals are available for anyone to work on, both community and the core Xamarin.Essentials team.
56
56
57
57
If you wish to start working on an accepted proposal, please reply to the thread so we can mark you as the implementor and change the title to In Progress. This helps to avoid multiple people working on the same thing. If you decide to work on this proposal publicly, feel free to post a link to the branch as well for folks to follow along.
58
58
59
59
###### What "Accepted" does mean
60
60
* Any community member is welcome to work on the idea.
61
-
* The core Microsoft Caboodle team _may_ consider working on this idea on their own, but has not done so until it is marked "In Progress" with a team member assigned as the implementor.
61
+
* The core Xamarin.Essentials team _may_ consider working on this idea on their own, but has not done so until it is marked "In Progress" with a team member assigned as the implementor.
62
62
* Any pull request implementing the proposal will be welcomed with an API and code review.
63
63
64
64
###### What "Accepted" does not mean
65
-
* The proposal will ever be implemented, either by a community member or by the core Microsoft Caboodle team.
66
-
* The core Microsoft Caboodle team is committing to implementing a proposal, even if nobody else does. Accepted proposals simply mean that the core Microsoft Caboodle team and the community agree that this proposal should be a part of Microsoft Caboodle.
65
+
* The proposal will ever be implemented, either by a community member or by the core Xamarin.Essentials team.
66
+
* The core Xamarin.Essentials team is committing to implementing a proposal, even if nobody else does. Accepted proposals simply mean that the core Xamarin.Essentials team and the community agree that this proposal should be a part of Xamarin.Essentials.
67
67
68
68
##### In Progress
69
-
Once a developer has begun work on a proposal, either from the core Microsoft Caboodle team or a community member, the proposal is marked as in progress with the implementors name and (possibly) a link to a development branch to follow along with progress.
69
+
Once a developer has begun work on a proposal, either from the core Xamarin.Essentials team or a community member, the proposal is marked as in progress with the implementors name and (possibly) a link to a development branch to follow along with progress.
70
70
71
71
#### Rejected
72
-
Rejected proposals will not be implemented or merged into Microsoft Caboodle. Once a proposal is rejected, the thread will be closed and the conversation is considered completed, pending considerable new information or changes.
72
+
Rejected proposals will not be implemented or merged into Xamarin.Essentials. Once a proposal is rejected, the thread will be closed and the conversation is considered completed, pending considerable new information or changes.
0 commit comments