The github issue tracker is pretty nice for issue tracking.
On the subject of mbox viewer, hopefully Scott's work can be carried
on https://github.com/bytbox/go-mail
Let's bump this again. Someone might do something about it.
On 10 February 2012 18:25, Chris Siebenmann wrote:
> | > €I'm coming in late to an ongoing discussion: it sounds like there's
> | > something wrong with Byron's version of rc apart from being written from
> | > scratch for Unix (and not quite implementing Plan 9 rc syntax, since it
> | > doesn't h
On Friday, 10 February 2012, Christian Neukirchen
wrote:
> Anselm R Garbe writes:
>
>> On 9 February 2012 10:16, Hadrian Węgrzynowski
wrote:
>>> On Wed, 8 Feb 2012 20:15:52 +0100
>>> Anselm R Garbe wrote:
>>>
Btw. I would like you to use C and rc, not C and bash or something
similar.
>>
On 9 February 2012 10:16, Hadrian Węgrzynowski wrote:
> On Wed, 8 Feb 2012 20:15:52 +0100
> Anselm R Garbe wrote:
>
>>Btw. I would like you to use C and rc, not C and bash or something
>>similar.
>
> There were once discussion about "blessed" rc version, but AFAIR there
> were no simple conclusio
On Wed, 8 Feb 2012 20:15:52 +0100
Anselm R Garbe wrote:
>Btw. I would like you to use C and rc, not C and bash or something
>similar.
There were once discussion about "blessed" rc version, but AFAIR there
were no simple conclusion. What version of rc is good enough?
What I remember: Byron's vers
On 8 February 2012 10:53, Ahmet Emre Çepoğlu wrote:
> On Thu, Jan 26, 2012 at 2:40 AM, Paul Hoffman wrote:
>> That's good for starters. Here's a simple issue tracker repository
>> using directories, key-value text files, and symlinks:
>>
>> /path/to/repo/
>> ticket/
>> abc123/
>>
On Thu, Jan 26, 2012 at 2:40 AM, Paul Hoffman wrote:
> > - store everything under version control system: closed/resolved issues
> > can be moved to different branch (smaller checkout)
>
> Interesting.
>
> > This way data can be accessed very easily, some usage ideas:
> >
> > - searching for exis
So, how are things going? I guess setting up an existing BTS on
suckless.org while waiting is out of the question?
I'm already using some sort of TODO/XXX in comment but it could be better...
For what it's worth, here's my usecase/design/whatever. I don't need much:
- basic interface (cli, mail, h
On Fri, Jan 13, 2012 at 03:27:26PM +0100, Paul Onyschuk wrote:
> On Thu, 12 Jan 2012 19:34:09 +0200
> aecepoglu@ wrote:
>
> >
> > I might be interested in trying to help write one such suckless issue
> > tracker as requested on the webpage.
> >
> > I just want to ask;
> > What set of features ar
After playing with a test maildir, I'm less convinced of the ease of use
of that setup. It takes some config abuse of my mail client of choice
(mutt) to get it to not send messages and instead just store in the
local dir.
On Sun, Jan 15, 2012 at 09:25:33AM -0500, Kurt H Maier wrote:
> On Sat, Jan
On 16 January 2012 01:27, Kurt H Maier wrote:
> On Sun, Jan 15, 2012 at 01:27:28PM +1100, Alex Hutton wrote:
>> It seems to me it might overly complicate things to build the issue
>> tracker into a mail system or into git.
>>
>> The core functionality of tracking issues can be implemented in a
>>
On Sun, 15 Jan 2012 14:07:09 +
Stephen Paul Weber wrote:
>
> While I agree that adding custom headers is likely to be a pain and
> make users come up with hacks, some headers are very well
> standardized. Most notably In-Reply-To and Message-ID. IMHO, and
> "id" for the bug should be the Me
On Sun, Jan 15, 2012 at 01:15:10PM +0800, Kai Hendry wrote:
> I'm gone down the TODO list http://webconverger.org/todo/ and it's not
> "social" enough I dare say. You need commenting and +1 and all that
> crap nowadays, to keep interested.
if you need stupid games to keep people interested then th
On Sun, Jan 15, 2012 at 01:27:28PM +1100, Alex Hutton wrote:
> It seems to me it might overly complicate things to build the issue
> tracker into a mail system or into git.
>
> The core functionality of tracking issues can be implemented in a
> meta-language.
are you even listening to yourself?
On Sat, Jan 14, 2012 at 12:26:45PM +0100, Paul Onyschuk wrote:
> Maildir is a bit overkill in my opinion, just look at naming convention
> [1]. If you want to use "file per message" format, MH provides simpler
> solution (name of file is just a ID number e.g. 1, 2, 15 and so on).
really? that's
Somebody claiming to be Anselm R Garbe wrote:
On 12 January 2012 19:06, Anselm R Garbe wrote:
The reason I suggest to base the bug tracker "view" on a mail
archiving tool is simply because this problem hasn't been solved in an
acceptable way either (and we'd need a better system anyways).
Yes,
On Sun, 15 Jan 2012 13:27:28 +1100
Alex Hutton wrote:
>
> It seems to me it might overly complicate things to build the issue
> tracker into a mail system or into git.
>
> The core functionality of tracking issues can be implemented in a
> meta-language.
>
Static web generators (werc/ikiwiki et
> Afterwards all bug-related communication targets this email address. A
> suckless developer with the permission to amend the bug status could
> now send special commands to this address:
This is bullshit. An email address is no command line interface.
Greetings.
Kai Hendry wrote:
> On 14 January 2012 00:28, Paul Onyschuk wrote:
>> Right now best interfaces for issue trackers are search engines (e.g.
>> Google "site:adress_of_bug_tracker interesting issue") and mail
>> archives (Gmane and so on) in my opinion.
>
> I don't think they are the "b
On Sun 15 Jan 2012 08:06:55 AM PST, Anselm R Garbe wrote:
> If someone is unhappy that a bug was closed, issue a new bug. Closing
> a bug should be a final operation (in my experience this is one
> problem with the existing BTS that allow re-opening closed bugs, but
> re-opening closed bugs means y
On 12 January 2012 19:06, Anselm R Garbe wrote:
> One of the most important things of such a tracker is decent mail
> integration in my opinion (as most trackers that have evolved in the
> OSS space recently suck very much when it comes to mail integration).
>
> One aspect of this tracker could be
On 13 January 2012 19:17, Kurt H Maier wrote:
> All you really need is a good mail gateway and a decent way to browse.
> A mailing list, with the archive accessible in source control of some
> kind, sounds absolutely fantastic. All you really need as far as
> metadata is a string for project name
On 13 January 2012 01:34, wrote:
> What set of features are a must for you?
It pains me to say this, but the best BTS I've come across is
https://www.pivotaltracker.com/
Seriously.
It has great Web interface and a decent mail integration. You really
should study this.
I think Github's issue
On 13 January 2012 02:06, Anselm R Garbe wrote:
> One aspect of this tracker could be to start with a proper mail
> archiving system and then writing the web stuff on top. This would
+1 on decent HTML5 Web interface on a maildir or something. I think
this is a precursor to any project that wants
On 14 January 2012 00:28, Paul Onyschuk wrote:
> Right now best interfaces for issue trackers are search engines (e.g.
> Google "site:adress_of_bug_tracker interesting issue") and mail
> archives (Gmane and so on) in my opinion.
I don't think they are the "best interfaces". It's the only option a
It seems to me it might overly complicate things to build the issue
tracker into a mail system or into git.
The core functionality of tracking issues can be implemented in a meta-language.
For instance, you have one file per issue, and the issue files would
look something like this.
[timestamp]
> I did not say once that I was doing this...
Perhaps you overlooked the word "maybe", so I'll still try to answer
-- disregard my rage -- with a question:
Why might you be interested in trying to help write one such suckless
issue tracker as requested on the webpage?
On 14 January 2012 16:16, Ahmet Emre Çepoğlu wrote:
> Why are you telling me this? I did not say once that I was doing this
> because I was bored.
He's just a (pretty lame) troll.
cls
On 1/14/12, hiro <23h...@googlemail.com> wrote:
> Maybe you shouldn't write software because you're bored.
>
Why are you telling me this? I did not say once that I was doing this
because I was bored. Only because people know more than me, I should
sit in the corner and watch? If that is actually th
Maybe you shouldn't write software because you're bored.
On Fri, 13 Jan 2012 17:22:12 -0600
Hank Donnay wrote:
>
> I like the idea of maildir-in-git, it makes something like
> automatically generating a website trivial with hooks.
>
Maildir is a bit overkill in my opinion, just look at naming convention
[1]. If you want to use "file per message" form
On Sat, 14 Jan 2012 11:54:58 +0100, hiro <23h...@googlemail.com> wrote:
> mail sucks
>
It may very well be because I'm awake since yesterday, but (taking
into account the message you replied to) that was goddamn hilarious!
Thanks!
Peace
--
Pieter
mail sucks
So:
* Binary is a no no.
* Issues are stored in one way or another as mail(s).
* That sits under a version control.
And an issue has the fields:
* status
* id
* project
I am guessing what project it belongs to will already be in the address fileld.
and the id will be in the subject.
If foldere
Most issue tracker entries are full of stupid garbage we don't want
anyway. What worked great was the script we once had on the wmii irc
channel which just appended sentences beginning with BUG to the
buggfile.
Editing the sentences and then deleting all useless entries or
redundant letters keeps e
I like the idea of maildir-in-git, it makes something like automatically
generating a website trivial with hooks.
On Fri, Jan 13, 2012 at 11:35:33PM +0100, Paul Onyschuk wrote:
> On Fri, 13 Jan 2012 22:48:04 +0100
> markus schnalke wrote:
>
> >
> > Unless you want to make changes ...
> >
>
> "
On Fri, 13 Jan 2012 22:48:04 +0100
markus schnalke wrote:
>
> Unless you want to make changes ...
>
"Abandon all hope, ye who enter here". My personal workaround is to
join IRC channel (or spam mailing list) and force developer/commiter to
create issue. Ugly hack, but works most of the times.
[2012-01-13 17:28] Paul Onyschuk
> On Fri, 13 Jan 2012 15:48:43 +0100
> markus schnalke wrote:
>
> Mbox formats are human readable, and file per issues makes it
> accessible. Throwing everything into one file (like mbox mail archive)
> or splitting everything into zillon files (file per message l
On Fri, 13 Jan 2012 13:17:13 -0500
Kurt H Maier wrote:
>
> debbugs is a bit overblown. As a systems administrator I've had the
> profound displeasure of interacting with dozens of issue trackers over
> the years; everything from RT to Trac to JIRA and on and on. The
> problem is always the same
On Fri, Jan 13, 2012 at 05:28:19PM +0100, Paul Onyschuk wrote:
> What makes old plain TODO interesting is zero setup offline usage and
> direct access to data (checkout repository and open in your favorite
> editor).
and then it turns into a huge mess when some vim nerd has expandtab
turned on.
>
On Fri, 13 Jan 2012 15:48:43 +0100
markus schnalke wrote:
>
> No, put meta information in the header, where it belongs to. anno(1)
> from MH does it for you.
>
> Any newer message might change these attributes. Well, you might want
> to update these attributes in the first message, to have the l
[2012-01-13 15:27] Paul Onyschuk
>
> - treat first message in mbox as meta: modify and store common
> informations (priority, short description, category of issue and so on)
> there
No, put meta information in the header, where it belongs to. anno(1)
from MH does it for you.
Any newer message m
On Thu, 12 Jan 2012 19:34:09 +0200
aecepoglu@ wrote:
>
> I might be interested in trying to help write one such suckless issue
> tracker as requested on the webpage.
>
> I just want to ask;
> What set of features are a must for you?
>
After reading some discussion I have some ideas. For small
2012/1/12 markus schnalke
> [2012-01-12 19:06] Anselm R Garbe
> > On 12 January 2012 18:34, wrote:
> > >
> > > I might be interested in trying to help write one such suckless
> > > issue tracker as requested on the webpage.
> > >
> > > I just want to ask;
> > > What set of features are a must
[2012-01-12 19:06] Anselm R Garbe
> On 12 January 2012 18:34, wrote:
> >
> > I might be interested in trying to help write one such suckless
> > issue tracker as requested on the webpage.
> >
> > I just want to ask;
> > What set of features are a must for you?
>
> Oh what a relief someone wants
On 12 January 2012 19:58, Bjartur Thorlacius wrote:
> What's wrong with GNATS?
Nearly everything. GNU, 50kSLOC, etc.
Cheers,
Anselm
What's wrong with GNATS?
On 12 January 2012 18:34, wrote:
> I might be interested in trying to help write one such suckless issue tracker
> as requested on the webpage.
>
> I just want to ask;
> What set of features are a must for you?
Oh what a relief someone wants to volunteer on this idea.
One of the most important
I might be interested in trying to help write one such suckless issue tracker
as requested on the webpage.
I just want to ask;
What set of features are a must for you?
Thanks,
cheers.
50 matches
Mail list logo
