-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create CONTRIBUTING.md #4
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Ian J Mitchell <[email protected]>
I took https://github.com/zowe/docs-site/blob/master/README.md as the starting point on the assumption we aim to adopt the Zowe docs contribution process. I removed the Zowe references and also commented out some of sections - not wanting to remove them entirely as they may become relevant as we mature the process. |
Below is the proposed description for the modernization WG Modernization Definition and First Principles 01-13-23v2.docx |
short def is only app modernization. i do not agree....
…--
Rick Perret
Broadcom Software
mobile: +1 646-248-1277
office: +1 978-983-3848
"To accelerate the speed of delivery beyond the natural power of reception
is to distort experience itself.”
- Stephen Bertman
On Wed, Feb 15, 2023 at 12:04 PM qmangus ***@***.***> wrote:
From our meeting on February 15 there was a discussion on adding a short
definition. Here is the word doc from our discussion.
Modernization.Definition.and.First.Principles.01-13-23v3.docx
<https://github.com/openmainframeproject/wg-modernization/files/10745531/Modernization.Definition.and.First.Principles.01-13-23v3.docx>
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5KORPMOBO6SQBZYMKERWPLWXUECDANCNFSM6AAAAAAT7M6NIE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
|
This is not the correct PR to discuss the definition... please use #6. |
@MistyDecker ... this would be a good candidate for a first review/approval. |
@qmangus , @rpomp - would you be OK if I deleted your comments which are unrelated to this PR? (ie. The three immediately prior to the one I made pointing to the other PR ) |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ian - did I do the review right?
- You can rate the topic at the bottom of each page to tell us whether it is helpful. | ||
- If you have a question about docs, you can join the Zowe [#zowe-doc Slack channel](https://openmainframeproject.slack.com/archives/CC961JYMQ) to reach out to the Zowe Doc Squad and the community. | ||
|
||
Only file issues about Zowe docs in this repository. For issues, questions, new feature requests, or enhancement ideas about a specific component or aspect of Zowe, open an issue in the [corresponding code repository](https://github.com/zowe/community#zowe-sub-projects) or ask in the [community Slack channels](https://github.com/zowe/community#slack). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This process would be different for us, wouldn't it?
--> | ||
## Contributing to the project | ||
|
||
You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. You can make content contributions in your fork, and when the changes are ready, go to your fork and create a new pull request to send the changes to us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want people to Fork in this project?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a public project, I don't think we can deny the possibility of forking.
For more information about contributing to the Zowe documentation, see: | ||
- [Zowe documentation style guide](https://docs.zowe.org/stable/contribute/contributing#documentation-style-guide) | ||
--> | ||
<!-- let's investigate whether we need signoffs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is our signoff process? We should publish it here.
What is a DCO? I don't think that applies here, does it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
--
Rick Perret
Broadcom Software
mobile: +1 646-248-1277
office: +1 978-983-3848
"To accelerate the speed of delivery beyond the natural power of reception
is to distort experience itself.”
- Stephen Bertman
…On Wed, Mar 15, 2023 at 1:20 PM Ian J Mitchell ***@***.***> wrote:
@qmangus <https://github.com/qmangus> , @rpomp <https://github.com/rpomp>
- would you be OK if I deleted your comments which are unrelated to this PR?
(ie. The two immediately prior to the one I made pointing to the other PR
<#4 (comment)>
)
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5KORPKAAFG32X5SPUM7KILW4H27HANCNFSM6AAAAAAT7M6NIE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
|
I made some comments but I'm not sure I did it right. I'm not 100% sure I recognize a comment in this file format. And even if it's just a comment, I would lean towards removing them all together for V1 of our document so that newbs like me don't get confused. :-) Did I do what you need me to? Sorry, I'm still so clueless about this process. |
Comments were fine... I've responded to the ones about the Zowe links. They're in sections which I've commented out for now in anticipation that we would discuss and agree the finer aspects of contribution. |
Signed-off-by: Ian J Mitchell [email protected]