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 (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  > 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 > > 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 >> > 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  
> 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  
>>> 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 <
 jgl...@cloudbees.com>:

> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  
> 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 

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

['Gavin Mogan' via Jenkins Developers]

-

> 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  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  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 
>> 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 
 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 
>> 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 <
>>> jgl...@cloudbees.com>:
>>>
 On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck 
 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 jenkin...@googlegroups.com.
 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.
>>> [image: CloudBees-Logo.png] 
>>> E: rsan...@cloudbees.com
>>> 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,
>>> 

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

['Gavin Mogan' via Jenkins Developers]

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  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 
> 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 
>>> 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 
> 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 > >:
>>
>>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck 
>>> 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 jenkin...@googlegroups.com.
>>> 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.
>> [image: CloudBees-Logo.png] 
>> E: rsan...@cloudbees.com
>> 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 jenkin...@googlegroups.com.
>> 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 jenkin...@googlegroups.com.
 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 

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

['Gavin Mogan' via Jenkins Developers]

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 
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 
>> 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 
 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  >:
>
>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkin...@googlegroups.com.
>> 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.
> [image: CloudBees-Logo.png] 
> E: rsan...@cloudbees.com
> 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 jenkin...@googlegroups.com.
> 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 jenkin...@googlegroups.com.
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

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
>
> 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  > 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  
>>> 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 :

> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkin...@googlegroups.com.
> 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.
 [image: CloudBees-Logo.png] 
 E: rsan...@cloudbees.com
 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 jenkin...@googlegroups.com.
 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 jenkin...@googlegroups.com .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com.

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

['Gavin Mogan' via Jenkins Developers]

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 
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 
>> 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 :
>>>
 On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkin...@googlegroups.com.
 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.
>>> [image: CloudBees-Logo.png] 
>>> E: rsan...@cloudbees.com
>>> 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 jenkin...@googlegroups.com.
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
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.

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:
https://confluence.atlassian.com/confeval/confluence-evaluator-resources/confluence-analytics-statistics
https://confluence.atlassian.com/confkb/how-do-i-get-more-statistics-from-confluence-154239308.html

Thanks
Tim

On Sat, 19 Oct 2019 at 08:53, Oleg Nenashev  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 
>> 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 :
>>>
 On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkin...@googlegroups.com.
 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.
>>> [image: CloudBees-Logo.png] 
>>> E: rsan...@cloudbees.com
>>> 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 jenkin...@googlegroups.com.
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifxn-4a%2BBdMqDXCLYOqC9jeZQQ2rERhrU0gFKSznyxuPw%40mail.gmail.com.

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  > 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 > >:
>>
>>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck >> > 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 jenkin...@googlegroups.com .
>>> 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.
>> [image: CloudBees-Logo.png] 
>> E: rsan...@cloudbees.com 
>> 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 jenkin...@googlegroups.com .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com.

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  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 :
>
>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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.
> [image: CloudBees-Logo.png] 
> E: rsand...@cloudbees.com
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicsFkKUJQJb6bdBDK-L2AGmTFKo6oNo_eRwigu1da7%2BTw%40mail.gmail.com.

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

[Robert Sandell]

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 :

> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

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

[Jesse Glick]

On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  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 jenkinsci-dev+unsubscr...@googlegroups.com.
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.

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

[Daniel Beck]

> On 17. Oct 2019, at 17:05, Olblak  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/ 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/F195BE53-AE9A-42F9-94D1-EE87D5A22943%40beckweb.net.

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  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/
> * Migrating non-plugin doc pages from Wiki to jenkins.io:
> https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki
>
> 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  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
>> jenkins-in...@lists.jenkins-ci.org
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQNBYrzYUyVjVwxzUxN%2BhS%3DPnVL1ae4_GygXPqtAqmoLw%40mail.gmail.com.

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/
* Migrating non-plugin doc pages from Wiki to jenkins.io:
https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki

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  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
> jenkins-in...@lists.jenkins-ci.org
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAfGxEVwHt0Ti4rM8%3Dty%3D8a0ZYhzF4rjYCOdwX-K16zig%40mail.gmail.com.