On Thu, Jan 25, 2018, at 2:08 PM, Martin Quinson wrote: 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. 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? 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

On Thu, Jan 25, 2018, at 2:45 PM, Brian Exelbierd wrote: 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

Do we have sponsors who could pay for that? (although it is not exactly the most immediate thing to do for po4a...) Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune

On Thu, Jan 25, 2018 at 11:32:26PM +0900, Jean-Christophe Helary wrote: I am willing to contribute. Not a big deal... Any suggestion on where is better to subscribe the domanin? -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

On Thu, Jan 25, 2018 at 03:51:16PM +0100, Marco Ciampa wrote: Forgot to say that I already have an account on GoDaddy... -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

Hello, On Thu, Jan 25, 2018 at 04:46:58PM +0100, Jean-Baptiste wrote: The new Debian system is salsa.debian.org, which is a specific gitlab deployment. As such, they support web pages but not mailing lists. My idea was to keep the Debian packaging on salsa (it's already setup), but move the upstream project to another hosting solution. Since I'm a (penitent but regular) user of github, that's what I was proposing for the upstream project. We could have picked something else (such as gitlab.org) but I think that hosting the debian packaging and upstream project both on alioth made it difficult to potential contributors to see that it was a distribution-agnostic project, to which they could contribute without being part of the Debian movement. Of course, I may be wrong and other options are still possible. Thanks, Mt. -- What I am really interested in is knowing whether God could have created the world in a different way; in other words, whether the requirement of logical simplicity admits a margin of freedom. -- Albert Einstein, as quoted by Erner Strauss, his assistant.

On Thu, Jan 25, 2018 at 05:20:46PM +0100, Martin Quinson wrote: For the mailing list we can go to freelist... Alternatively, launchpad provides free space for mailing list, bug report, DVS like git, and such as I have already (a little) experience with the KiCad project... -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

On Fri, Jan 26, 2018, at 12:50 AM, Jean-Christophe Helary wrote: I’ve got 12.39 at nfsn. Fedora will support 5-8 years because we value this project. I’d prefer to see us not use GoDaddy solely because I’ve not always cared for their company’s advertising and policies regarding the objectification of women. Should I register this domain? NFSN can also do hosting but it will cost about $5 per year. I believe an alternative was mentioned above. I’m still waiting for a response from Red Hat. That team is at a conference this weekend. Regards, bex

On Sat, Jan 27, 2018 at 05:47:59PM +0100, Brian Exelbierd wrote: Hello Brian, there is definitely no objection on my side. Thanks a lot for arranging this. I will come back to the person you contacted. I certainly hope for others to jump into that van and request the write access to help with the current migration and future maintainance of the project :) Please guys, don't be shy and come help us. This is an open project, after all. Thanks to all, Mt. -- Compatibility means deliberately repeating other people’s mistakes.

On Tue, Jan 30, 2018 at 09:32:14AM +0900, Jean-Christophe Helary wrote: We have to have a space where to put it in. Any suggestion? Buying a little space is not a big issue though. This could be tricky. I suggest to just "snapshot" the issues with something like wget or curl and then re-create the opened issues and preserve the old one as a static block. Issues and list could be created on launchpad. Are there any objections to this? correct. -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

Hi All, On Tue, Jan 30, 2018, at 9:02 AM, Brian Exelbierd wrote: Sorry it took a few extra days. I have uploaded the site to https://www.po4a.org/ This was heavily reliant on the hardwork of Duck, a community sysadmin with Red Hat. I believe the site is working. A linkchecker revealed what appears to be the same broken links as the original site (baby steps). Please beat up on this. I will open a PR with the changes required to get this work. We should consider updating content links as they are ready. Anyone? Anyone? I'll let Duck and Martin chime in here. regards, bex

On Tue, Feb 6, 2018, at 5:39 PM, Martin Quinson wrote: We need a PR/edits to update links to our new source locations on GH, mailing list when, ready, etc. I'd also like someone other than me and a linkchecker to look at the site :) Happy to be added. I'll send you a PR today with what I did to make this work on the new space. I know he was in a conference earlier this week. I believe end of the month is a good timeframe. regards, bex

On Wed, Feb 07, 2018 at 09:04:15PM +0100, Brian Exelbierd wrote: I _want_ to help, (in my _very_ limited capabilities, please be patience) so please add me to whatever list of things to do and to assign you are compiling... You already fixed something ... now the Italian translation of the site is shown correctly (and I do no know why)! :-) Thank you in advance, Best regards -- Marco Ciampa

On Thu, Feb 08, 2018 at 09:17:06AM +0100, Marco Ciampa wrote: If you are looking for something to translate, you should fetch the po file of https://github.com/mquinson/po4a-website update it, and return it either as a PR or directly per private email to me. If you are looking for something to code in Perl, some of the bugs are probably easier to fix (#65, #72 or #73 maybe). I seem to remember that #17 requires shell programming instead of Perl. #7 needs some example files on which we could test the listed feature. You could also go to the translation groups (eg, debian-l10n-it if that's their name) and see if you could help them to fully use po4a. I've no idea of how they handle translations, but maybe they would use someone with some po4a know-how to write the config files and everything. Also, you could try to convince them to take benefit of weblate or some other similar infrastructure. Finally, do not hesitate to report all issue that you could see as an issue on GitHub. Bug reports are really really really helpful. You will see issues that we don't see, and you need to tell us. Even a typo or a borken link on the webpage should be reported. If you know how to program in python, you could try to come up with a prototype of po4a reimplementation. I'm getting the feeling that Perl is not the right choice anymore. But the prototype may be difficult because we use the regular expressions so much. Scala would probably be easier, but I would not say that Scala is a much wiser choice here. I dunno what Scala will become in the next decade (which may be the last decade for Perl). Bye, Mt. -- Il n'y a pas de recherche appliquée, mais des applications de la recherche. -- Louis Pasteur

On Thu, Feb 8, 2018, at 10:06 PM, Martin Quinson wrote: we could use perl6 :P Seriously, I am not sure that changing languages buys us a lot if we don't think through the architecture first. One question I would like to have to explore is "How many of our formats now have canonical or 'really good' processors that we could leverage instead of writing new parsers?" regards, bex

Hello, On Fri, Feb 09, 2018 at 10:04:58AM +0100, Brian Exelbierd wrote: I must confess that I'm rather happy with the current architecture [1]. I still think that it nicely allows to split the generic concerns (dealing with the po file, deciding which files to update, etc) from the format-specific concerns. We could go a bit further over that line, and deal with includes in a generic manner. [1] https://po4a.org/man/man3/Locale::Po4a::TransTractor.3pm.php We may want to change the current code organization of several independent binaries (po4a-gettextize po4a-normalize po4a-translate po4a-updatepo) that are called from po4a. Historically, po4a was created as a layer over the other ones, and retrospectively, I think that a git-like organisation (with subcommands that cannot be accessed directly) would be more adapted. Likewise, po4a-build could be merged back into ... something. But I still like the idea of TransTractors in charge of parsing the structure to both separate the translatable original content that goes to the po file and also inject the translated content in place. It prevents from using existing unmodified parsers (that are never meant to offer that service -- (2)), but this idea makes it really simple to add new formats to the picture. This design still seems clean and lean to me after all these years. In the other projects I'v seen, each formats are handled with a completely specific toolchain with almost no shared concerns. (2) If you have *one* parser (regardless of its language) allowing to separate translatable content from the structure, and that could be used as a library to share generic concerns over several parsers, I'd be really really interested. I don't know any. The thing that I miss the most in the current TransTractor API is that you cannot loop over the languages. That's what you would need to deal with formats where all languages are to be put in the same file, such as Desktop files. That would not be really difficult to implement I guess (po-debconf, a sister project of po4a does so), but I never took the time to do so. What I meant previously is that someone should try to come up with a proof of concept (PoC) of TransTractors in Python, just to see how it would look like. That should not be horrible, I guess. But maybe I'm not fluent enough in Python to preview the difficulties. Sorry for Ruby fans, but I strongly believe that we should stick for the most common programming language to maximize the amount of potential contributors. To rephrase it slightly: do not provide a Ruby PoC if you're not serious about maintaining it in the next 10 years as I'll personnally only commit myself in mainstream solutions for po4a. Bye, Mt. -- It is impossible to find the perfect research tool, in which you have absolutely nothing to adapt for doing your own research. Unless the tool designers scooped you and conducted this very study already. -- Da SimGrid Team