edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Cleverson Casarin Uliana <clcaul@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] master
Date: Tue, 28 Jan 2014 15:31:39 -0200	[thread overview]
Message-ID: <52E7E97B.5020007@gmail.com> (raw)
In-Reply-To: <87ha8om3hm.fsf@mushroom.PK5001Z>

On an issue tracker, I find Trac's interface quite easy, although I 
haven't tested it with edbrowse. It's used by the NVDA screen reader 
developers, for example.

Regards
Cleverson

Em 28/01/2014 15:16, Chris Brannon escreveu:
> Adam Thompson<arthompson1990@gmail.com>  writes:
>
>> Do we have some form of issue tracker which works with edbrowse (I'm not sure
>> how edbrowse-friendly the github setup is)?
>
> Well, the github issue tracker isn't edbrowse-friendly at all.  Github
> uses lots and lots of ajax and other fancy web stuff.
> However, they do provide an API for programmatic access.
> A few years back, I wrote a command-line interface to github, using
> their API.  It works well with their issue tracker.  You can clone the
> code here: git://github.com/CMB/cligh.git
> Coincidentally, this is the program I used to give you and Karl push
> access to the main repository.
> It's written in Python.  Also, it requires a couple of external
> dependencies, one of which is probably not packaged on most
> distributions.  I suspect this is a problem for some people.
>
>> On the subject of 3.4.11, apart from the js lib change and other bug fixes,
>> are there any other features or major changes we want to make before it
>> happens
>
> I don't think so.
>
> -- Chris
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

  reply	other threads:[~2014-01-28 17:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 11:20 Karl Dahlke
2014-01-28 16:41 ` Chris Brannon
2014-01-28 16:49   ` Adam Thompson
2014-01-28 16:41 ` Adam Thompson
2014-01-28 17:16   ` Chris Brannon
2014-01-28 17:31     ` Cleverson Casarin Uliana [this message]
2014-01-29 10:54       ` Adam Thompson
2014-01-28 17:35 Karl Dahlke
2014-01-28 21:31 ` Adam Thompson
2014-01-28 21:45 Karl Dahlke
2014-01-28 22:16 ` Chris Brannon
2014-01-29 10:48 ` Adam Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E7E97B.5020007@gmail.com \
    --to=clcaul@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).