> On Feb 11, 2019, at 15:55, azjezz wrote:
>
> if we keep on saying "migration is hard, lets wait" we will never do it.
> the first step would be to create tools that enable us to migrate to MD and
> wait till migration to Git from SVN is finished.
I’m not against migrating the documentation t
Hello,
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, February 9, 2019 10:57 PM, Ben Ramsey wrote:
> > On Feb 9, 2019, at 11:55, azjezz azj...@protonmail.com wrote:
> > Another question i have in mind is, after migrating to GIT, is there any
> > plan to switc
> On Feb 9, 2019, at 11:55, azjezz wrote:
>
> Another question i have in mind is, after migrating to GIT, is there any plan
> to switch to markdown instead of XML ? this would be a really great step for
> the PHP.net website, as we can host the documentation using GitHub Pages
> without having
Hello,
On Sat, 9 Feb 2019 at 18:56, azjezz wrote:
>
> Today i bought a VPS so i can host the mockups for people to see instead of
> just looking at the screenshots.
GitHub pages can do that also fine. And they are simpler to use for
the case of mockups maybe. Only thing is to learn and understa
Hello
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, February 9, 2019 1:48 PM, Peter Kokot wrote:
> Hello,
>
> On Wed, 6 Feb 2019 at 14:17, azjezz azj...@protonmail.com wrote:
>
> > Good afternoon.
> > as some of you may know, i am currently working on a new d
Hello,
On Wed, 6 Feb 2019 at 14:17, azjezz wrote:
>
> Good afternoon.
>
> as some of you may know, i am currently working on a new design for the
> php.net website and i came across the installation page[1].
>
> the page contains information about "how to compile php from source" but no
> "how
Good afternoon.
as some of you may know, i am currently working on a new design for the php.net
website and i came across the installation page[1].
the page contains information about "how to compile php from source" but no
"how to install it" and i think this is not a good for newbies.
when i