![]() ![]() Discarded as being too immature, in particular due to the number of very immature plugins with no support.Discarded as it is heavily tied to MDN at this time.MDN's Yari tool, used to create the MDN Documentation.clear landing page to allow relevant information to be found quicklyĭifferent options were assessed, including the option to introduce new features and changes to the existing Wikimedia-based documentation, and migrating to a new documentation system.Īs part of the process the working group assessed several other solutions, including:.the ability to link issues to Moodle tracker issues and hold new features from being integrated until appropriate documentation exists for them.the ability to easily remove legacy content.the ability to link content to specific versions of Moodle.the ease of editing when most developers are used to GitHub Formatted Markdown (GFM)Īs part of an internal process, several sessions were held to identify the key features required to improve the Moodle developer documentation, these included:.searchability - the quality of the search tools.discoverability - finding relevant information using the interface and.the ease with which information can be found, including both:.large quantities of stale or irrelevant information, including:.Documentation can be updated after logging in with standard credentials for .Īnecdotal feedback from a range of sources, including in-person discussions, forum posts, and online discussions suggests that there are a number of limitations with the current approach, including: The current developer documentation has over 2,000 pages, and is written and updated using the MediaWiki platform. If (-not (Get-Command choco.The Moodle Developer documentation has been a key resource for all Moodle developers for over fifteen years. zip to the filename to handle archive cmdlet limitations # Ensure Chocolatey is installed from your internal repository # $Chocolate圜entralManagementServiceSalt = "servicesalt" # $Chocolate圜entralManagementClientSalt = "clientsalt" # $Chocolate圜entralManagementUrl = " # ii. # If using CCM to manage Chocolatey, add the following: $ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.1.4.0.nupkg" # This url should result in an immediate download when you navigate to it # ("password" | ConvertTo-SecureString -AsPlainText -Force) # If required, add the repository access credential here $NugetRepositoryUrl = "INTERNAL REPO URL" # Should be similar to what you see when you browse Your internal repository url (the main one). # We use this variable for future REST calls. ::SecurityProtocol = ::SecurityProtocol -bor 3072 # installed (.NET 4.5 is an in-place upgrade). NET 4.0, even though they are addressable if. # Use integers because the enumeration value for TLS 1.2 won't exist # Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories. # We initialize a few things that are needed by this script - there are no other requirements. ![]() ![]() # You need to have downloaded the Chocolatey package as well. Download Chocolatey Package and Put on Internal Repository # # repositories and types from one server installation. # are repository servers and will give you the ability to manage multiple # Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they # generally really quick to set up and there are quite a few options. # You'll need an internal/private cloud repository you can use. Internal/Private Cloud Repository Set Up # # Here are the requirements necessary to ensure this is successful. Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed. Human moderators who give final review and sign off.Security, consistency, and quality checking.ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. ![]()
0 Comments
Leave a Reply. |