The repository structure should look like this:
#Standard notes github full#
LICENSE file that includes the full license text and copyright notice for the
#Standard notes github code#
The subdirectory for third-party code vendor instead of 'third_party'.Įvery directory inside third_party (or 'vendor', etc.) needs to have a Projects may also use different layouts or naming conventions, such as calling In the upstream repository can continue to live in its original location. Own the copyright to or that Google has not received under Google's ContributorĪ third_party directory at the root of theįor any repositories forked from third-party open source projects, code present Making third-party code easy to find helps us andĭownstream users comply with license requirements.įor any first-party Google open source projects, any code that Google does not Google-managed source repositories use top-level /third_party subdirectories to The OSPO team's review we will flag any issues we come across, but our primaryįocus is on licensing and legal issues. They're fit for public viewing and ensure the code has no security implicationsįor Google that haven't been reviewed by the security team. Please be very careful when releasing code - read all the comments to ensure If you think you need a license other than Apache 2, to confirm this for you. the main audience for your release is a community which has standardized.
Don't name the project after anyone else's trademarks, no matter howįor repository names, avoid just concatenating words and instead separating themĭO: successor-to-serverless License your projectĭefault (it provides us the best legal protections while giving others wideįreedom) and you must use it unless there is a specific reason not to, such as:."Test Libraries for Java" rather than "Java Test
Don't use third-party brands except when necessary use them only asĭescriptors (e.g.Google, Android, YouTube) in the name unless Provide a second-choice name in case the first-choice can't be approved.Use a descriptive name that makes it clear what your project does.Project to receive significant media attention).įollow these guidelines specific to open source projects: Release of the project is being accompanied by a press release or you expect the Follow go/naming if you're naming a high-profile project (e.g., the We recommend a descriptive, clear name that's indicative of what the Naming your project (and associated repository) is an important part of If you're in one of those orgs, you should start by following that process.Īfter satisfying any specific prerequisites, you will end up back at NOTE: Some groups have slightly different processes for work-related releases. We want toĪpprove your request! Before requesting approval to release code, you'll need to The Open Source Programs Office, it's our job to help you do that. Google believes in open source and wants to contribute back to the community. You'll need to pick the version listed here.As open source.
#Standard notes github install#
You can install the NDK inside of Android Studio. We use native code from the Libsodium encryption library to achieve high performance.
0 kommentar(er)
