On Fri, May 22, 2020 at 6:23 PM Scott McCarty <smccarty@redhat.com> wrote:
Alvaro and Robert, we have the docs site revamp up and running. I'm quite happy with this foundation.We should discuss how to get a Spanish site going, and revamp the tutorials. I want to bring the rest of them over from GitHub docs to Sphinx. I also want to add two new tutorials which will pull together content from our bunches of blogs:1. Moving from Docker to Podman2. Moving between Podman and KubernetesTotally open to other thoughts too...Best RegardsScott MOn Fri, May 15, 2020 at 4:58 PM Scott McCarty <smccarty@redhat.com> wrote:All,This article got my brain thinking about building out an "architecture" section which has drawings explaining how Podman works with runc, crun, cni, etc. Basically, all of my Linux Internals stuff with some good drawings:Best RegardsScott MOn Fri, May 15, 2020 at 4:15 PM Scott McCarty <smccarty@redhat.com> wrote:Dan,That's because of CORS. I can't fake the production site. That will be fixed in production when it's published.Best RegardsScott MOn Fri, May 15, 2020 at 1:54 PM Daniel Walsh <dwalsh@redhat.com> wrote:_______________________________________________I think it looks good, but the reference block is broken.
On 5/15/20 09:56, Scott McCarty wrote:
Alvaro,Check this out, I have a fork of the upstream libpod going [1], along with a dev site that auto-builds whenever I push a commit [2]. The dev site has some changes baked in which I think are a good base for a PR. I'm still contemplating the right way to do this for all of us that want to contribute to the docs. I need to get a little more ninja with Git so that I can squash all my changes into one commit, then I'm thinking I could start pulling people's changes into my repos then submitting PRs upstream. I don't really like forcing everyone's changes through me, but it has the advantage of using one dev site. Another option is we could a few of us set up our own forks with our own dev sites and we could all submit our changes upstream. To be honest, I'm not sure which is better. I'm totally open to thoughts. Here's my sort of personal todo list:
1. Squash these changes into a single change with on PR2. Start pulling a bunch of our blog content into a single "Moving from Docker to Podman" tutorial for the docs site (this will be our first native Sphinx tutorial on the Read the Docs site)3. Figure out how hard it is to migrate the existing tutorials in GitHub4. Figure out who can give me $50 a month to get rid of the ads :-)5. Other ideas?
Would some people mind beating on my PR and see if everyone thinks it's solid before I submit the PR?
[1]: github repository: https://github.com/fatherlinux/libpod[2]: Development Site: https://libpod.readthedocs.io/en/latest/index.html
Best RegardsScott M
On Tue, May 5, 2020 at 3:43 PM Álvaro Castillo <sincorchetes@gmail.com> wrote:
All right!
You are great! Almost you are spanish people, don't forget dance "flamingo" to get a bonus skill heh.
If you wanna practice with me, maybe we could do a "spanish hour" over riot.me|Discord|Telegram|IRC...
Cheers!
On Tue, May 5, 2020 at 4:21 PM Scott McCarty <smccarty@redhat.com> wrote:
_______________________________________________Álvaro,Que bien! Seria muy genial! Me encantaria ayudarte también. En Septiembre, yo presente en una conferencia que se llama TechZone en Bolivia, y desde entonces tengo un gol de practicar más :-)
También, encontré este video que es muy bien:
CordialmenteScott M
On Mon, May 4, 2020 at 3:51 PM Daniel Walsh <dwalsh@redhat.com> wrote:
_______________________________________________On 5/4/20 15:33, Tom & Susie Sweeney wrote:
Sure and getting the man pages translated would be pretty cool as well.I'll just say that sounds awesome Alvaro!
t
On Mon, May 4, 2020 at 3:30 PM Álvaro Castillo <sincorchetes@gmail.com> wrote:
Hi Scott,
I would llike to translate the documentation when It's okay.
Currently, I'm in translator team of Fedora Project. In Fedora we use Fedora Weblate application to translate a Fedora project webdocs and software applications that's contribute upstream to projects requires to translated.
For example, I finished few days ago, fixed and ended all spanish translation of Cockpit. Today I finished translate cockpit-podman. All this translations will be added in the next release in both software cockpit and cockpit-podman for everybody.
Maybe, would interesting to see how we can translate this information using git repositories and that It's connects to the Fedora Weblate to easily translate.
What do you think?
Cheers!
On Mon, May 4, 2020 at 8:29 PM Scott McCarty <smccarty@redhat.com> wrote:
Avaro/Tom,It's still on my todo list to get that docs site beefed up. I just checked the latest tag and it's the same as the 1.6.4 tag, so that's all we have in the readthedocs site today. That said, I am crushing a RHEL 8.2 blog, then getting my dev site fired up for upstream docs.
Best RegardsScott M
On Sun, May 3, 2020 at 7:55 AM Tom & Susie Sweeney <sweeney@teamalpha.org> wrote:
We need to get that link updated. In the meantime, the tutorials are probably best at: https://github.com/containers/libpod/tree/master/docs/tutorials and in particular: https://github.com/containers/libpod/blob/master/docs/tutorials/podman_tutorial.md
t
_______________________________________________On Sun, May 3, 2020 at 6:33 AM Álvaro Castillo <sincorchetes@gmail.com> wrote:
Hi,_______________________________________________
I want to access to doc of podman but It's does not exist (?)
Cheers!
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
--
--
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
--
--
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
--
--Moving Wordpress, Mediawiki and Request Tracker into containers: http://crunchtools.com/a-hackers-guide-to-moving-linux-services-into-containers/--Scott McCarty Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.comUsing Azure Pipelines with Red Hat Universal Base Image and Quay.io: https://red.ht/2TvYo3Y
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
----Moving Wordpress, Mediawiki and Request Tracker into containers: http://crunchtools.com/a-hackers-guide-to-moving-linux-services-into-containers/--Scott McCarty Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.comUsing Azure Pipelines with Red Hat Universal Base Image and Quay.io: https://red.ht/2TvYo3Y----Moving Wordpress, Mediawiki and Request Tracker into containers: http://crunchtools.com/a-hackers-guide-to-moving-linux-services-into-containers/--Scott McCarty Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.comUsing Azure Pipelines with Red Hat Universal Base Image and Quay.io: https://red.ht/2TvYo3Y----Moving Wordpress, Mediawiki and Request Tracker into containers: http://crunchtools.com/a-hackers-guide-to-moving-linux-services-into-containers/--Scott McCarty Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.comUsing Azure Pipelines with Red Hat Universal Base Image and Quay.io: https://red.ht/2TvYo3Y