indieterminacy at libre.brussels indieterminacy at libre.brussels
Mon Oct 25 12:02:01 BST 2021
- - - - - - - - - - - - - - - - - - -
Hi Alex,
Im personally ok with these suggestions.
There is certainly no harm falling back to the mailing list fordiscussions for the time being.
If people can synthesize things for future infrastructure and governancethen we can hopefully minimise duplication and align more effectively.
And people summarising issues and a tree of options would be helpful,particularly is cross threading is deployed.
Kind regards,
Jonathan
Alex Schroeder <alex at alexschroeder.ch> writes:
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 for
my personal projects, or projects where just a handful of people
collaborate, an issue tracker is nice to have but also overhead that's
easily ignored.
Futhermore, in our current setup, with all eyes focused on the mailing
list, perhaps keeping issues on a repository website is not only
alienating because of javascript and all that, but also a black hole
into which topics disappear, the assumption being that "somebody" is
going to handle them.
My suggestion is for somebody intending to write up stuff (what I
volunteered to do) to keep a todo list, for sure, and in public, if
possible, but without the expectation that people take the discussion
from the mailing list to the issue tracker.
Incidentaly, I suspect that having a Gemini-based issue tracker is not
going to solve the problem of tearing appart the discussion which is why
I 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 are
in discussion at any one time, we can always bring issue trackers back.
But for now, perhaps them being separate from the mailing list was a
mistake 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 it
goes. Perhaps I can pick up items from discussion on the mailing list
without having to involve myself in every discussion, or somebody can
tell me: "Hey Alex, I think we're ready to fix that section on X. Why
don't you take a look at the thread in the archives and write up a
draft?" And then I can separate myself from the flames emotionally, or
something 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 on
the mailing list would for the draft writer (e.g. me) to go through the
thread and pick out the various arguments in favour and against, and
write that summary for future reference, as part of the drafting
process.
Cheers
Alex