similar to: Fw: Would Xiph be interested in a logo redesign for Vorbis?

So, in a thread on HA a user asked if some logo was the official one for Vorbis. It turned out not to be, but everyone agreed the official logo was ugly and a bad idea to add on any portable player compilant with Vorbis (or other Ogg media for that matter). The chaps, me included, started a discussion of a redesign, but truth be told, if Xiph isn't interested in a redesign, there's no

I may be way behind here, but I see that digium redesigned their site. I cannot find the mailing list search screen. I have found the mailman list page, but that doesn't have have a nice search ability. Do I need to just rely on google and other generic search engines or is there a search on the digium site? Thanks! -- -M There are 10 kinds of people in this world: Those who can count in

Ticket 4052 (http://dev.rubyonrails.org/ticket/4052) just came through trac, which introduces the need for a better way to access fixtures. I believe the basic problem is the same as 3935 (http://dev.rubyonrails.org/ticket/3935) in that the accessor method which is constructed by the fixture call can''t infer the class name from the table name. The band-aid in 3935 was to allow you to

Hi, I feel the CSS definitions for the HTML help pages are not visually appealing enough. I admit this is a very subjective matter, so I don't have strong arguments for this wishlist, although I wrote my version of R.css with some web design instructions in mind (e.g. use browser-safe sans-serif fonts). Anyway, here is what I've done:

BCIT Downtown Campus[1] has been chosen, with a maximum capacity of 300 people. With already over 50% of the seats filled, be sure to register soon or you might miss out on one of the most exciting technical events to come to Vancouver. YVR06 will be twice the size of the last conference by Open Source Events[2] held last June, and with 4 times the amount of speakers, during the two days. All for

Hello all: I am in the process of redesigning my site and was thinking about incorporating RoR into the overall structure. However, there are multiple things I would like to create with Rails, namely a gallery, a weblog, and portfolio management system. Given that I am going to be using a lot of RoR, what is the best way to accomplish this task? Here are some random things that have come

Expire plugin / expire-tool seems annoyingly inflexible currently, so I was thinking about a more generic redesign: The expire plugin keeps track of the oldest message in configured mailboxes. Its only configuration is the list of tracked mailboxes. There's no configuration like what the expire timeouts are or anything. There will be a new doveadm command: doveadm expunge [-u user | -A]

In case anyone is interested in reading (and maybe helping!) with a dsync redesign that's intended to fix all of its current problems, here are some possibly incoherent ramblings about it: http://dovecot.org/tmp/dsync-redesign.txt and even if you don't understand that, here's another document disguising as an algorithm class problem :) If anyone has thoughts on how to solve it, would

I was writing this to beta9 announcement, but it grew so huge that I guess a separate mail is better. :) I've spent quite a lot of time this last week redesigning/rewriting Squat indexer. I think the redesign is good enough now that I'll just replace the existing squat with this new one in next release. I don't think many people are using the old squat, and there are also some bugs in

"Finkel, Hal J. via llvm-dev" <llvm-dev at lists.llvm.org> writes: > One concern that I have is that, from personal experience, the ability > for bugpoint to reduce the set of optimization passes applied in order > to reproduce a bug is extremely helpful. I understand your desire to > decouple the logic somewhat, and maybe there's some way to generalize > that

Hi all, This proposes a redesign of LLD’s symbol table in order to improve memory locality by minimizing indirection when resolving relocations. The key idea is that we perform symbol resolution by overwriting SymbolBodies, rather than by updating pointers. This is based on some ideas mentioned by Rafael on IRC. Conceptually, we split Symbol into a non-polymorphic part and a polymorphic part (a

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less

First off, let me say thanks to Mr. Eastep for such a solid and easy to use package. Seawall was the only ipchains ''package'' firewall I ever considered using, and Shorewall has been my first venture into the world of iptables. The deployment I have just completed (and now need to redo due to client requirement changes) was 100% straightforward and has been working flawlessly for

The biggest problem with Vorbis comments are too loose specifications and too little standardisation. Another problem is attribution of involved parties. Currently only the ARTIST field name is supported in software. More standardised field names need to be worked out for organisations and persons involved in the production of the recording. See:

This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox

On 6/11/19 12:25 PM, Philip Reames via llvm-dev wrote: At the moment, bugpoint has three major use cases: crash reduction, miscompile reduction, and mutation fuzzing. Out of these, a huge proportion of the interface complexity comes from the miscompile handling. I generally agree with removing the auto-detection logic. I've found it to be extraordinarily error prone and confusing.

Hi all, The bitset metadata currently used in LLVM has a few problems: 1. It has the wrong name. The name "bitset" refers to an implementation detail of one use of the metadata (i.e. its original use case, CFI). This makes it harder to understand, as the name makes no sense in the context of virtual call optimization. 2. It is represented using a global named metadata node, rather than

Hi, Just to let you know about the new Xiph QuickTime Components project. It should be of interest to people wanting to use ogg/vorbis files (and other Xiph formats, as well) in combination with QuickTime-based applications (e.g. see: iTunes). The project pages are at: http://www.xiph.org/quicktime/ The first OS-X(ppc) binary builds are out, as well. Regards, Arek

On 14 Sep 2007 at 15:52, Ian Malone wrote: > Vorbis comments could do better than they currently do > but no-one seems compelled to implement any of the exotic > tag proposals that have hung around for years. Exotic tag proposals?! Do you mean the ones linked from the wiki? As far can tell, the only roadblock to "implementation" (by which, I assume you mean support from

Hey all, I wanted to share a proposal <https://docs.google.com/document/d/171ecPTeXw68fbCghdGw_NPBouWvmvUX8vePlbhhHEdA/edit?usp=sharing> to revamp the current go-to IR debugging tool: Bugpoint. i'd love to hear any feedback or general thoughts. Here's the markdown version of the doc: --- # Bugpoint Redesign Author: Diego Treviño (diegotf at google.com) Date: 2016-06-05 Status: