Re: [PR] Rename apachecon -> commcode [comdev-events-site]

2024-04-29 Thread via GitHub
rbowen merged PR #15: URL: https://github.com/apache/comdev-events-site/pull/15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Rename apachecon -> commcode [comdev-events-site]

2024-04-29 Thread via GitHub
rbowen opened a new pull request, #15: URL: https://github.com/apache/comdev-events-site/pull/15 Update various links to match the new directory structure that was introduced recently. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] Preview/calendar [comdev-events-site]

2024-04-19 Thread via GitHub
sebbASF merged PR #14: URL: https://github.com/apache/comdev-events-site/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Preview/calendar [comdev-events-site]

2024-04-19 Thread via GitHub
sebbASF opened a new pull request, #14: URL: https://github.com/apache/comdev-events-site/pull/14 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] [#12] Redesign - Styles + Nav [comdev-events-site]

2024-04-10 Thread via GitHub
RedYetiDev commented on PR #13: URL: https://github.com/apache/comdev-events-site/pull/13#issuecomment-2048285000 Seeing as #12 was suggested to be split up into separate PRs, this one has been marked "Ready for Review". -- This is an automated message from the Apache Git Service. To

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-10 Thread via GitHub
RedYetiDev commented on PR #12: URL: https://github.com/apache/comdev-events-site/pull/12#issuecomment-2048283988 Sounds good! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-10 Thread via GitHub
RedYetiDev closed pull request #12: New Design for events.apache.org URL: https://github.com/apache/comdev-events-site/pull/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-10 Thread via GitHub
bdelacretaz commented on PR #12: URL: https://github.com/apache/comdev-events-site/pull/12#issuecomment-2046838024 #13 looks focused on style + nav changes which is good, in terms of being "a single thing". Best might be to close this PR and create another one with the suggested content

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-03 Thread via GitHub
RedYetiDev commented on PR #12: URL: https://github.com/apache/comdev-events-site/pull/12#issuecomment-2034882850 Hey, @bdelacretaz, would you like me to close this and open more similar to #13, or close #13 in favor this (#12)? -- This is an automated message from the Apache Git

[PR] [#12] Redesign - Styles + Nav [comdev-events-site]

2024-04-01 Thread via GitHub
RedYetiDev opened a new pull request, #13: URL: https://github.com/apache/comdev-events-site/pull/13 This Pull Request implements the styling and navbar shown in #12. Please see that pull request for photos and more features. The pull-request is a draft. If ready-for-review, we can

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-01 Thread via GitHub
RedYetiDev commented on PR #12: URL: https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029669946 Okay! Do you want me to split up this PR, or keep that in note for the future? Thank you! -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] New Design for events.apache.org [comdev-events-site]

2024-04-01 Thread via GitHub
bdelacretaz commented on PR #12: URL: https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029602689 This changes many things indeed, in general we prefer having "atomic" PRs which change one thing only and can be reviewed in isolation. I suggest creating separate PRs at

[PR] New Design for events.apache.org [comdev-events-site]

2024-03-30 Thread via GitHub
RedYetiDev opened a new pull request, #12: URL: https://github.com/apache/comdev-events-site/pull/12 In , the following item was listed: 'Keep this events.apache.org [website source code

Re: [PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-27 Thread via GitHub
tisonkun merged PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-27 Thread via GitHub
tisonkun commented on PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#issuecomment-1966949988 @rbowen Different repo I think. The other days before is for comdev-site. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-27 Thread via GitHub
tisonkun commented on code in PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#discussion_r1504555742 ## .asf.yaml: ## @@ -8,6 +8,6 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org -

Re: [PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-27 Thread via GitHub
rlenferink commented on code in PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#discussion_r1504553366 ## .asf.yaml: ## @@ -8,6 +8,6 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org -

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1966782830 I think, eventually, we'd want to move the list of advisors to a separate file, but I don't see that as a blocker to moving forward with this PR. Thanks! -- This is an

Re: [PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen commented on PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#issuecomment-1966625249 Didn't someone already do this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen merged PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen merged PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-27 Thread via GitHub
potiuk commented on PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 If there are no more comments. I'd love to get this one merged and then maybe others (I can do as well) add a bit more why`s for different areas. I think also - when we have a

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-27 Thread via GitHub
potiuk commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1966593319 I hope it's ready for merge -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-27 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1504265776 ## wg-advisors/advisors.md: ## @@ -0,0 +1,14 @@ +Here you will find a list of advisors who signed up to be listed in this repository. + +In order to be

Re: [PR] Add social media todo item [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen merged PR #25: URL: https://github.com/apache/comdev-working-groups/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Add social media todo item [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen opened a new pull request, #25: URL: https://github.com/apache/comdev-working-groups/pull/25 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] working group content [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen merged PR #24: URL: https://github.com/apache/comdev-working-groups/pull/24 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] working group content [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen opened a new pull request, #24: URL: https://github.com/apache/comdev-working-groups/pull/24 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] ToDo list for social media [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen merged PR #23: URL: https://github.com/apache/comdev-working-groups/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] ToDo list for social media [comdev-working-groups]

2024-02-27 Thread via GitHub
rbowen opened a new pull request, #23: URL: https://github.com/apache/comdev-working-groups/pull/23 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-25 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501957585 ## wg-advisors/advisors.md: ## @@ -0,0 +1,14 @@ +Here you will find a list of advisors who signed up to be listed in this repository. + +In order to be

Re: [PR] Add a chapter about "collaborative" aspect of Advisors [comdev-working-groups]

2024-02-25 Thread via GitHub
tisonkun merged PR #20: URL: https://github.com/apache/comdev-working-groups/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] chore: send notification to a separate list [comdev-working-groups]

2024-02-25 Thread via GitHub
tisonkun opened a new pull request, #22: URL: https://github.com/apache/comdev-working-groups/pull/22 A peer to https://github.com/apache/comdev-site/pull/64. I'm thinking of it as the first place (to commits@), but I'm unsure how many people are subscribing to notifications from

Re: [PR] wg-website += curcuru; add pointers and fix typos [comdev-working-groups]

2024-02-25 Thread via GitHub
tisonkun commented on code in PR #21: URL: https://github.com/apache/comdev-working-groups/pull/21#discussion_r1501929933 ## wg-website/README.md: ## @@ -28,12 +28,12 @@ from other mailing list traffic. Anyone with ideas and a willingness to work collaboratively with us is

[PR] wg-website += curcuru; add pointers and fix typos [comdev-working-groups]

2024-02-25 Thread via GitHub
ShaneCurcuru opened a new pull request, #21: URL: https://github.com/apache/comdev-working-groups/pull/21 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Send GitBox notifications to separate list (comdev-site)

2024-02-25 Thread via GitHub
sebbASF merged PR #64: URL: https://github.com/apache/comdev-site/pull/64 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Send GitBox notifications to separate list (comdev-site)

2024-02-25 Thread via GitHub
slawekjaranowski commented on code in PR #64: URL: https://github.com/apache/comdev-site/pull/64#discussion_r1501876112 ## .asf.yaml: ## @@ -29,8 +29,8 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org -

Re: [PR] Send GitBox notifications to separate list (comdev-site)

2024-02-25 Thread via GitHub
slawekjaranowski commented on code in PR #64: URL: https://github.com/apache/comdev-site/pull/64#discussion_r1501875815 ## .asf.yaml: ## @@ -29,8 +29,8 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org -

Re: [PR] Add Maven to Good First Issue list (comdev-site)

2024-02-25 Thread via GitHub
rbowen commented on PR #159: URL: https://github.com/apache/comdev-site/pull/159#issuecomment-1963023504 Thanks!! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Add Maven to Good First Issue list (comdev-site)

2024-02-25 Thread via GitHub
rbowen merged PR #159: URL: https://github.com/apache/comdev-site/pull/159 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Add Maven to Good First Issue list (comdev-site)

2024-02-25 Thread via GitHub
slawekjaranowski commented on code in PR #159: URL: https://github.com/apache/comdev-site/pull/159#discussion_r1501873032 ## source/committers/good-first-issues.md: ## @@ -22,8 +22,9 @@ It's a good idea to put contact information in the ticket, so that someone that ###

[PR] Add Maven to Good First Issue list (comdev-site)

2024-02-25 Thread via GitHub
slawekjaranowski opened a new pull request, #159: URL: https://github.com/apache/comdev-site/pull/159 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962388856 > Inspiring by this simple discussion, I'm taking to try to activate more contributors > > https://lists.apache.org/thread/y1b0x39g3xkh45klmv9ndfj1czcrx4zb > > we

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
slawekjaranowski commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962385814 Inspiring by this simple discussion, I'm taking to try to activate more contributors https://lists.apache.org/thread/y1b0x39g3xkh45klmv9ndfj1czcrx4zb we

Re: [PR] Add a chapter about "collaborative" aspect of Advisors [comdev-working-groups]

2024-02-24 Thread via GitHub
slawekjaranowski commented on PR #20: URL: https://github.com/apache/comdev-working-groups/pull/20#issuecomment-1962335940 > Fingers crossed that we will be able to incentivise enough engaged members and PMCs to make Advisors a useful platformm for this kind of collaboration. Good

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501401856 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501401856 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening

[PR] Add a chapter about "collaborative" aspect of Advisors [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk opened a new pull request, #20: URL: https://github.com/apache/comdev-working-groups/pull/20 Having a - potentially - bigger and engaged group of Advisors that can exchange best practices they learn from the project and have the possibility of shaping best practices that other

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962325653 > Although I'm afraid it's too generic to be a red flag, these are good points. I think one of the good things - assuming we will have a number of advisors advising a

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
slawekjaranowski commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501397552 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1962324323 Ready for the next round of reviews. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501396031 ## wg-advisors/red-flags.md: ## @@ -15,7 +15,7 @@ not a policeman enforcing the rules. * Has a website external to apache.org * Is missing reports * Is

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501395596 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501395470 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1962319343 Ready for the next round of reviews :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388602 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388411 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388274 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501387753 ## wg-advisors/README.md: ## @@ -91,6 +91,13 @@ the indulgence of the PMC, advisor. Do not abuse this relationship. ## FAQ +## How to become an

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501387636 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501378100 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501372589 ## wg-advisors/red-flags.md: ## @@ -15,7 +15,7 @@ not a policeman enforcing the rules. * Has a website external to apache.org * Is missing reports * Is

[PR] Add next examples that discourages to contributions [comdev-working-groups]

2024-02-24 Thread via GitHub
slawekjaranowski opened a new pull request, #19: URL: https://github.com/apache/comdev-working-groups/pull/19 I think such issues related to approving PR and finally prepare next release with accepted contributions can have impact for new contributions. -- This is an automated message

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501372091 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501371159 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501371004 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-24 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501370655 ## wg-advisors/README.md: ## @@ -91,6 +91,13 @@ the indulgence of the PMC, advisor. Do not abuse this relationship. ## FAQ +## How to become an

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501329155 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501328950 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501328880 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501327566 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501327362 ## wg-advisors/README.md: ## @@ -91,6 +91,13 @@ the indulgence of the PMC, advisor. Do not abuse this relationship. ## FAQ +## How to become an

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501326585 ## wg-advisors/red-flags.md: ## @@ -15,7 +15,7 @@ not a policeman enforcing the rules. * Has a website external to apache.org * Is missing reports * Is

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501325628 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501325488 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
justinmclean commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501297317 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
justinmclean commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501296133 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well

Re: [PR] Add Security issues handling as an important use case [comdev-working-groups]

2024-02-23 Thread via GitHub
justinmclean commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1962180930 Projects often need to be pointed in the right direction for the correct process when a security issue arises. I can see an Advisor doing that. -- This is an automated

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501285983 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501228575 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501200329 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501186272 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501174824 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501173776 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1961978300 > Interesting idea. Yeah, I like this. It also gives us something to point to when projects push back, in a "this isn't personal, it's just the way things are" kind of way.

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501154060 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501153331 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501153319 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501152118 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was

[PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk opened a new pull request, #18: URL: https://github.com/apache/comdev-working-groups/pull/18 This PR adds quite a bit of clarity on how the process of initiating (and ending) the relationship between the Advispr and PMC is expected to happen. It's more on a FAQ rather than rules,

Re: [PR] Add bi-directional approach for Advisors [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen merged PR #17: URL: https://github.com/apache/comdev-working-groups/pull/17 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Exclude .idea project to not accidentally commit .idea directory [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen merged PR #15: URL: https://github.com/apache/comdev-working-groups/pull/15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Add bi-directional approach for Advisors [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk opened a new pull request, #17: URL: https://github.com/apache/comdev-working-groups/pull/17 This is something I wanted to proposed from the beginnig of seing the Sharpenes apporach. I believe the original approach where Advisors just advise the projects their join - and the flow is

Re: [PR] Ad Security issues handling as an important use case [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1961924471 > I'm not sure I agree. We have a Security committee, and they are the correct people to handled security issues. I'm not at all sure they want passionate amateurs trying

[PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk opened a new pull request, #16: URL: https://github.com/apache/comdev-working-groups/pull/16 I would like to propose the "why" folder, where we will keep a (very) short summary about some of the rules and policies that we will be - as Advisors - discussing with the projects we will

Re: [PR] Ad Security issues handling as an important use case [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1961883753 I'm not sure I agree. We have a Security committee, and they are the correct people to handled security issues. I'm not at all sure they want passionate amateurs trying to do

Re: [PR] Replace NameTBD with Advisor [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen merged PR #13: URL: https://github.com/apache/comdev-working-groups/pull/13 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Add Jarek as interested in membership [comdev-working-groups]

2024-02-23 Thread via GitHub
rbowen merged PR #12: URL: https://github.com/apache/comdev-working-groups/pull/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Exclude .idea project to not accidentally commit .idea directory [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk opened a new pull request, #15: URL: https://github.com/apache/comdev-working-groups/pull/15 Many of us use different IDEs. I use VIm and IntelliJ interchangeably, for editing markdown files I find IntelliJ rather helpful with preview and Intellij creates .idea folder which can be

[PR] Ad Security issues handling as an important use case [comdev-working-groups]

2024-02-23 Thread via GitHub
potiuk opened a new pull request, #14: URL: https://github.com/apache/comdev-working-groups/pull/14 The security issue handling is an important aspects and one that all projects should have very good policies and processes about, so I think we shoudl add it here. -- This is an automated

  1   2   3   4   5   >