From Bastien Guerry to ~bzg/emacsfr
DarkBuffalo <darkbuffalo@gnu.re> writes: > Voici mon sourcehut <https://sr.ht/~darkbuffalo/> Je t'ai ajouté - merci ! ~$ git clone git@git.sr.ht:~bzg/emacs-doctor.com -- Bastien Guerry
From Bastien Guerry to ~sircmpwn/sr.ht-discuss
Страхиња Радић <sr@strahinja.org> writes: > Exactly. But by applying that logic (which I support wholeheartedly!), > GNU Emacs is a bloated mess and should be avoided whenever possible. > Something like Vim is much better, or if that still feels as too > bloated, plain vi or vis. .org files can be edited outside GNU Emacs: https://github.com/jceb/vim-orgmode https://github.com/vscode-org-mode/vscode-org-mode https://github.com/ihdavids/orgextended > Markdown, while arguably not ideal, is better and more widely
From Bastien Guerry to ~bzg/emacsfr
DarkBuffalo <darkbuffalo@gnu.re> writes: > Voici mon sourcehut <https://sr.ht/~darkbuffalo/> Je t'ai ajouté au dépôt https://git.sr.ht/~bzg/emacs-doctor.com Merci ! -- Bastien Guerry
From Bastien Guerry to ~bzg/emacsfr
Hello Matt, DarkBuffalo <darkbuffalo@gnu.re> writes: > Il s'agit d'un dépôt git à mettre à jour ou autres ? Oui, il s'agit d'être co-mainteneur avec Leo de ce dépôt : https://git.sr.ht/~bzg/emacs-doctor.com Pour l'instant c'est hébergé sur mon compte mais l'idée est que Leo pourra l'héberger sur le sien et que le groupe aidera au fait de payer le compte SourceHut (qui peut être à 2€ par mois) pour avoir accès à la CI de sr.ht et publier le site sur mon serveur (ou un autre).
From Bastien Guerry to ~bzg/emacsfr
Je suppose que l'information n'a échappé à personne, mais je crois qu'elle n'a pas encore été partagée ici : le week-end prochain aura lieu l'Emacs Conf 2024 ! Le programme, comme d'hab, est riche : https://emacsconf.org/2024/ Certains ont prévu d'y assister ? Perso je serai sur IRC pour papoter samedi entre 16h et 17h. Au plaisir de vous y croiser \o/ -- Bastien Guerry
From Bastien Guerry to ~sircmpwn/sr.ht-discuss
Matěj Cepl <mcepl@cepl.eu> writes: > I don’t think Sourcehut is focused on the same audience Agreed, but IMHO the relevant difference here is in the attitude towards the user base. I appreciate the fact that SourceHut users can discuss features directly with the team, and that they can contribute to its value by maintaining build images, submitting patches, etc., all sorts of things I don't expect from GitHub. I also appreciate the fact that SourceHut doesn't pretend to have an "open governance" with decision-making processes for user involvement:
From Bastien Guerry to ~bzg/emacsfr
Thierry Stoehr <thierry@formats-ouverts.org> writes: > L'animation des séances, quasiment uniquement en ligne depuis 4 ans et > demi (sauf 2 fois en salle pour moi), c'est oui, je sais que je sais > faire et que je peux faire. Merci Thierry ! Je te compte donc avec Matt et Leo dans l'équipe d'animation :) Et qui viendrait en soutien de Leo pour tenir à jour le site ? -- Bastien Guerry
From Bastien Guerry to ~sircmpwn/sr.ht-discuss
Matěj Cepl <mcepl@cepl.eu> writes: > Especially, when the solution of these problems is available. I don't think this is a good solution. > Comparison with GitHub is unfair, in my opinion, because > Sourcehut is a forge for-hackers-by-hackers, not for an > incompetent newbies and random Joe Doe from a street like GitHub. I'd argue that "hackers" also prefer clean direct solutions rather than clumsy hacks and workarounds :) --
From Bastien Guerry to ~sircmpwn/sr.ht-discuss
Matěj Cepl <mcepl@cepl.eu> writes: > You don’t have to do it on every commit, my example > ~mcepl/m2crypto does it just for merges to the master branch. Thanks for sharing this example. Still, direct support for more lightweight markup formats for rendering plain text files on sr.ht would be great. When you think about it, this is actually the requested feature: "visual rendering of plain text files when they use one of the most common lightweight markup languages" - this is *not* about "adding support for my favourite format".
From Bastien Guerry to ~sircmpwn/sr.ht-discuss
hi@eva.fish writes: > it's not discouraging org-mode, it's encouraging openness! Defaults matter. I understand that maintainers are careful not to add features that they would have to maintain over time with limited resources, and I can take a "no". In this case, I still think it is worth insisting: there is a reason why GitHub, GitLab (and probably others) support README.org, and it is not just to please a niche of users.