operations-mediawiki-config
operations-puppet
Our great sponsors
- Appwrite - The Open Source Firebase alternative introduces iOS support
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
- SonarQube - Static code analysis for 29 languages.
| operations-mediawiki-config | operations-puppet | |
|---|---|---|
| 1 | 1 | |
| 76 | 239 | |
| - | 0.0% | |
| 9.8 | 10.0 | |
| 2 days ago | 5 days ago | |
| HTML | Puppet | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
operations-mediawiki-config
-
The falsehoods of anti-AGPL propaganda (2020)
> Configuration is just a short artifact. It's not a creative work and is therefore not copyrightable at all, whether by AGPL or otherwise.
I'm doubtful. For example https://github.com/wikimedia/operations-mediawiki-config is wikipedia's config. It is not short, and much of it is complex enough i think it would be copyrightable (ianal)
I agree though a very traditional list of key value pairs that are simple facts like where to find the db, might lack creativity to be copyrighted (ianal). But how many real deployed systems have that simple a config. More generally i would prefer that the license was less ambigious about this especially in an international context (e.g. rules are totally different in uk over what can be copyrighted)
> I'm not convinced obscurity helps against spam at all. DKIM and blocklists have done much more against email spam than any form of "security by obscurity" corporate scheme has.
Gmail et al use techniques beyond dkim that are secret. However i meant more like web spam where you can't just rely on source vouching for users. For example on wikipedia there is a feature where admins can write "code" that block patterns in edits. When used against persistent vandals, they are often secret lest they use the info to adjust behaviour. That's the type of thing i mean.
> if you are coordinating with the developers, then you have their explicit permission to temporarily withhold those changes (AGPL copyright holders can still grant exceptions to the license)
That only works if one entity holds all the copyright. Even then, does that mean forks cannot have coordinated disclosure?
operations-puppet
We haven't tracked posts mentioning operations-puppet yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
kiwix-js-windows - Kiwix JS Offline Browser for Windows and Linux, packaged as PWA, Electron, NWJS and UWP
govuk-puppet - Puppet manifests used to provision remaining parts of the legacy GOV.UK stack (as at Mar 2023: crawler, data sync/backup, Licensify, CKAN)
Spell4Wiki - Spell4Wiki is a mobile application to record and upload audio for Wiktionary words to Wikimedia Commons. Spell4Wiki also a multilingual Wiki-Dictionary.
Mediawiki - 🌻 The collaborative editing software that runs Wikipedia. Mirror from https://gerrit.wikimedia.org/g/mediawiki/core. See https://mediawiki.org/wiki/Developer_access for contributing.
archwiki - MediaWiki used on Arch Linux websites