Whoops. This was meant to go to list, not just Andy.
---------- Forwarded message ---------- From: Will Coleda <[EMAIL PROTECTED]> Date: Jan 9, 2008 11:00 PM Subject: Documentation Status: Was Re: Build status wiki page To: Andy Dougherty <[EMAIL PROTECTED]> On Jan 8, 2008 10:32 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote: > On Sat, 5 Jan 2008, Andy Lester wrote: > > > > Can you mention what platform tests were failing on? t/shootout isn't > > > failing anymore on any platform I have access to. It's very slow, but not > > > failing. > > > > No, I didn't mean that I would maintain it. I just started a place for > > people > > to keep notes on, just to get inertia going. > > > > > Another really good way to deal with this is to always keep all tests > > > passing in trunk. > > Yes, though there is the danger that TODO'd tests quickly become > forgotten tests. > > > Clearly. However, since there's been so much lately where that hasn't been > > the case, I figured it made sense to make a central location for reporting > > and/or tracking what's failing, without having to resort to RT tickets. > > Would it be easier to just keep a simple file listing "Known Problems" > in t/ ? t/harness could be taught to refer to that file, if it exists. > There's even a chance it might be kept slightly more up-to-date. > > Speaking more broadly, I find parrot's development very scattered. > It's hard to find stuff. Yup. Depends on what you're looking for, and there are a lot of places to look. If you look and can't find something, by all means ask on the list. To clarify what you might expect to find on these particular locations: > Was it on a mailing list? Usually recent conversations. Might have some historical conversation of note, but anything relevant to today's parrot should end up somewhere more permanent. > on a web page? > Which web page? launchpad? Moving towards this to tracking design issues... A work in progress. > some blog site? This is usually going to be an individual committer's status report, maybe aggregated via Planet Parrot. While this is a good place to find out what people have been working on lately, it shouldn't be considered a primary source of documentation. > perlfoundation.org? Only grant information is stored at the primary PF site; we link to the relevant pages from documents in the repository, so goto the repository first. There's also the wiki; this is on a par with the mailing list in terms of permanence; gives a more dynamic way to put docs together; items from here that need longevity eventually get moved into the repository; This is linked to from parrotcode.org (/wiki) ; > parrotcode.org? Much of docs/ on this site is just a pointer to docs in the repository; This is basically just a placeholder for release information and pointers how to get into the repository. > One of the web sites listed in the README file? I think referring to external sites from inside the README is reasonable. > Somewhere else? Was it on IRC (which isn't logged anywhere, so discussions > there are lost except to those who happen to be connected at the time)? We can certainly ask the community if there's consensus about turning on logging here... but even so, I wouldn't rely on this as a documentation method; if something is worth saving, it'll get written down, or a ticket opened, or the conversation will migrate to the slightly more permanent mailing list. I'm certainly interested in improving the state of the documentation; If you ask for stuff you can't find, that'll definitely help us improve the state of the parrot. > -- > Andy Dougherty [EMAIL PROTECTED] > > -- Will "Coke" Coleda -- Will "Coke" Coleda
