>> So I asked him privately via email, and he replied that he can't
>> reply/receive to fricas-devel, because Google wants cell number.
> This seems extremely odd to me.
Also to me. Google does not have a phone number from me, in fact,
without a mobile phone I could not even give one. ;-)
Google sometimes tries to convince me to provide a phone number, if they
force me to give one, I must give up my google account.
> So far as I know this isn't even necessary if you actually have a
> gmail account. Rather, it is perhaps an option in this case if you
> want to use 2-factor authentication.
Well, Bill, try to setup a new google account. I had a discussion with
Waldek some time ago and was surprised that (maybe from 2022 on) I am no
longer able to create a google or gmail account without providing a
phone number. If you know how one could do this, I'd be interested to know.
I use the fricas-devel list in the same way as Bill. I almost never
login to the webinterface. And since we have
https://www.mail-archive.com/fricas...@googlegroups.com/
there is no need for a google login. And the list is searchable.
> Although of course I want Waldek to participate in the FriCAS group
> but it seems strange to me if Waldek is the only user experiencing
> this problem. Perhaps it can be resolved just by accessing the group
> in a different way, i.e. by email.
Waldek is now subscribed at fricas-devel with a an email ending in
@
gtempaccount.com. That looks to me that he has changed his email and
maybe this is the source of his problem. Unfortunately, I have only
heard about google wanting a phone number, but not whether Waldek still
receives mail from fricas-devel.
To fix the problem of not being able to receive mails from fricas-devel
or post to it would be good, to learn a bit more about how this all came
about.
Today I have tested with Dima on another google mailing list, that it is
actually not necessary at all to have a google account in order to post
to the group or receive emails from it. The list owner (which is
currently Waldek, Bill and me can add people to the group with any email
address.
So my suggestion is, we continue using fricas-devel as always and put a
note to
fricas.github.io, that everyone who does not want to create a
google account sends an email to me and I will manually add them. I'm
sure that I will not be overburdened by this task.
Waldek, give me some email-address and I will add you to fricas-devel
and you can use our mailing list as before.
>> To quote Waldek's opinion:
>>
>> > ATM I am not sure what is better. One possiblity is to
>> > set up our own mail server. I could do this on the
>> > same machine as wiki.
I am strongly against it. That only causes needless maintenance work and
would run on a very old debian.
> Of course we could use GitHub
>> > mail. However, it is not clear what folks on the list
>> > want. For me old plain e-mail is preferable and also
>> > I would like sensible publicaly visible archive.
Exactly. We can continue as always. I just use my local mailreader to
communicate with fricas-devel.
>> Personally I prefer GitHub. Waldek replies with:
>>
>> > Well, GitHub web interface mangles code which is IMO serious problem.
>> > That is why I wrote "sensible publicaly visible archive", AFAICS
>> > GitHub does not qualify as "sensible" here.
>> But I think GitHub uses markdown, and ```` code block should solve it.
Yes. Wrapping code in
```
some code
here
```
is an easy exercise. But I must admit that I would also be happier if
github offered a way to simply post in ASCII. However, Markdown is
reasonably simple enough.
> GitHub would be fine with me if this is really necessary. But I think
> it is also very common to use GitHub with the 2-factor authentication
> option (at least I do) in which case a cell phone will usually also be
> involved.
The good thing with using git as a repository format is that we are not
bound to any particular provider. We would just have to declare one
particular clone to be the official one. And only for that reason I
initially wanted github. I still don't use many features from github,
but I see a clear advantage to have some kind of issue tracker that
allows for discussions on a particularly numbered issue. In fact, I very
much like that the issues are visible and not hidden in the noise of the
mailing list.
Everything should stay as is, but we should resolve Waldek's problem
with the mailing list. I'm pretty sure we can handle this to his liking.
Ralf