[Phpmyadmin-devel] Commit notifications
Hi all It looks like commit notifications is something sourceforge does not like: https://sourceforge.net/apps/trac/sourceforge/ticket/17347 -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
2011/2/11 Michal Čihař <michal@cihar.com>:
Hi all
It looks like commit notifications is something sourceforge does not like:
Hi Michal, I saw your blogpost [0] about this. I agree that having to provide an E-mail sending script to an external website, would potentially cause a lot of security breaches, or vehicles for sending spam. I like the E-mail notifications of the commits, it keeps me informed of new commits and what's being commited, and I'm sure other developers like this too. So I also would like to see it re-enabled one way or the other, be it by an external script, SF.net allowing sending E-mails from the gitserver again, or even hosting the repository on another server. But I think that this last option should be a last resort. SF.net provides a lot of tools for managing a project, so having to set it up on our own, or transferring everything to another provider would take quite some work and effort. [0] http://blog.cihar.com/archives/2011/02/11/tightening-too-much/ Kind regards, Dieter
Hi Dne Sat, 12 Feb 2011 11:17:37 +0100 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I saw your blogpost [0] about this. I agree that having to provide an E-mail sending script to an external website, would potentially cause a lot of security breaches, or vehicles for sending spam. I like the E-mail notifications of the commits, it keeps me informed of new commits and what's being commited, and I'm sure other developers like this too. So I also would like to see it re-enabled one way or the other, be it by an external script, SF.net allowing sending E-mails from the gitserver again, or even hosting the repository on another server.
What I don't like is that they are pushing their problem to the users - now every project would have to take care of sending of notification emails. I think this is simply wrong as any possible problem could be much better handled in the infrastructure than by using arbitrary hacks which will every project introduce.
But I think that this last option should be a last resort. SF.net provides a lot of tools for managing a project, so having to set it up on our own, or transferring everything to another provider would take quite some work and effort.
Yes is is definitely last resort solution. In case we can only move git hosting elsewhere, what would definitely not be that hard. Anyway filing new ticket because the official documentation still contains not working script to do the notifications and I will try to add mailing list to CC. -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
Hi Dne Sat, 12 Feb 2011 21:39:37 +0100 Michal Čihař <michal@cihar.com> napsal(a):
Anyway filing new ticket because the official documentation still contains not working script to do the notifications and I will try to add mailing list to CC.
Okay, it did not seem to work, the bug report is here: https://sourceforge.net/apps/trac/sourceforge/ticket/17525 -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
Le 2011-02-12 15:57, Michal Čihař a écrit :
Hi
Dne Sat, 12 Feb 2011 21:39:37 +0100 Michal Čihař <michal@cihar.com> napsal(a):
Anyway filing new ticket because the official documentation still contains not working script to do the notifications and I will try to add mailing list to CC.
Okay, it did not seem to work, the bug report is here: https://sourceforge.net/apps/trac/sourceforge/ticket/17525
In the blog, just after "as mentioned above, outbound email is not functional so any script utilizing this will fail. If you need to send outbound email, a workaround would be to use curl and and external site or Project Web to send the email." They write "We are still working hard to restore all services, and we appreciate your continued patience." So I believe that this is temporary. -- Marc Delisle http://infomarc.info
Le 2011-02-13 07:07, Marc Delisle a écrit :
Le 2011-02-12 15:57, Michal Čihař a écrit :
Hi
Dne Sat, 12 Feb 2011 21:39:37 +0100 Michal Čihař <michal@cihar.com> napsal(a):
Anyway filing new ticket because the official documentation still contains not working script to do the notifications and I will try to add mailing list to CC.
Okay, it did not seem to work, the bug report is here: https://sourceforge.net/apps/trac/sourceforge/ticket/17525
In the blog, just after "as mentioned above, outbound email is not functional so any script utilizing this will fail. If you need to send outbound email, a workaround would be to use curl and and external site or Project Web to send the email."
They write "We are still working hard to restore all services, and we appreciate your continued patience."
So I believe that this is temporary.
I wrote to sfnet_ops@geek.net asking for a clarification. -- Marc Delisle http://infomarc.info
Hi Dne Sun, 13 Feb 2011 07:07:13 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
In the blog, just after "as mentioned above, outbound email is not functional so any script utilizing this will fail. If you need to send outbound email, a workaround would be to use curl and and external site or Project Web to send the email."
They write "We are still working hard to restore all services, and we appreciate your continued patience."
So I believe that this is temporary.
Well it does not sound like that from reply to my bug report, but maybe I am wrong: http://sourceforge.net/apps/trac/sourceforge/ticket/17347#comment:3 -- Michal Čihař | http://cihar.com | http://blog.cihar.com
2011/2/14 Michal Čihař <michal@cihar.com>:
Hi
Dne Sun, 13 Feb 2011 07:07:13 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
In the blog, just after "as mentioned above, outbound email is not functional so any script utilizing this will fail. If you need to send outbound email, a workaround would be to use curl and and external site or Project Web to send the email."
They write "We are still working hard to restore all services, and we appreciate your continued patience."
So I believe that this is temporary.
Well it does not sound like that from reply to my bug report, but maybe I am wrong:
http://sourceforge.net/apps/trac/sourceforge/ticket/17347#comment:3
Hi all, It seems the commit notifications by E-mail work again. Did you change anything in the scripts, Michal? Or did sf.net re-enable it? Greets, Dieter
Hi Dne Tue, 15 Feb 2011 10:01:19 +0100 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
It seems the commit notifications by E-mail work again. Did you change anything in the scripts, Michal? Or did sf.net re-enable it?
No I did not change anything, so it seems they have reverted this restriction. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
2011/2/12 Michal Čihař <michal@cihar.com>:
Hi
Dne Sat, 12 Feb 2011 11:17:37 +0100 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I saw your blogpost [0] about this. I agree that having to provide an E-mail sending script to an external website, would potentially cause a lot of security breaches, or vehicles for sending spam. I like the E-mail notifications of the commits, it keeps me informed of new commits and what's being commited, and I'm sure other developers like this too. So I also would like to see it re-enabled one way or the other, be it by an external script, SF.net allowing sending E-mails from the gitserver again, or even hosting the repository on another server.
What I don't like is that they are pushing their problem to the users - now every project would have to take care of sending of notification emails. I think this is simply wrong as any possible problem could be much better handled in the infrastructure than by using arbitrary hacks which will every project introduce.
True. Can we let them know how we feel about this? I guess we are not alone in this...
But I think that this last option should be a last resort. SF.net provides a lot of tools for managing a project, so having to set it up on our own, or transferring everything to another provider would take quite some work and effort.
Yes is is definitely last resort solution. In case we can only move git hosting elsewhere, what would definitely not be that hard.
Anyway filing new ticket because the official documentation still contains not working script to do the notifications and I will try to add mailing list to CC.
OK. Anyway, I think we should wait until SF.net replied to the bugreport, before starting to make any plans. Greets, Dieter
participants (3)
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař