vNext

[Radka Janekova]

Hi there,
please let me know before you plan to deploy next one, I have some changes.

Regards,
Radka

------------------------------
*Radka Janeková*
.NET & OpenShift Engineer, Red Hat
*[e-mail] *
IRC: radka | Freenode: Rhea

[Brian Exelbierd]

On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
> Hi there,
> please let me know before you plan to deploy next one, I have some
> changes.

On a related note, do we want to consider moving this to the new docs
publishing engine so it is less of a hassle to get built/maintained?
That would reduce the commiter needs to accepting patches (mostly).  It
may require a bit of a rethink on the design though.
regards,

bex

[Pavel Valena]

----- Original Message -----
> From: "Brian Exelbierd" 
> To: [e-mail]
> Sent: Friday, October 20, 2017 10:54:44 AM
> Subject: [Developer-portal] Re: vNext
>
> On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
>
> Hi there,
> please let me know before you plan to deploy next one, I have some changes.

Hello,
please submit the changes before Thu 26/10 EOD.
(Thought: would it be possible to include mostly 'stable' content? E.g. that spans at least two releases. I do not consider this news-website. Fixes are however to be made:).)
> On a related note, do we want to consider moving this to the new docs
> publishing engine so it is less of a hassle to get built/maintained? That
> would reduce the commiter needs to accepting patches (mostly). It may
> require a bit of a rethink on the design though.

Bex, can you please point me to the 'engine' info, sources, example code?

Who would do the porting/maintenance? I think most of the time I spend on this is reviewing the commits/actual content, not building/releasing. Having automated OpenShift builds for PRs(or local), which is what I've planned, would put a bit ease the contributions IMHO. Apart from that, it's just a Markdown with simple YAML headers.

Pavel

PS: I find it a bit funny, to use docs engine, as we specifically avoid accepting(or forbid) any documentation-type content.
http://developer-portal.github.io/contributing/write-introduction.html
> regards,
>
> bex

[Brian Exelbierd]

On Fri, Oct 20, 2017, at 11:43 AM, Pavel Valena wrote:
> ----- Original Message -----
> > From: "Brian Exelbierd" 
> > To: [e-mail]
> > Sent: Friday, October 20, 2017 10:54:44 AM
> > Subject: [Developer-portal] Re: vNext
> >
> > On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
> >
> > Hi there,
> > please let me know before you plan to deploy next one, I have some changes.
>
> Hello,
> please submit the changes before Thu 26/10 EOD.
> (Thought: would it be possible to include mostly 'stable' content? E.g.
> that spans at least two releases. I do not consider this news-website.
> Fixes are however to be made:).)
> > On a related note, do we want to consider moving this to the new docs
> > publishing engine so it is less of a hassle to get built/maintained? That
> > would reduce the commiter needs to accepting patches (mostly). It may
> > require a bit of a rethink on the design though.
>
> Bex, can you please point me to the 'engine' info, sources, example code?

We are using asciibinder.  See docs.fedoraproject.org for output.  We
are going to be adding some non-docs content to that site soon.

A code example can be found in the Release Notes
(https://pagure.io/fedora-docs/release-notes/tree/master) or in the
OpenShift upstream docs.

Today this would be shifting from Markdown to Asciidoc.  There is a
pending proposal to add Markdown support to asciibinder.

I did a sample conversion (content only no theming) here:
https://bex.fedorapeople.org/devportal/latest/sw/web-app/apache.html --
note a few links are broken.

This site should still be able to live on it's own or as an alias into
the docs site (which is becoming more than just "documentation").
> Who would do the porting/maintenance? I think most of the time I spend on
> this is reviewing the commits/actual content, not building/releasing.
> Having automated OpenShift builds for PRs(or local), which is what I've
> planned, would put a bit ease the contributions IMHO. Apart from that,
> it's just a Markdown with simple YAML headers.

Porting would need to be shared (see above).  Maintenance of the engine
will be done via the docs project and fedora infrastructure.

There is no requirement that you make this change, obviously.  I have
been waiting on a Fedora Openshift space to launch so we can host this
in there and get Infra more involved in maintenance.  I suggest you
consider doing the same no matter what you choose.
> PS: I find it a bit funny, to use docs engine, as we specifically avoid
> accepting(or forbid) any documentation-type content.
> http://developer-portal.github.io/contributing/write-introduction.html

I guess it is good we want more than just "docs" on the docs site :)

regards,

bex

[Radka Janekova]

> Hello,
> please submit the changes before Thu 26/10 EOD.
> (Thought: would it be possible to include mostly 'stable' content? E.g.

that spans at least two releases. I do not consider this news-website.
Fixes are however to be made:).)

