See Title.
I can't find anything like that =/
The only possible way i see, is to parse it from the websites via php but I assume that this is not a good solution.
All TYPO3 CMS changes as RSS Feed: https://github.com/TYPO3/TYPO3.CMS/commits/master.atom
Each released version also has release notes, which are located in the wiki: http://wiki.typo3.org/Category:ReleaseNotes/TYPO3_7.x
The releases notes contain some additional information next to the list of changes (like warnings fpr breaking changes, tips how to upgrade things safely etc)
Magento moved to GitHub recently, so you have a Feed of all changes as well: https://github.com/magento/magento2/commits/develop.atom
Related
In this video (https://www.youtube.com/watch?v=qPHKWsZK2Jc&list=PLvv0ScY6vfd-p1gSnbQhY7vMe2rng0IL0&index=10) from about a year ago, there is example code on the SDL_CreateWindow function documentation page. I have seen other posts talking about the SDL examples.
If you look at the documentation now it is the same minus the example code
https://wiki.libsdl.org/SDL2/SDL_CreateWindow
Am I blind or is there no longer any example code on the SDL2 wiki?
If not, does anybody know what the reasons for removing it are?
I expect that
There are some official examples somewhere
If they were removed from the official wiki they would at least be placed in a 'legacy' repo or something like that.
A Google (DuckDuckGo) search gives only third party examples and, aside from a few forum posts, no mention of there ever being any examples on the wiki.
In 2022, the Wiki migrated from MoinMoin to ghwikipp. With that came a host of breaks and bugs. Your issue specifically is covered under issue #233.
The images were also broken, but that issue shows a workaround for viewing the Wiki in working form: use archive.org on wiki.libsdl.org, not wiki.libsdl.org/SDL2 where it is currently hosted. This gives you your examples back.
e.g. like this
If you have some sort of MediaWiki viewer program, you can also just pull an old revision from the Repo and read it offline. Even Github's MarkDown viewer isn't terrible. Caveat that new changes won't be reflected.
They promise us that it will be fixed at some point, and they do seem to be working hard on it. The only hardfix is either to (a) wait, or (b) help them finish their migration.
I am currently trying to analyse Bugzilla in order to find the ratio of number of bugs : lines of code for each Firefox component. However, I have never worked with Bugzilla before and have no knowledge of Firefox's codebase.
How would I go about finding lines of code per Firefox component (as they appear on Bugzilla under Comp header)? I have made an attempt at looking through mozilla central, but have no idea which source files relate to which components.
EDIT: Dexter pointed out that there is a directive BUG_COMPONENT in the mozilla-central tree, but this directive seems extremely incomplete and is not helpful. Any other advice, or pointers as to where I could get such advice would be much appreciated.
Great question! We recently added the BUG_COMPONENT directive (see the meta bug) to the Firefox code: it's in the moz.build file contained in each directory in the source. This directive allows linking each file in the repository to the related Bugzilla component.
For example, the following directive found here, tells that all the files in test/browser containing the Telemetry word belong to the Toolkit::Telemetry component on Bugzilla.
with Files("test/browser/*Telemetry*"):
BUG_COMPONENT = ("Toolkit", "Telemetry")
You can use either DXR or searchfox to quickly search the Firefox repository.
Updated the answer to account for the questions in the comments.
As noted in the comments, some components are tracked on Bugzilla (e.g. Activity Stream) but do not have a direct mapping to source files within the mozilla-central repository (the one Firefox is built from). That's because some newer components do not ride "the trains" (~6 weeks development cycle), but are rather updated more frequently and deployed as addons.
The code for these components usually lives under the Mozilla github account, along with other project. Since there are quite a number of projects, one way to identify the ones you might be interested in is to restrict them to JavaScript ones. If you follow this last link, you'll see the repository for both the test-pilot and Activity Stream (plus other addons).
I'm afraid the only way to match GitHub projects to Bugzilla components is to look at the name of the repository on GitHub and find the matching component in Bugzilla: you can type the name here to get some component suggestions. If you want to get fancy, you might also leverage the Bugzilla REST API:
Get a list of the JS GitHub project.
Extract the name of the project.
Use the REST API to get the component suggestion.
I would personally just consider the mozilla-central repository as a starting point, as it is mostly annotated: scrape the BUG_COMPONENT from the source files, map them to the paths then use the REST API to get the list of bugs.
Sidenote: the Download Panel seems to be correctly annotated in the main repo.
I am currently working on a Jekyll blog on Linux. However I'd like to add contributors to this blog who are using Windows and who haven't any skills in programming or using tools like Git etc.
I was wondering what could be the best process/pratice to enable them to post on the blog?
Installing them the entire environment and writing a script maybe?
Could it cause any issues due to the OS?
Any suggestions or advices are welcome :)
I don't think installing git, and pushing content to your repo is hard task for any non-tech guy.
1: Little tough way
Use team viewer and help your partner to setup git.
Allowed access to your repository.
Teach them, about frontmatter, and some jekyll commands.
2: Simple and smooth way.
Just get doc files dirctly from partner, which contain only content, nothing else, and convert yourself into markdown with manual frontmatter.
3: Create your own dashboard.
You can create your own dashoard like WordPress, where your partner can add categories, tags, title, meta description etc things, that can convert into frontmatter automatically. For that, you need to build yourself. (I find out that kind of generator here, but look's like he deleted, you can find it, by visiting him, old deleted commits).
I had the same problem so I ended up using Wordpress as the interface to it and creating a plugin to marry the systems up.
I figured I'd share it so feel free to have a look:
https://wordpress.org/plugins/wp2jekyll/
I've succesfully generated a docset with AppleDoc by following the installation instructions. If i got into XCode Documentation Organiser, everything is there, including the categories:
But when I ⌥-click on one of my category methods I see nothing but this:
I've tried a lot of things but none of these work:
Adding --no-merge-categories
Adding --merge-categories
Changing filename extensions
Restart XCode
Restart macbook
Search google (AppleDoc quickhelp categories)
Search stackoverflow
Search gitHub repository issue list (https://github.com/tomaz/appledoc)
Please help, because I want to generate documentation, and most of my library consists of categories. I'm using the latest AppleDoc (appledoc 2.1 (build 858)), and Xcode 4.6.3.
Edit: are there users actually using AppleDoc? Does the quick help actually work for you? I also note a lack of documentation even though the repository is updated regularly.
It seems nobody else is using appledoc but me. Anyway, it looks like it is a bug in XCode, i have pushed a workaround in github. Comment if you want details.
Update: my pull request has been accepted, check here for details:
Pull request https://github.com/tomaz/appledoc/pull/375
related issue: https://github.com/tomaz/appledoc/issues/374
I wrote gem and published it to github (ex - https://github.com/randx/six)
I added LICENSE file.
I often see VERSION file in other repo - whats the goal?
Any other files should I add?
Chapter 8 of "Ruby Best Practices" by Greg Brown exclusively deals with properly maintaining Ruby projects, including directory layout, files you should include etc. The book is legally available online here:
http://majesticseacreature.com/rbp-book/pdfs/rbp_1-0.pdf
I always love a good README. It's much easier to read a well explained README than browse the automatically generated RDoc manual. The README should explain what the gem does and how to use it, with example code and even some advanced examples can be included towards the end of the README.
Another essential file is a history or CHANGES file. This file should contain an explanation of the major changes between releases. It does not need to include nitty gritty details, but should include enough information so that someone upgrading from version x to version y can quickly see what's new (so you can asses the benefits of upgrading) and what has changed (so you can asses the potential impacts an upgrade has on your current code).
Too many times I see projects where the CHANGES file is missing, and you're left pretty much in the dark about what has changed when you run an upgrade.
From my perspective each GitHub project (based on your question you have a repo there) should have:
Integration with CI servers (Travis CI, Circle CI, etc)
.github folder with issue/pull requests templates (example https://github.com/zold-io/zold/tree/master/.github)
.gitingore to avoid accidentally committed temporal/local files
.gitattributes for custom Git repo configuration (more https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes and https://git-scm.com/docs/gitattributes)
.rubycop.yml
Add the following badges to your readme.md
version of your ruby gem
license details
commit activity per year to hightlight the status of the project
More about HoC here https://www.yegor256.com/2014/11/14/hits-of-code.html
the status of the latest builds
the status of dependencies (obsolte or not)
show the vulnurabilities count(if any) for the dependencies
as code quality badges
Projects from the examples above:
https://github.com/dgroup/docker-unittests (java)
https://github.com/mattbrictson/gem (ruby)