💾 Archived View for rawtext.club › ~sloum › geminilist › 007383.gmi captured on 2023-09-08 at 16:36:05. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
DJ Chase u9000 at posteo.mx
Mon Oct 25 01:00:39 BST 2021
- - - - - - - - - - - - - - - - - - -
On Sun, 2021-10-24 at 22:52 +0200, Alex Schroeder wrote:
I'd love to build a team and get going. If anyone else wants to as
well, please say so.
I'm willing to help.
Great! Thank you.
In the spirit of showing what sort of things I'd be about:
TLDR: I agree with most of these things. I've replied to a fewdisagreements below, but otherwise I pretty-much agree. I'd love to haveyou on the team.
I like to use git directly. We can all collaborate using our respective
git repositories and pull requests. If one of us uses a repository
available via GitLab, SourceHut or some other platform, that's a nice
bonus, but as far as I'm concerned, I'm happy with using git, and
discussions on the mailing list.
I mostly agree with this. I agree we should be "using git directly", butI don't consider sending around pull-requests to various repos to beusing git directly. Multiple repos are totally fine, but we should usegit's native way of distributing patches: git send-email. I know thatrequiring send-email would put some people off, though, so I'm fine withalso accepting patches via the method you described above.
Either way, though, I think that we should still have onecentral/official repo. Not having one would mean that new contributorswould have nothing to clone in order to get started.
[...] I'm happy with using git, and discussions on the mailing list.
This brings up a good point - though probably best suited for the parentthread - of whether we even need issue trackers. What do y'all think ofthis?
My preferred way of working would be discussing things on the mailing
list, me writing a draft on the wiki, and finally committing it to my
repository and then inviting others to pull it.
I think it's important that people be able to submit patches in additionto just discussing it on the mailing list. A draft branch may be thebest way of doing this, but of course I'm open to ideas.
Based on the above, I guess I'm volunteering for draft writing,
maintaining one of the repos, and the process of getting things into
that repo,
Awesome.
and less for lively mailing list discussion.
Also great, though I am confused as to how this does not conflict withyour above quote: "I'm happy with using git, and discussions on themailing list".
In an ideal
world, friends would read the mailing list for me and summarize the
discussion for me.
It could be good to have an actual digest-mode instead of simplygrouped-emails.
Anyway, if you're interested in having me on the team in a role that
plays to my strength, then you have my … keyboard, I guess. :)
I'd love to have you on the team assuming people aren't greatly upset bythis. It seems improbable that people would be so.
-- DJ ChaseThey, Them, Theirs