On 07/29/2011 03:49 PM, Jonathan "Duke" Leto wrote: >> Parrot itself would also benefit from being more user-centric. > > Would you care to expand upon this? Do you have specific examples of things > that can be improved ?
1) the recent discussion about README changes shows how controversial simple changes are from which users benefit, and which don't really make life harder for developers 2) Recently I wanted to add some search paths 'load_library' to rakudo, from PIR or NQP. So I went to http://docs.parrot.org/parrot/latest/html/ and read the list of documents there... and didn't even know where I should start reading. None of these documents seemed to even come close to describing what I wanted to do. Asking in #parrot, I got a pointer to IGLOBALS_LIB_PATHS, and the whole documentation I could find was include/parrot/interpreter.h 280: IGLOBALS_LIB_PATHS, /* LoL of search paths and dynamic ext */ Try to call that user-centric... 3) http://parrot.org/dev/docs/user doesn't mention the bug tracker at all, only http://parrot.org/dev does. So do you only expect developers to submit bug reports? 4) ok, suppose I want to submit a ticket, and find the link "Parrot Issue Tracker" on the developer's page. I click on it, and it greets me with "Welcome to the Parrot Developer Wiki" -- wait, not quite what I wanted. Neither does that page contain any information about how to submit a ticket. I'm sure you now got an idea what I'm talking about, and can find other examples along these lines. Cheers, Moritz _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
