On Thu, Jan 25, 2018, at 2:45 PM, Brian Exelbierd wrote:
On Thu, Jan 25, 2018, at 2:08 PM, Martin Quinson wrote:
> Hello pals,
>
> it was decided that the alioth hosting service will be soon
> decommissioned[1] next month, and we should move the development to
> another hosting service. I should have done that mail before, sorry.
>
> The git itself was already mirrored on github[2], so I will just change
> the README and everything to point to github instead.
>
> The web server can also be hosted on github, but this has still to be
> done and I'm really short on time. Any help would be welcome here. The
> source code of the web pages were already mirrorred on github[3], but
> we should take care of the hosting.
I am happy to work on getting the site running on GitHub pages. One
challenge is that GH pages doesn't support SSL. I believe we have two
options:
1) Use Cloudflare's free service to do this. I am not fully in favor of
this because I feel like it is "fake" SSL because cloudflare pulls from
the non-SSL gh pages.
2) I may be able to get us hosting via Red Hat's Open Source and
Standards Community Cage program. This would be full featured and
probably involve a container (with possible CI interface) running on
OpenShift. It is SSL capable.
Looking at this a bit more I don't think GH pages is an option. We make use of php to
drive some components and I believe GH pages is static content only.
I see two options:
1) Convert to a static system (jekyll, asciibinder, etc.)
2) Use a full featured host ala #2 above.
I'll keep pushing on #2, but I'd like to know if anyone would object to moving to
a static page generator.
regards,
bex
> The most concerning parts are this mailing list, and the issues that
> are reported on alioth.
>
> For the issues, I could not find any tool to move them to github and I
> fear that we would have to it manually. Does someone know such an
> automatic tool or would be willing to do the move? If we have an
> automatic tool, I'd like to move the closed issues also, as they
> contain valuable information. If not I think we should at least copy
> the open issues over. Again, any help would be welcome here.
Between now and Feb 1 I won't have time to do this for sure. Do we
think we can get a dump we could parse to load later?
> For the mailing lists, I have no good idea. Do you? If the list gets
> shut down on Feb 1st as it could, we have the IRC channel to coordinate:
> #po4a on oftc. I have a permanent presence on that channel so it could
> work as a (very) temporarily solution. But someone should come up with
> a better idea, I think.
I may be able to get OSAS to host this mailing list too.
I am emailing them today with the following request:
1) A mailing list
2) A web service supporting SSL
Can you tell me:
a) Who provides our ssl certificate? Lets Encrypt? who?
b) Do we have a domain name? I can probably get one purchased if we
don't. Alternately there is probably a domain name we can get a po4a@/.
on.
Let me know.
regards,
bex
>
> Again, I'm sorry for the short notice, I'm trying to do too much
> things at the same time these days.
>
> Bye, Mt.
>
> [1]
https://wiki.debian.org/Alioth#Deprecation_of_Alioth
> [2]
https://github.com/mquinson/po4a
> [3]
https://github.com/mquinson/po4a-website
>
> --
> Being able to break security doesn’t make you a hacker anymore than
> being able to hotwire cars makes you an automotive engineer.
> -- Eric S. Raymond.
> _______________________________________________
> Po4a-devel mailing list
> Po4a-devel(a)lists.alioth.debian.org
>
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/po4a-devel
> Email had 1 attachment:
> + signature.asc
> 1k (application/pgp-signature)
_______________________________________________
Po4a-devel mailing list
Po4a-devel(a)lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/po4a-devel