Re: [racket-dev] collections with no one responsible

5 hours ago, Sam Tobin-Hochstadt wrote: > > (eli?) > "collects/tests/profile/main.rkt" > "collects/tests/profile/topsort.rkt" > "collects/tests/lazy/main.rkt" > "collects/tests/lazy/forcers.rkt" > "collects/tests/lazy/promise.rkt" > "collects/tests/lazy/lang.rkt" > "collects/tests/file/md5.rkt" >

Re: [racket-dev] collections with no one responsible

Yes, there are two of them at the moment. Those are the only bugs assigned to 'nobody' at the moment. However, since I sent the last email I've had a volunteer to maintain the eopl collection, so hopefully this story will have a happier ending than I expected. Sam On Feb 17, 2012 6:15 PM, "Robby

Re: [racket-dev] collections with no one responsible

Sam Tobin-Hochstadt wrote at 02/17/2012 05:38 PM: 2. We keep it where it is, and don't maintain the code other than fixing life-threating bugs. This is basically the status quo, and I think it means people who report other, non-life-threatening bugs should be informed that we're not maintaining

Re: [racket-dev] collections with no one responsible

Do we have any bugs in category 2.? Robby On Fri, Feb 17, 2012 at 4:38 PM, Sam Tobin-Hochstadt wrote: > On Fri, Feb 17, 2012 at 9:00 AM, Robby Findler > wrote: >> On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt >> wrote: - eopl  Various people have changed this collection in th

Re: [racket-dev] collections with no one responsible

On Fri, Feb 17, 2012 at 9:00 AM, Robby Findler wrote: > On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt > wrote: >>> - eopl >>>  Various people have changed this collection in the past few years >>> (robby, eli, mflatt).  Who should I assign bugs to? >> >> If no one is maintaining this code

Re: [racket-dev] collections with no one responsible

On Fri, Feb 17, 2012 at 8:58 AM, Sam Tobin-Hochstadt wrote: >> Also, it would be good to run a script >> that checks that all source files are owned. > > Yes, that's a good idea.  I'll do that. The .rkt files with no one responsible are (all in tests, with who I think should be assigned them): (

Re: [racket-dev] collections with no one responsible

On Fri, Feb 17, 2012 at 9:06 AM, Matthew Flatt wrote: > At Fri, 17 Feb 2012 08:43:48 -0500, Sam Tobin-Hochstadt wrote: >> On Fri, Feb 3, 2012 at 6:32 PM, Sam Tobin-Hochstadt >> wrote: >> > As well as: >> > - gui-builder >> >  No one has made significant changes (other than collection-wide >> > c

Re: [racket-dev] collections with no one responsible

At Fri, 17 Feb 2012 08:43:48 -0500, Sam Tobin-Hochstadt wrote: > On Fri, Feb 3, 2012 at 6:32 PM, Sam Tobin-Hochstadt wrote: > > As well as: > > - gui-builder > >  No one has made significant changes (other than collection-wide > > cleanups) to guibuilder in more than 6 years, except Asumu.  Asumu,

Re: [racket-dev] collections with no one responsible

On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt wrote: >> - eopl >>  Various people have changed this collection in the past few years >> (robby, eli, mflatt).  Who should I assign bugs to? > > If no one is maintaining this code, would it be better for EOPL to > distribute a PLT file? I don'

Re: [racket-dev] collections with no one responsible

On Fri, Feb 17, 2012 at 8:52 AM, Eli Barzilay wrote: > Just now, Sam Tobin-Hochstadt wrote: >> >> For `tests', there are currently 3 files with no one responsible at >> the top level: >>  - eli-tester.rkt >>  - info.rkt >>  - run-automated-tests.rkt >> >> I think they should all have you as respon

Re: [racket-dev] collections with no one responsible

Just now, Sam Tobin-Hochstadt wrote: > > For `tests', there are currently 3 files with no one responsible at > the top level: > - eli-tester.rkt > - info.rkt > - run-automated-tests.rkt > > I think they should all have you as responsible, and I'll leave the > dir the way it is. Does that seem

Re: [racket-dev] collections with no one responsible

On Fri, Feb 3, 2012 at 7:47 PM, Eli Barzilay wrote: > An hour ago, Sam Tobin-Hochstadt wrote: >> Currently, the following collections have no one listed as >> responsible, along with who i think should be assigned to them: >> >> - tests (eli, mflatt)  -- just the top level directory, not the >>  

Re: [racket-dev] collections with no one responsible

On Fri, Feb 3, 2012 at 6:32 PM, Sam Tobin-Hochstadt wrote: > Currently, the following collections have no one listed as > responsible, along with who i think should be assigned to them: > > - mzlib (mflatt) Done. > Any objections to this?  If not, I'll do this soon. > > As well as: > - gui-build

Re: [racket-dev] collections with no one responsible

An hour ago, Sam Tobin-Hochstadt wrote: > Currently, the following collections have no one listed as > responsible, along with who i think should be assigned to them: > > - tests (eli, mflatt) -- just the top level directory, not the > subdirectories > - mzlib (mflatt) > - info-domain (mflatt)

Re: [racket-dev] collections with no one responsible

On 2012-02-03 18:32:46 -0500, Sam Tobin-Hochstadt wrote: > As well as: > - gui-builder > No one has made significant changes (other than collection-wide > cleanups) to guibuilder in more than 6 years, except Asumu. Asumu, do > you want to take this on? AFAIK, this doesn't even ship with the sta

[racket-dev] collections with no one responsible

Currently, the following collections have no one listed as responsible, along with who i think should be assigned to them: - tests (eli, mflatt) -- just the top level directory, not the subdirectories - mzlib (mflatt) - info-domain (mflatt) -- NB: contains no source files Any objections to this?