I understand that but I can't predict the development. The issue is not
gonna be resolved upstream anytime soon (months) which is why it had to be
mentioned, but our awesome engineers have hacked it for Fedora and it's
fixed (hacked) on our side so it's now irrelevant and after I check with
them I will probably remove the mention of the bug from the portal.

Radka

------------------------------
*Radka Janeková*
.NET & OpenShift Engineer, Red Hat
*[e-mail] *
IRC: radka | Freenode: Rhea

On Fri, Oct 20, 2017 at 11:43 AM, Pavel Valena  wrote:
> ----- Original Message -----
> > From: "Brian Exelbierd" 
> > To: [e-mail]
> > Sent: Friday, October 20, 2017 10:54:44 AM
> > Subject: [Developer-portal] Re: vNext
> >
> > On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
> >
> > Hi there,
> > please let me know before you plan to deploy next one, I have some
>
> changes.
>
> Hello,
> please submit the changes before Thu 26/10 EOD.
> (Thought: would it be possible to include mostly 'stable' content? E.g.
> that spans at least two releases. I do not consider this news-website.
> Fixes are however to be made:).)
> > On a related note, do we want to consider moving this to the new docs
> > publishing engine so it is less of a hassle to get built/maintained? That
> > would reduce the commiter needs to accepting patches (mostly). It may
> > require a bit of a rethink on the design though.
>
> Bex, can you please point me to the 'engine' info, sources, example code?
>
> Who would do the porting/maintenance? I think most of the time I spend on
> this is reviewing the commits/actual content, not building/releasing.
> Having automated OpenShift builds for PRs(or local), which is what I've
> planned, would put a bit ease the contributions IMHO. Apart from that, it's
> just a Markdown with simple YAML headers.
>
> Pavel
>
> PS: I find it a bit funny, to use docs engine, as we specifically avoid
> accepting(or forbid) any documentation-type content.
> http://developer-portal.github.io/contributing/write-introduction.html
> > regards,
> >
> > bex

[Pavel Valena]

----- Original Message -----
> From: "Radka Janekova" 
> To: "Pavel Valena" 
> Cc: "Brian Exelbierd" , [e-mail]
> Sent: Friday, October 20, 2017 12:34:10 PM
> Subject: [Developer-portal] Re: vNext
> > Hello,
> > please submit the changes before Thu 26/10 EOD.
> > (Thought: would it be possible to include mostly 'stable' content? E.g.
> > that spans at least two releases. I do not consider this news-website.
> > Fixes are however to be made:).)
>
> I understand that but I can't predict the development. The issue is not gonna
> be resolved upstream anytime soon (months) which is why it had to be
> mentioned, but our awesome engineers have hacked it for Fedora and it's
> fixed (hacked) on our side so it's now irrelevant and after I check with
> them I will probably remove the mention of the bug from the portal.

I'm glad to hear that!
From my POV removing a sentence or changing/adding any tiny bit counts as a fix and is fine and welcome anytime :)

Thanks,

Pavel
> Radka
>
> Radka Janeková
> .NET & OpenShift Engineer, Red Hat
> [e-mail]
> IRC: radka | Freenode: Rhea
>
> On Fri, Oct 20, 2017 at 11:43 AM, Pavel Valena < [e-mail] > wrote:
>
> ----- Original Message -----
> > From: "Brian Exelbierd" < [e-mail] >
> > To: [e-mail]
> > Sent: Friday, October 20, 2017 10:54:44 AM
> > Subject: [Developer-portal] Re: vNext
> >
> > On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
> >
> > Hi there,
> > please let me know before you plan to deploy next one, I have some changes.
>
> Hello,
> please submit the changes before Thu 26/10 EOD.
> (Thought: would it be possible to include mostly 'stable' content? E.g. that
> spans at least two releases. I do not consider this news-website. Fixes are
> however to be made:).)
> > On a related note, do we want to consider moving this to the new docs
> > publishing engine so it is less of a hassle to get built/maintained? That
> > would reduce the commiter needs to accepting patches (mostly). It may
> > require a bit of a rethink on the design though.
>
> Bex, can you please point me to the 'engine' info, sources, example code?
>
> Who would do the porting/maintenance? I think most of the time I spend on
> this is reviewing the commits/actual content, not building/releasing. Having
> automated OpenShift builds for PRs(or local), which is what I've planned,
> would put a bit ease the contributions IMHO. Apart from that, it's just a
> Markdown with simple YAML headers.
>
> Pavel
>
> PS: I find it a bit funny, to use docs engine, as we specifically avoid
> accepting(or forbid) any documentation-type content.
> http://developer-portal.github.io/contributing/write-introduction.html
> > regards,
> >
> > bex