HN user

bzg

872 karma

Free Software and Free culture.

https://bzg.fr

Posts16
Comments42
View on HN

In 2012, he travelled to France and bought me a beer to thank me for my work on Org-Mode, and it was great. He was enthusiastic about this worldwide half-random connections, and insisted on how great it was to be able to connect with everyone in this way... we certainly miss him and that spirit.

He contributed to GNU Emacs Org-Mode with gnugol: https://list.orgmode.org/4D210A00.9070901@teklibre.org/

Hi, I'm in charge of code.gouv.fr and I initiated this BlueHats prize.

The money comes from the French government (4x10K€ for the four prizes).

We wanted to do this with NLnet to benefit from their experience and to rely on another entity to transfer the funds.

We received a lot of interesting submissions and asking public administrations who deserves the award is already a very nice exercise. We will write more about the process and the lessons learned after this first (experimental) iteration.

Thanks! No, we don't plan to self-host and manage our own instance of sr.ht: the FLOSS unit at Etalab is small, we have just a few repos.

Also, self-hosting a sr.ht would make sense if we can welcome repos from any public agency, but there is no plan for such a project, partly due to the lack of resources.

Long and nice read.

Ten years ago, there was still heated debates about whether Nicolas Carr was right.

Now we kind of know he somehow was right, so parts of the debate are over, while others, still relevant parts, leave us speachless. Or maybe that's just me.

Hi! Thanks for your feedback. I think the Org mailing list has a pretty good record of both useful and polite conversations.

I don't know if the tone of conversations is different on mailing lists vs. web UIs like issues, PRs or code reviews.

As I said in another reply, I guess we can somehow reconcile both worlds by allowing PRs to be sent as patches to a mailing list - I guess https://sr.ht could support something like this (if it does not already).

The thing with the whole "entry barrier" point of people who want Org-mode development to happen on Git(Lab|Hub) is that they miss the point: I don't want more contributions, I want more engaged contributors, more committed support of any kind.

I find emails to be more engaging than emojis on a web interface - and I use both on a daily basis, so perhaps I don't deserve my #okboomer yet :)

I hope one day both worlds will reconcile.

After all, it should be possible to have PRs sent as patches over a mailing list (and we don't need manual patches to be published as PRs.)

We don't use code.orgmode.org for Org's development.

But please clone Org's repo, make a patch - perhaps with https://magit.vc - and attach it to an email you send to emacs-orgmode@gnu.org: that's all it takes.

Then we will help with polishing your contribution :)

"I can't participate or reply on the web interface, I have to sign up for something completely different to participate"

Let me correct this one: no, you don't have to sign up to anything: (1) click on a bug entry on https://updates.orgmode.org then (2) click on "try the mailto: link" link.

This is other way around: if Org goes to GitLab, GitHub-only users will have to sign up to GitLab just to report an issue, and same for GitHub.

"But there's something else, there's now an entire generation of software developers who simply don't know how to deal with sending patches, etc., and they don't even care. And that's not a good trend."

Agreed. I hope https://sr.ht can help resisting this trend. I'm sure there are plenty of happy Git(Lab/Hub) users here but again, I'm not convinced these platforms would fit Org's needs.

I confirm it still makes sense.

I just want to make things easier for the futur Org maintainer by spending the next few months recruiting more contributors.

Can you elaborate a bit more on how this would simplif the contribution process?

Perhaps it would make it more familiar, but I don't think it would really simplify it.

First because I think issue handling on GitLab/GitHub kinda worsen the problem of the lack of maintainance resources, instead of fixing it

Second because we are quite strict on how to format changelog entries, and I believe email interactions help educating contributors in a nice way, while MR/PR interactions might generate more fatigue -- not so sure about this one, though.

Well, of course you can revert a commit from org-mode.

Simply create a bash source code block that goes in the right directory and does the git revert. \o/

Did you try to see what made the table unusable? If you feel want, you can report this to emacs-orgmode@gnu.org and maybe we can do something about it. Thanks!