💾 Archived View for rawtext.club › ~sloum › geminilist › 007386.gmi captured on 2023-11-14 at 08:38:33. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Alex Schroeder alex at alexschroeder.ch
Mon Oct 25 11:28:07 BST 2021
- - - - - - - - - - - - - - - - - - -
DJ Chase <u9000 at posteo.mx> writes:
This brings up a good point - though probably best suited for the parent
thread - of whether we even need issue trackers. What do y'all think of
this?
It depends on activity of the project, in my experience. I know that formy personal projects, or projects where just a handful of peoplecollaborate, an issue tracker is nice to have but also overhead that'seasily ignored.
Futhermore, in our current setup, with all eyes focused on the mailinglist, perhaps keeping issues on a repository website is not onlyalienating because of javascript and all that, but also a black holeinto which topics disappear, the assumption being that "somebody" isgoing to handle them.
My suggestion is for somebody intending to write up stuff (what Ivolunteered to do) to keep a todo list, for sure, and in public, ifpossible, but without the expectation that people take the discussionfrom the mailing list to the issue tracker.
Incidentaly, I suspect that having a Gemini-based issue tracker is notgoing to solve the problem of tearing appart the discussion which is whyI personally don't want to invest too much energy into it.
And if we find that discussions go in circles, or too many hot spots arein discussion at any one time, we can always bring issue trackers back.But for now, perhaps them being separate from the mailing list was amistake as it cut them off from discussion.
Also great, though I am confused as to how this does not conflict with
your above quote: "I'm happy with using git, and discussions on the
mailing list".
Yeah, I'm unsure of how to bridge that gap myself. We'll see how itgoes. Perhaps I can pick up items from discussion on the mailing listwithout having to involve myself in every discussion, or somebody cantell me: "Hey Alex, I think we're ready to fix that section on X. Whydon't you take a look at the thread in the archives and write up adraft?" And then I can separate myself from the flames emotionally, orsomething like that. I'll have to figure something out.
It could be good to have an actual digest-mode instead of simply
grouped-emails.
Perhaps one good way of working out issues after a lively discussion onthe mailing list would for the draft writer (e.g. me) to go through thethread and pick out the various arguments in favour and against, andwrite that summary for future reference, as part of the draftingprocess.
CheersAlex-- Fingerprint: DF94 46EB 7B78 4638 7CCC 018B C78C A29B ACEC FEAE