Join the copy editors - help the docs

[Mark Waite]

The Jenkins documentation is written and reviewed by volunteers through the https://github.com/jenkins-infra/jenkins.io repository on GitHub.

Pull request reviews are automatically requested of the copy-editors team.

We need more members in the copy-editors team.  Instructions for becoming a member of the copy-editors team are listed in the contributing file.  The steps include:

• Be a Jenkins contributor (code, documentation, mailing lists, gitter channels, etc.)
• Submit a Contributor License Agreement
• Send a request to the Jenkins Developers mailing list to become a copy editor

We'd love to have your help!

Thanks,

Mark Waite

[Tim Jacomb]

Hi 

I would be happy to join the team 

Thanks

Tim

--
You received this message because you are subscribed to the Google Groups "Jenkins Documentation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-doc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/42cc67ff-c4c8-4eb2-92a8-71bac80514f0%40googlegroups.com.

[Sladyn Nunes]

Hey,

I would love to be a part of the team.

[Vlad Silverman]

It looks I don't have access to copy-editors team.
Pls let me know if I can help

Thx, Vlad

[Mark Waite]

Yes, I still need to be granted permission to manage that group.  I also need to create a new group that will have review permission without having merge permission.  That will give us a two stage approach to including new reviewers.  I'd like to use a similar permission set as are used in the Jenkins core repository.  I'll check with the administrator of that repository tomorrow.

--

You received this message because you are subscribed to the Google Groups "Jenkins Documentation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-doc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/210f6995-b5af-4745-aac9-3b7a5d92524e%40googlegroups.com.

[Mark Waite]

I now have administrator permissions to the jenkins.io repository.  

I've also learned that there is a better way to approach the additional help that we need.  I'll add a new group that has triage permission so that the new reviewers can review, close, and reopen pull requests but cannot merge them.  I'll let you know when that group is created and you've been added to the group.  Thanks for your willingness to help!

[Oleg Nenashev]

Hi Mark,

Please let me know if I could somehow help to get this story over the line.

If we agree on the triage team, I could write up short team documentation similar to the Jenkins Core maintainer guide and to create the team.

Best regards,

Oleg

On Friday, April 24, 2020 at 2:29:42 AM UTC+2, Mark Waite wrote:

I now have administrator permissions to the jenkins.io repository.  

I've also learned that there is a better way to approach the additional help that we need.  I'll add a new group that has triage permission so that the new reviewers can review, close, and reopen pull requests but cannot merge them.  I'll let you know when that group is created and you've been added to the group.  Thanks for your willingness to help!

On Tue, Apr 21, 2020 at 3:20 PM Mark Waite <mark.e...@gmail.com> wrote:

Yes, I still need to be granted permission to manage that group.  I also need to create a new group that will have review permission without having merge permission.  That will give us a two stage approach to including new reviewers.  I'd like to use a similar permission set as are used in the Jenkins core repository.  I'll check with the administrator of that repository tomorrow.

On Tue, Apr 21, 2020 at 2:18 PM Vlad Silverman <vsilv...@gmail.com> wrote:

It looks I don't have access to copy-editors team.
Pls let me know if I can help

Thx, Vlad

On Thursday, April 16, 2020 at 2:14:35 PM UTC-7, Mark Waite wrote:

The Jenkins documentation is written and reviewed by volunteers through the https://github.com/jenkins-infra/jenkins.io repository on GitHub.

Pull request reviews are automatically requested of the copy-editors team.

We need more members in the copy-editors team.  Instructions for becoming a member of the copy-editors team are listed in the contributing file.  The steps include:

• Be a Jenkins contributor (code, documentation, mailing lists, gitter channels, etc.)
• Submit a Contributor License Agreement
• Send a request to the Jenkins Developers mailing list to become a copy editor

We'd love to have your help!

Thanks,

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Documentation" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkins...@googlegroups.com.

[Mark Waite]

Thanks Oleg!  That would be great.

I think we need to add Vlad and Sladyn to a new group defined with Triage permission on the jenkins.io repository.  I assume we'll want a group name that is consistent with the group name that is used for the Core Pull Request Reviewer role on Jenkins core.  That will allow them to triage and close issues and manage pull requests.  We're seeing an increase of reports

They will review GitHub issues reported on the jenkins.io repository, confirm the issues are clearly described and understood and can be duplicated.  They will review and comment on pull requests, applying labels in those cases where the automatic labeling may be insufficient (like those cases where 'on-hold' and 'squash-merge-me' are needed).

The group is calling "core-pr-reviewers" for Jenkins core.  Would this group be "docs-pr-reviewers" or something else?

Mark Waite

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-doc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/1ae625a9-e91d-4c58-8a08-9005b0554786%40googlegroups.com.

[Oleg Nenashev]

Thanks Mark! I will do it

I created the team (@jenkins-infra/jenkins-io-triage), obstacles

• Sladyn and Vlad need to be added to the organization, I have no permissions to do that
• Triage permission is not enabled in jenkins-infra. Contacted the team again

Will try to write docs today/tomorrow so that we close this topic. Thanks to everyone!

Best regards,

Oleg

On Tuesday, April 28, 2020 at 2:28:07 PM UTC+2, Mark Waite wrote:

Thanks Oleg!  That would be great.

I think we need to add Vlad and Sladyn to a new group defined with Triage permission on the jenkins.io repository.  I assume we'll want a group name that is consistent with the group name that is used for the Core Pull Request Reviewer role on Jenkins core.  That will allow them to triage and close issues and manage pull requests.  We're seeing an increase of reports

They will review GitHub issues reported on the jenkins.io repository, confirm the issues are clearly described and understood and can be duplicated.  They will review and comment on pull requests, applying labels in those cases where the automatic labeling may be insufficient (like those cases where 'on-hold' and 'squash-merge-me' are needed).

The group is calling "core-pr-reviewers" for Jenkins core.  Would this group be "docs-pr-reviewers" or something else?

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/1ae625a9-e91d-4c58-8a08-9005b0554786%40googlegroups.com.

[Sladyn Nunes]

Hello,

Thanks for inviting me to the team, looking forward to helping the community.

Thanks and cheers 

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-doc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/e3f88d2f-7709-44dd-91aa-bcdcee11c3cd%40googlegroups.com.

[Lalith Kumar]

Hello guys,

I am new into this Jenkins CICD pipeline. I am good in conceptual and workflows. Would you guys share your scenarios and common issues that we face on CICD pipeline day by day. That should help me getting a deep insight. 

Regards, 

Lalith

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-doc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/1ae625a9-e91d-4c58-8a08-9005b0554786%40googlegroups.com.

[Mark Waite]

Lalith,

This thread is focused on increasing the number of people that are helping with the Jenkins documentation.  Your question is not related to the topic of the thread.  Please refer to the Jenkins tutorials, the Jenkins guided tour, the Jenkins pipeline documentation, and the many free videos and courses available for Jenkins pipeline.

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/CADjBoSmuJ_O%2Be02nJO5gfmEQzjm7XDnQmx70DxZ6-%3DeykSmztw%40mail.gmail.com.

[Oleg Nenashev]

Quick update:

• The triage team was created on GitHub. Welcome aboard Sladyn and Vlad!
• There is a catch, Triage permission has not been enabled yet, so the team just grants read permissions and allows requesting reviews from members. Triage permission is WiP in https://issues.jenkins-ci.org/browse/INFRA-2596
• I have just created a pull request with the Maintainer guide, reviews will be appreciated: https://github.com/jenkins-infra/jenkins.io/pull/3141

Best regards,

Oleg

On Wednesday, April 29, 2020 at 1:29:32 AM UTC+2, Mark Waite wrote:

Lalith,

This thread is focused on increasing the number of people that are helping with the Jenkins documentation.  Your question is not related to the topic of the thread.  Please refer to the Jenkins tutorials, the Jenkins guided tour, the Jenkins pipeline documentation, and the many free videos and courses available for Jenkins pipeline.

Mark Waite

On Tue, Apr 28, 2020 at 8:15 AM Lalith Kumar <kumar.l...@gmail.com> wrote:

Hello guys,

I am new into this Jenkins CICD pipeline. I am good in conceptual and workflows. Would you guys share your scenarios and common issues that we face on CICD pipeline day by day. That should help me getting a deep insight. 

Regards, 

Lalith

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/1ae625a9-e91d-4c58-8a08-9005b0554786%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Documentation" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkins...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-docs/CADjBoSmuJ_O%2Be02nJO5gfmEQzjm7XDnQmx70DxZ6-%3DeykSmztw%40mail.gmail.com.

[sladyn...@gmail.com]

Hi all, 

Hope everyone is doing well, I was getting back to contributing to the jenkins documentation now that Google summer of code is over and I have more bandwidth. Is this permissions issue resolved or is it still under progress. I can see an issue open but no definite conclusion.

Thanks