Dirk, If you can create a HTML dump, I can put it up on the scons.org webserver and link to it. And then maybe we create a repo to check in all the source files with scripts to regen?
-Bill On Sat, Aug 31, 2019 at 5:09 AM Dirk Bächle <tshor...@gmx.de> wrote: > Hi, > > this approach sounds good to me too. I just wanted to mention that I have > all the old Tigris Issues (and user and developer mails) > archived on my local machine. They're stored in a simple text-ish format > that can be read into corresponding Python classes. > My plan is still to write a small "viewer" app, that would enable > interested developers/users to "browse" through the "SCons > archives". In my view there is a lot of hidden knowledge in there, that we > can't really use at the moment. > > I'll try to check whether my "archive" is still up-to-date during the next > days. ;) > > Best regards, > > Dirk > > On 27.08.19 15:53, Gary Oberbrunner wrote: > > I think this would be great. I'll help review the bugs-to-be-closed. > > > > -- Gary > > > > On Tue, Aug 27, 2019 at 8:50 AM Mats Wichmann <m...@wichmann.us <mailto: > m...@wichmann.us>> wrote: > > > > > > Just to pull some thoughts together: > > > > there are currently 679 open scons issues on github. > > > > That number drops to 92 if you select only ones which have had a > > modification since the big migration from tigris. Try this query: > > > > is:issue is:open updated:>=2018-02-10 > > > > or as a link: > > > > > https://github.com/SCons/scons/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+updated%3A%3E%3D2018-02-10+ > > > > I'm a relative newcomer around here, but I don't see the value of > > showing a ton of historical bugs that aren't being worked on; the > newly > > filed ones don't even get a lot of attention - there just isn't a big > > scons team at this point and numerically most current contributors > have > > a specific motivation ("itch to scratch" as it were) rather than the > > ability to just generally work on bugs. To provide more visible > focus > > there's already been some discussion of a bug prune. > > > > My suggestion is this: > > > > (a) close all open tigris bugs with a message that includes these > items: > > > > * bug is now tracked on github [link] > > * bugs which have not had activity in 18 months are going to be > closed > > (it doesn't have to be 18, but that was the cutover time) > > * we understand readers of this issue might not see messages from > > github, so if you want to keep this issue alive, make a comment - any > > comment - on the corresponding github issue. > > > > (b) fire up a bot to mark inactive github issues with a tag, and > > configure suitably. Looks like there's an app in the github > marketplace > > that is free so setup is just a YAML file. Example setup here: > > > > > https://github.com/timgrossmann/InstaPy/commit/afd968dfa1ce1141456a207484d35f2766d5916b > > > > the app: > > > > https://github.com/marketplace/stale > > > > (c) someone scan through the first-time closure proposal list and > > manually update any which seem deserving of continued life. > > > > > > Closed-as-stale issues don't vanish, they are still there to be > browsed > > as needed... > > > > _______________________________________________ > > Scons-dev mailing list > > Scons-dev@scons.org <mailto:Scons-dev@scons.org> > > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > > > > > > > -- > > Gary > > > > _______________________________________________ > > Scons-dev mailing list > > Scons-dev@scons.org > > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev