[Scons-dev] Is Tigris issue tracking actively used?

anatoly techtonik techtonik at gmail.com
Mon Jul 7 16:01:17 EDT 2014


On Sun, Jul 6, 2014 at 3:25 PM, Andrew Featherstone
<andrew.featherstone at cantab.net> wrote:
> Hi All,
>
> I was wondering what the current state of issue tracking is for the SCons
> project. There was some talk a little while back about moving away from
> Tigris to a different issue tracker, has that happened?

No. Sorry. Dirk made script to export tigris.org issues, which I saved here:
https://bitbucket.org/techtonik/dataliberation/src/tip/issues/?at=default
but Google deprecated their Issue API, probably due a lot of spam:
https://code.google.com/p/support/wiki/IssueTrackerAPIPython
Bitbucket supports import/export, but was considered awful by me:
https://confluence.atlassian.com/display/BITBUCKET/Export+or+import+issue+data
and then I stuck with reversing Roundup tracker model.

The task to move is assigned to me here http://scons.org/wiki/Roadmap
but I don't have timeframe when I can work on it.

I wanted:
1. Good framework for transformation of structured data
2. Duplicate Tigris dashboards (that's why Roundup - it allows hacking)
    Ezio Melotti made a proof of concept here:
    http://bugs.python.org/issue?@template=stats

I've made:
1. Support for Jinja2 template engine to Roundup

What is needed:
1. HTML hackery to get design that we want
    (and not what is available)
    some mockups would be fine
2. Field list with types from old tracker and new tracker
    "field type" need a good definition, such as:
        type: username
        handle as: string
        requirement: unique
        requirement: should exist in usernames table
   This is for consistency checks and for cases where
   we need to restore consistency.

> What's the model used for triaging and resolving issues? The "we're looking,
> so email us" approach on http://www.scons.org/dev.php feels a bit
> old-fashioned, particularly compared to the "social coding" feel you get on
> Github where you can comment on an issue, create a branch on a fork and try
> to close the issue via a pull request.

SCons had an exceptional IRC triaging sessions that got me hooked in the
first place, the process is described in wiki, but we don't do this
often anymore.

I guess I need just make a converter to Bitbucket and that's all.
-- 
anatoly t.


More information about the Scons-dev mailing list