-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate ebml specs from sourceforge to github pages #4
Comments
I've set up the pages, but I'm currently not an admin for the EBML project on sourceforge. I've pinged Steve Lhomme about it. |
@mbunkus you should be admin there. Let me know if it doesn't work. |
@robUx4 Everything's fine, thanks. The pages have been replaced with redirections. |
Thanks. I see in the sourceforge version (https://web.archive.org/web/20140630212630/http://ebml.sourceforge.net/specs/) the signature elements were all in blue text whereas the other elements were described in black text. In the github pages version they are all the same color. Did the color differentiation in the sourceforge version have any meaning? |
In the Matroska specs, that means "not used". You can see in there that the Signature elements don't belong to any version at all. They were defined but never used. |
What @robUx4 said. The signature elements in EBML should die as soon as possible. Or turned into something that actually works and is secure. But until then they should be removed. |
I propose moving the EBML specs from http://ebml.sourceforge.net to a 'github pages' in the libebml repo (potentially to be at http://matroska-org.github.io/libebml). The EBML homepage has various issues (broken links, typos) and it would be easier to fix these issues if we could send pull requests through github and have the change process documented.
I suggest moving the pages from http://ebml.sourceforge.net to github pages as-is and adding a notice to the sourceforge pages to say that they have moved to the new repo.
The text was updated successfully, but these errors were encountered: