Re: issue tracker?

[Diego Zamboni]

Hi all,

Interesting discussion. I have also wondered about this - I have not
yet contributed to the Org codebase, but I have wondered if patches
and bug fixes can sometimes get lost among other discussions.

However, ultimately the best tracking system is the one that works for
the developers and their workflow. A full-featured issue tracking
system is useless if the developers don't have the habit of using it.

So, whatever works for Nicolas and all the other wonderful people who
maintain this amazing piece of software for free, works for me :)

Best,
--Diego



On Tue, May 19, 2020 at 10:18 PM Roland Everaert <address@hidden> wrote:
>
> Sourcehut seams interesting. Did you know if importing github/gitlab 
> projects, with issues and merge requests (opened and closed) is supported at 
> the moment?
>
> I noticed it is in alpha, so I don't expect to see all the features of any of 
> those forges yet.
>
> Before I forget, Does magit+forge works well with sourcehut, especially the 
> latter, as the former shouldn't have any problem?
>
>
> Regards,
>
> Roland.
>
>
> On Tue, May 19, 2020 at 9:43 PM Eric Abrahamsen <address@hidden> wrote:
>>
>> "James R Miller" <address@hidden> writes:
>>
>> > So, I definitely agree that using Github / Gitlab does expose you to
>> > tracking messes and that is something to shun. I figured a self-hosted
>> > Gogs instance (which is already being hosted at
>> > https://code.orgmode.org/bzg/org-mode) would fix the "tracking" issue.
>> >
>> > I think an actual issue tracker has merit to large projects.
>>
>> I've been going around doing proselytizing for sr.ht (sourcehut, aka
>> "Sir Hat"), which is a forge-like site that is very much in line with
>> Emacs' principles. No tracking (barely any javascript at all),
>> everything can be driven via email -- it's pretty nice. Could be a good
>> solution here.
>>
>> (Not affiliated, though I do give them money.)
>>
>> Eric
>>