Comments (7)
Why not just download the code via git? composer.josn and phpunit.xml.dist are only removed if a git export is done. If you are using composer to get the code you can pass the --prefer-source flag.
from datavalues.
I am interested in packaging DataValues for Debian (as a prerequisite for Wikibase), and having stable HTTP(S) URIs for testable release archives would be very helpful, although I can in principle get around with git. However, release archives contain test files, but not the metadata required to execute the tests offline – why not include it?
from datavalues.
That is rather weird yes. Just the case for the latest releases though, on master the test directory is also excluded since 9b54bf3
My first reaction to exclusion of tests is that it removes potentially useful info, since tests have a documenting function. And while I still think that, there are a number of Wikiemdia people that want these things excluded. If it was just them... but many open source projects are doing the same, so there presumably is some kind of non-Wikimedia motivation as well?
So I'm undecided on what to do with this
from datavalues.
Btw I will make a new release tomorrow so this is consistent
from datavalues.
For what it's worth, the motivation for excluding certain files via .gitattibutes, when that originally happened was Wikimedia one. Namely, it was a means to not include not needed files in Wikimedia's Mediawiki Vendor component.
That said, exclude files from the git export is not the only way to achieve e.g. not included not wanted files, tests etc from the said component, e.g. for libraries beyond Wikimedia's control, git-ignoring in the component itself has been used, see https://github.com/wikimedia/mediawiki-vendor/blob/3ff8ee3dd4ac225dce030b400b3ad0f75bb5ed7e/.gitignore#L39.
I'd personally say that ignoring in this "MW vendor" thing is a better approach, as the library author should define themselves what they are willing to export.
Whether the above information should determine any changes to the DataValues libraries, I have no opinion.
from datavalues.
Coming from outside the MW, for me it is a bit difficult to understand the reasons for exclusion of this data from releases. It's always easier to delete unneeded data than to find the ways to get it. But for sure things should be done in convenience for primary users.
Thanks a lot for including these files in the release!
from datavalues.
We still need to release that as 2.3 though...
from datavalues.
Related Issues (3)
- 3.0.0 release HOT 6
- Fix PHP 8.1 deprecation warnings HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from datavalues.