wiki.jenkins.io is now effectively in read-only mode

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

wiki.jenkins.io is now effectively in read-only mode

R. Tyler Croy-2

Our primary wiki has been struggling lately without sufficient or motivation
from anybody in the infrastructure team to fix it or keep it alive. We have
also seen increased spam attacks, which must be pain-stakingly cleaned up.

As a stop-gap measure I have restricted adding pages, comments, and attachments
to administrators. I _believe_ edits will still work by users, but it's only a
matter of time before spammers start defacing plugin pages and things like
that.


Thanks to Oleg (I believe) plugins.jenkins.io can pull README.mds from GitHub
and display those inline. I strongly encourage everybody to consider this
approach for their plugin pages. I don't know how much longer we can keep
Confluence alive.



Please jump into #jenkins-infra on Freenode if you have any questions, or feel
like yelling (praise) at me about this.




Toodles


--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/jIfr-rfo9WizBut_ApNLwBufPREsEQ3qkybbZR9ao9ITNQhi_xeTcwXcQf69xNy7MMc6kKB1du4-sutr6qedHP70Fxnx-4TsNLg0EkX2aFY%3D%40brokenco.de.

signature.asc (858 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Oleg Nenashev
GitHub documentation support is available thanks to Zbynek, I am just facilitating things and helping PRs to land. Anyway, I agree we should consider moving content to GitHub and jenkins.io where possible. 

Some useful links:

* Plugin Documentation (including GitHub): https://jenkins.io/doc/developer/publishing/documentation/

In the Docs SIG we added the docs migration topic to the Hacktoberfest featured projects. We got some pull requests, but not that many so far. If anyone is interested to contribute in this area, please do so!

Best regards,
Oleg 


On Thu, Oct 17, 2019, 02:18 R. Tyler Croy <[hidden email]> wrote:

Our primary wiki has been struggling lately without sufficient or motivation
from anybody in the infrastructure team to fix it or keep it alive. We have
also seen increased spam attacks, which must be pain-stakingly cleaned up.

As a stop-gap measure I have restricted adding pages, comments, and attachments
to administrators. I _believe_ edits will still work by users, but it's only a
matter of time before spammers start defacing plugin pages and things like
that.


Thanks to Oleg (I believe) plugins.jenkins.io can pull README.mds from GitHub
and display those inline. I strongly encourage everybody to consider this
approach for their plugin pages. I don't know how much longer we can keep
Confluence alive.



Please jump into #jenkins-infra on Freenode if you have any questions, or feel
like yelling (praise) at me about this.




Toodles


--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
_______________________________________________
Jenkins-infra mailing list
[hidden email]
http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAfGxEVwHt0Ti4rM8%3Dty%3D8a0ZYhzF4rjYCOdwX-K16zig%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Antonio Muñiz
> I don't know how much longer we can keep Confluence alive.

I've seen some links in jenkins.io still pointing to confluence (ie. https://jenkins.io/doc/developer/views/).
If confluence is going down, those should be migrated, I think.

On Thu, 17 Oct 2019 at 07:36, Oleg Nenashev <[hidden email]> wrote:
GitHub documentation support is available thanks to Zbynek, I am just facilitating things and helping PRs to land. Anyway, I agree we should consider moving content to GitHub and jenkins.io where possible. 

Some useful links:

* Plugin Documentation (including GitHub): https://jenkins.io/doc/developer/publishing/documentation/

In the Docs SIG we added the docs migration topic to the Hacktoberfest featured projects. We got some pull requests, but not that many so far. If anyone is interested to contribute in this area, please do so!

Best regards,
Oleg 


On Thu, Oct 17, 2019, 02:18 R. Tyler Croy <[hidden email]> wrote:

Our primary wiki has been struggling lately without sufficient or motivation
from anybody in the infrastructure team to fix it or keep it alive. We have
also seen increased spam attacks, which must be pain-stakingly cleaned up.

As a stop-gap measure I have restricted adding pages, comments, and attachments
to administrators. I _believe_ edits will still work by users, but it's only a
matter of time before spammers start defacing plugin pages and things like
that.


Thanks to Oleg (I believe) plugins.jenkins.io can pull README.mds from GitHub
and display those inline. I strongly encourage everybody to consider this
approach for their plugin pages. I don't know how much longer we can keep
Confluence alive.



Please jump into #jenkins-infra on Freenode if you have any questions, or feel
like yelling (praise) at me about this.




Toodles


--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
_______________________________________________
Jenkins-infra mailing list
[hidden email]
http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAfGxEVwHt0Ti4rM8%3Dty%3D8a0ZYhzF4rjYCOdwX-K16zig%40mail.gmail.com.


--
Antonio Muñiz
Human, Engineer
CloudBees, Inc.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQNBYrzYUyVjVwxzUxN%2BhS%3DPnVL1ae4_GygXPqtAqmoLw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: wiki.jenkins.io is now effectively in read-only mode

Baptiste MATHUS
In reply to this post by R. Tyler Croy-2


Le jeu. 17 oct. 2019 à 02:18, R. Tyler Croy <[hidden email]> a écrit :

Our primary wiki has been struggling lately without sufficient or motivation
from anybody in the infrastructure team to fix it or keep it alive. We have
also seen increased spam attacks, which must be pain-stakingly cleaned up.

As a stop-gap measure I have restricted adding pages, comments, and attachments
to administrators. I _believe_ edits will still work by users, but it's only a
matter of time before spammers start defacing plugin pages and things like
that

AFAICT, it's not the case even for existing users. I checked and cannot edit my wiki page.

Don't we have a feature in Confluence to add a big warning in top of pages, for people logged in, to point them to this thread or so? 
(more likely a redirect from jenkins.io) so people know why the wiki is RO, even temporarily, and start migrating?

We know many plugin devs do not actively follow the dev list. 



Thanks to Oleg (I believe) plugins.jenkins.io can pull README.mds from GitHub
and display those inline. I strongly encourage everybody to consider this
approach for their plugin pages. I don't know how much longer we can keep
Confluence alive.



Please jump into #jenkins-infra on Freenode if you have any questions, or feel
like yelling (praise) at me about this.

Should we either temporarily re-enable access to edit, or provide a way to access markup code?

Or use services or tools like Pandoc to migrate from the rendered HTML like I've seen Oleg or Daniel recommend off-the-band.
 

Toodles


--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/jIfr-rfo9WizBut_ApNLwBufPREsEQ3qkybbZR9ao9ITNQhi_xeTcwXcQf69xNy7MMc6kKB1du4-sutr6qedHP70Fxnx-4TsNLg0EkX2aFY%3D%40brokenco.de.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6WdML%2Bnt0M9HbNkiyVutL0rKJcz2mFUCSC%3D7T8pjzS2w%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: wiki.jenkins.io is now effectively in read-only mode

Jesse Glick-4
I am all for migrating content from Confluence to GitHub
(`jenkins-infra/jenkins.io`, `jenkinsci/*-plugin`, etc.), but we would
still need write access to Confluence at a minimum to delete the
content from a page and replace it with a note saying where the new
content lives!

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0JcivC2KY9CNk75Z-hWfHvPF-AXi9qevLyQAtJkFHfAQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: wiki.jenkins.io is now effectively in read-only mode

Olblak-2
Don't we have a feature in Confluence to add a big warning in top of pages, for people logged in, to point them to this thread or so? 

I added that warning message

I am all for migrating content from Confluence to GitHub
(`jenkins-infra/jenkins.io`, `jenkinsci/*-plugin`, etc.), but we would
still need write access to Confluence at a minimum to delete the
content from a page and replace it with a note saying where the new
content lives!

Can we just add that information on top of every page, something like "The content of this page is deprecated in favor of plugins.jenkins.io/<the plugin id>"

Olivier

---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---

On Thu, Oct 17, 2019, at 4:02 PM, Jesse Glick wrote:
> I am all for migrating content from Confluence to GitHub
> (`jenkins-infra/jenkins.io`, `jenkinsci/*-plugin`, etc.), but we would
> still need write access to Confluence at a minimum to delete the
> content from a page and replace it with a note saying where the new
> content lives!

> -- 
> You received this message because you are subscribed to the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to [hidden email].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0JcivC2KY9CNk75Z-hWfHvPF-AXi9qevLyQAtJkFHfAQ%40mail.gmail.com.
>

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2155e690-7889-413f-a443-da5b503c629a%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Daniel Beck


> On 17. Oct 2019, at 17:05, Olblak <[hidden email]> wrote:
>
>> Don't we have a feature in Confluence to add a big warning in top of pages, for people logged in, to point them to this thread or so?
>
> I added that warning message

It shows for everyone, but that way it prepares everyone for the eventual (I guess?) shutdown of the wiki.

>
>> I am all for migrating content from Confluence to GitHub
>> (`jenkins-infra/
>> jenkins.io
>> `, `jenkinsci/*-plugin`, etc.), but we would
>> still need write access to Confluence at a minimum to delete the
>> content from a page and replace it with a note saying where the new
>> content lives!
>>
>
> Can we just add that information on top of every page, something like "The content of this page is deprecated in favor of plugins.jenkins.io/<the plugin id>"
>

I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere. The script for that basically exists at https://github.com/jenkins-infra/wiki-maintainers-updater -- grant write access only to that group and you're basically done.

Combined with the giant notice on top (perhaps slightly reworded) it should be clear that this is temporary, and the expectation is for the content to be moved, rather than just edited.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/F195BE53-AE9A-42F9-94D1-EE87D5A22943%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Jesse Glick-4
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Robert Sandell-2
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Tim Jacomb
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicsFkKUJQJb6bdBDK-L2AGmTFKo6oNo_eRwigu1da7%2BTw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Oleg Nenashev
First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">rsan...@...> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jgl...@...>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">m...@...> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees,<a href="http:///" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http:///&#39;;return true;" onclick="this.href=&#39;http:///&#39;;return true;"> Inc.
<a href="http://www.cloudbees.com/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;">CloudBees-Logo.png
E: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">rsan...@...
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mstWqNcuCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Tim Jacomb
Do we have any information on the Wiki pages that get the most hits, that way we could target specific pages to migrate to github / jenkins.io?

A quick google suggests the below, but they may not be enabled:

Thanks
Tim

On Sat, 19 Oct 2019 at 08:53, Oleg Nenashev <[hidden email]> wrote:
First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifxn-4a%2BBdMqDXCLYOqC9jeZQQ2rERhrU0gFKSznyxuPw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Gavin Mogan
In reply to this post by Oleg Nenashev
Last night I started a little web app to make the migration easier for people

https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

I have to incorporate some of the items oleg mentioned in the doc, but its a start.

Gavin


On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <[hidden email]> wrote:
First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvLRZaYL6uh7jwPSGCv8T51YjPXiAst-d%3Dz2GreWOBi%3DA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Oleg Nenashev
Thanks Gavin!

I submitted the pull request for truncating RAW HTML which should improve the layout. More pull requests to come soon. I would suggest hosting this service on jenkinsci or jenkins-infra. I think we can get a lot of contributions. Also, I think we should reserve opportunities to add support of Asciidoc export for jenkins.io and README.adoc later, so probably the final name could be `jenkins-wiki-exporter` or so. 

One of the topics we will need to think about is images. Right now the tool references images from Confluence, which is a bad idea.
I will try to reimplement by guidelines in JS and to add support of ZIP download if you agree, Gavin. It will imply some temporary file magic.

BR, Oleg


On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote:
Last night I started a little web app to make the migration easier for people

<a href="https://jenkins-wiki-md.g4v.dev/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-md.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEus5Lv93qpO_LRquSmj8J3SUN4yw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-md.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEus5Lv93qpO_LRquSmj8J3SUN4yw&#39;;return true;">https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

I have to incorporate some of the items oleg mentioned in the doc, but its a start.

Gavin


On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="XaS-_F-HCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
First version of the plugin Wiki=>GitHub migration guide is available here: <a href="https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fwiki-page%2F%23migrating-from-wiki-to-github\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGJWPWCg6mzIyXIOsRrSLob7a4sdg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fwiki-page%2F%23migrating-from-wiki-to-github\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGJWPWCg6mzIyXIOsRrSLob7a4sdg&#39;;return true;">https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees,<a href="http:///" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http:///&#39;;return true;" onclick="this.href=&#39;http:///&#39;;return true;"> Inc.
<a href="http://www.cloudbees.com/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;">CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="XaS-_F-HCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Gavin Mogan
Thanks for the PR, I've deployed the change, and started to get prepped for straight up markdown, markdown + zip with images, and eventually adoc

I'm totally up for forking it to infra or something, I have no idea how to do that though.

On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev <[hidden email]> wrote:
Thanks Gavin!

I submitted the pull request for truncating RAW HTML which should improve the layout. More pull requests to come soon. I would suggest hosting this service on jenkinsci or jenkins-infra. I think we can get a lot of contributions. Also, I think we should reserve opportunities to add support of Asciidoc export for jenkins.io and README.adoc later, so probably the final name could be `jenkins-wiki-exporter` or so. 

One of the topics we will need to think about is images. Right now the tool references images from Confluence, which is a bad idea.
I will try to reimplement by guidelines in JS and to add support of ZIP download if you agree, Gavin. It will imply some temporary file magic.

BR, Oleg


On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote:
Last night I started a little web app to make the migration easier for people

https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

I have to incorporate some of the items oleg mentioned in the doc, but its a start.

Gavin


On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <[hidden email]> wrote:
First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusbgCosQDvOgQowydQhp-6oZNaqJmdAL3C%3D83BTPWVP5Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Gavin Mogan
Okay~~~

https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown, or a zip of markdown + images

Gavin

On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan <[hidden email]> wrote:
Thanks for the PR, I've deployed the change, and started to get prepped for straight up markdown, markdown + zip with images, and eventually adoc

I'm totally up for forking it to infra or something, I have no idea how to do that though.

On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev <[hidden email]> wrote:
Thanks Gavin!

I submitted the pull request for truncating RAW HTML which should improve the layout. More pull requests to come soon. I would suggest hosting this service on jenkinsci or jenkins-infra. I think we can get a lot of contributions. Also, I think we should reserve opportunities to add support of Asciidoc export for jenkins.io and README.adoc later, so probably the final name could be `jenkins-wiki-exporter` or so. 

One of the topics we will need to think about is images. Right now the tool references images from Confluence, which is a bad idea.
I will try to reimplement by guidelines in JS and to add support of ZIP download if you agree, Gavin. It will imply some temporary file magic.

BR, Oleg


On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote:
Last night I started a little web app to make the migration easier for people

https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

I have to incorporate some of the items oleg mentioned in the doc, but its a start.

Gavin


On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <[hidden email]> wrote:
First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
Later it will be improved once I finish the migration tool on the top of Pandoc

Could use GitHub topics? Or just add to the readme 

Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
Could use GitHub topics? Or just add to the readme 

On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
> I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusEXTw2jgo6Dw1uRD_hpGBEH9njO6RPcvLuzrpbEaEEwA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Gavin Mogan
  • > Asciidoc format can be used as well, with the .adoc extension.

  • I can add that pretty easily

  • > Remove the macro references in the top of the document.

  • Totally done

  • > If the document includes "Table of contents", remove this section in Markdown or replace it by :toc: macros in Asciidoc (example).

    If anyone has an example of that, I can add that

    > If the source Wiki page includes code blocks, they will need to be manually converted. Pandoc exports them as tables.

    I don't think I can automatically handle this, but if anyone has examples I can try things out.


    This tiny little project its starting to get bigger so I probably need to start saving test cases soon


  • On Sun, Oct 20, 2019 at 8:32 PM Gavin Mogan <[hidden email]> wrote:
    Okay~~~

    https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown, or a zip of markdown + images

    Gavin

    On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan <[hidden email]> wrote:
    Thanks for the PR, I've deployed the change, and started to get prepped for straight up markdown, markdown + zip with images, and eventually adoc

    I'm totally up for forking it to infra or something, I have no idea how to do that though.

    On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev <[hidden email]> wrote:
    Thanks Gavin!

    I submitted the pull request for truncating RAW HTML which should improve the layout. More pull requests to come soon. I would suggest hosting this service on jenkinsci or jenkins-infra. I think we can get a lot of contributions. Also, I think we should reserve opportunities to add support of Asciidoc export for jenkins.io and README.adoc later, so probably the final name could be `jenkins-wiki-exporter` or so. 

    One of the topics we will need to think about is images. Right now the tool references images from Confluence, which is a bad idea.
    I will try to reimplement by guidelines in JS and to add support of ZIP download if you agree, Gavin. It will imply some temporary file magic.

    BR, Oleg


    On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote:
    Last night I started a little web app to make the migration easier for people

    https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

    I have to incorporate some of the items oleg mentioned in the doc, but its a start.

    Gavin


    On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <[hidden email]> wrote:
    First version of the plugin Wiki=>GitHub migration guide is available here: https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
    Later it will be improved once I finish the migration tool on the top of Pandoc

    Could use GitHub topics? Or just add to the readme 

    Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to jenkins.io

    On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
    Could use GitHub topics? Or just add to the readme 

    On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
    And how do I mark a plugin as up for adoption without the wiki labels?

    /B

    Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
    On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
    > I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

    Makes sense, but is there some plan to notify maintainers of plugins
    who have not done this? There are a couple thousand pages out there,
    and many people will not see mailing list notifications reliably.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


    --
    Robert Sandell
    Software Engineer
    CloudBees, Inc.
    CloudBees-Logo.png
    Twitter: robert_sandell

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutHHNZGM8r5UOcU26sQdSLy0-JGH26HNFCaLUwiqMkCtg%40mail.gmail.com.
    Reply | Threaded
    Open this post in threaded view
    |

    Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

    Oleg Nenashev
    I have created https://github.com/jenkins-infra/jenkins.io/pull/2589 to document the service usage.
    Also, created few tickets in https://github.com/halkeye/jenkins-wiki-exporter so that we can fix exposrt for some plugins and support non-plugin issues.
    But overall it works great, thanks Gavin!

    Also created https://issues.jenkins-ci.org/browse/INFRA-2297 for hosting in the Jenkins infra.
    I suppose we can use WEBSITE-637 EPIC for all related stories.

    On Monday, October 21, 2019 at 5:42:28 AM UTC+2, Gavin Mogan wrote:
  • > Asciidoc format can be used as well, with the .adoc extension.

  • I can add that pretty easily

  • > Remove the macro references in the top of the document.

  • Totally done

  • > If the document includes "Table of contents", remove this section in Markdown or replace it by :toc: macros in Asciidoc (<a href="https://raw.githubusercontent.com/jenkinsci/.github/master/.github/release-drafter.adoc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fraw.githubusercontent.com%2Fjenkinsci%2F.github%2Fmaster%2F.github%2Frelease-drafter.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGYwJP-P8hWth4Ds9YC5X-WQXbVFA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fraw.githubusercontent.com%2Fjenkinsci%2F.github%2Fmaster%2F.github%2Frelease-drafter.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGYwJP-P8hWth4Ds9YC5X-WQXbVFA&#39;;return true;">example).

    If anyone has an example of that, I can add that

    > If the source Wiki page includes code blocks, they will need to be manually converted. Pandoc exports them as tables.

    I don't think I can automatically handle this, but if anyone has examples I can try things out.


    This tiny little project its starting to get bigger so I probably need to start saving test cases soon


  • On Sun, Oct 20, 2019 at 8:32 PM Gavin Mogan <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="gpJWH3_vCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ga...@...> wrote:
    Okay~~~

    <a href="https://jenkins-wiki-exporter.g4v.dev/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-exporter.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3jcau8giZyqrdXrI4ITSpw-N4lA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-exporter.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3jcau8giZyqrdXrI4ITSpw-N4lA&#39;;return true;">https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown, or a zip of markdown + images

    Gavin

    On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="gpJWH3_vCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ga...@...> wrote:
    Thanks for the PR, I've deployed the change, and started to get prepped for straight up markdown, markdown + zip with images, and eventually adoc

    I'm totally up for forking it to infra or something, I have no idea how to do that though.

    On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="gpJWH3_vCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
    Thanks Gavin!

    I submitted the pull request for truncating RAW HTML which should improve the layout. More pull requests to come soon. I would suggest hosting this service on jenkinsci or jenkins-infra. I think we can get a lot of contributions. Also, I think we should reserve opportunities to add support of Asciidoc export for <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io and README.adoc later, so probably the final name could be `jenkins-wiki-exporter` or so. 

    One of the topics we will need to think about is images. Right now the tool references images from Confluence, which is a bad idea.
    I will try to reimplement by guidelines in JS and to add support of ZIP download if you agree, Gavin. It will imply some temporary file magic.

    BR, Oleg


    On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote:
    Last night I started a little web app to make the migration easier for people

    <a href="https://jenkins-wiki-md.g4v.dev/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-md.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEus5Lv93qpO_LRquSmj8J3SUN4yw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-wiki-md.g4v.dev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEus5Lv93qpO_LRquSmj8J3SUN4yw&#39;;return true;">https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean")

    I have to incorporate some of the items oleg mentioned in the doc, but its a start.

    Gavin


    On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <[hidden email]> wrote:
    First version of the plugin Wiki=>GitHub migration guide is available here: <a href="https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fwiki-page%2F%23migrating-from-wiki-to-github\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGJWPWCg6mzIyXIOsRrSLob7a4sdg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fwiki-page%2F%23migrating-from-wiki-to-github\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGJWPWCg6mzIyXIOsRrSLob7a4sdg&#39;;return true;">https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github
    Later it will be improved once I finish the migration tool on the top of Pandoc

    Could use GitHub topics? Or just add to the readme 

    Yes, I agree we should use GitHub topics. I already have a prototype of integration between GitHub topics and  the plugin site, and we can also replace queries on the Wiki page while moving it to <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io

    On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote:
    Could use GitHub topics? Or just add to the readme 

    On Fri, 18 Oct 2019 at 15:24, Robert Sandell <[hidden email]> wrote:
    And how do I mark a plugin as up for adoption without the wiki labels?

    /B

    Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <[hidden email]>:
    On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <[hidden email]> wrote:
    > I propose that we restore write access for plugin maintainers at least for a time, to allow them to clear out wiki pages after migrating the content elsewhere.

    Makes sense, but is there some plan to notify maintainers of plugins
    who have not done this? There are a couple thousand pages out there,
    and many people will not see mailing list notifications reliably.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.


    --
    Robert Sandell
    Software Engineer
    CloudBees,<a href="http:///" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http:///&#39;;return true;" onclick="this.href=&#39;http:///&#39;;return true;"> Inc.
    <a href="http://www.cloudbees.com/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;">CloudBees-Logo.png
    Twitter: robert_sandell

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="gpJWH3_vCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
    To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ebad216e-1929-4e6a-a024-9dea576d6a12%40googlegroups.com.
    Reply | Threaded
    Open this post in threaded view
    |

    Re: wiki.jenkins.io is now effectively in read-only mode

    Damian Szczepanik
    In reply to this post by Baptiste MATHUS

    Should we either temporarily re-enable access to edit, or provide a way to access markup code?

    Can we use daniel-beck-bot to update each repo with proper <url> to github page as described https://jenkins.io/doc/developer/publishing/documentation/ ? That way we easily inform developers that documentation should be migrated.

    How about installations stats - would it be possible to have trends put on the github README file? For example my new plugin does not have it https://plugins.jenkins.io/build-history-manager and I don't know if this is plugin problem or result of RO state.

    Damian

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7032ad87-2e91-4c9b-b0c6-ce958cb2d8fc%40googlegroups.com.
    Reply | Threaded
    Open this post in threaded view
    |

    Re: wiki.jenkins.io is now effectively in read-only mode

    Gavin Mogan-2

    > Can we use daniel-beck-bot to update each repo with proper <url> to github page as described https://jenkins.io/doc/developer/publishing/documentation/ ? That way we easily inform developers that documentation should be migrated.

    <url> is only processed from the released metadata, so updating github doesn't really help that much. Plus in theory they should also update README.md

    I would like to see this automated, but I think we need more discovery first.
    On Fri, Oct 25, 2019 at 2:11 PM Damian Szczepanik <[hidden email]> wrote:

    Should we either temporarily re-enable access to edit, or provide a way to access markup code?

    Can we use daniel-beck-bot to update each repo with proper <url> to github page as described https://jenkins.io/doc/developer/publishing/documentation/ ? That way we easily inform developers that documentation should be migrated.

    How about installations stats - would it be possible to have trends put on the github README file? For example my new plugin does not have it https://plugins.jenkins.io/build-history-manager and I don't know if this is plugin problem or result of RO state.

    Damian

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7032ad87-2e91-4c9b-b0c6-ce958cb2d8fc%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
    To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAgr96%2BZh_t-O%2BEO4t4z0e3U6S5RQrwWhCCc_wzCUenQXnAMOA%40mail.gmail.com.
    12