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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 changes, assuming they are "a single thing", or several PRs 
if they have distinct goals.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 (A) merge it, or 
(B) merge #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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 least for the content changes vs 
style/behavior/navigation changes, to make the review easier.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 
updated](https://svn.apache.org/repos/asf/concom/site/trunk/content). Possibly 
make it look better.', so I took on the task.
   
   This Pull-Request completely redesigns the website. It's hard to list all 
the changes, but I'll try
   ## Technical
   - Remove `.htaccess` and update links directly
   - Remove `/x/`, as it always redirects to Community Over Code
   - Remove extra unused images
   - Make outgoing links target `_blank`
   - Update copyrights
   - Edit README.md for the newer site
   
   ## Layouts + CSS
   - Replace the navbar with a expanding sidebar
   - Redo the CSS stylings in accordance with the changes to the website
   - Add a 404 page
   
   ## Homepage
   - Remove event listing
   - Rewrite introduction + Table of Contents
   
   ## Events
   - Replace 'past events' and 'upcoming events' with a calendar
   - Switch from native google calendar to fullcalendar
   - Retype introduction to calendar
   
   ## About
   - Added 'The current version of this site was designed by [Aviv Keller 
(@RedYetiDev)](https://github.com/redyetidev)' to 'About This Website' (Credit 
where credit is due)
   - Replace 'apachecon' (404) link with 'Community Over Code'
   - Fix duplicated title in 'Endorsed Events'
   
   ## Community For Code / ApacheCon
   - Fix invalid markdown
   - Reorganize list
   - Remove 'Possibly make it look better.' from volunteer opportunities
   - Fix incorrect twitter URLs
   
   ## Getting Involved
   - Add subheaders to introduction
   - Redesign Mailing List Table
   
   ## And so much more!
   
   ## Screenshots
   
![image](https://github.com/apache/comdev-events-site/assets/38299977/a0ae2c99-f580-43e9-a2de-7a083b549b12)
   
![image](https://github.com/apache/comdev-events-site/assets/38299977/5042d0d3-554f-4e5c-ac79-dae7409c67e7)
   
![image](https://github.com/apache/comdev-events-site/assets/38299977/e5a0720f-f041-466d-9df1-34076008ba3a)
   


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
-  pullrequests: dev@community.apache.org
+  issues:   notificat...@community.apache.org
+  pullrequests: notificat...@community.apache.org

Review Comment:
   ```suggestion
 pullrequests: notificati...@community.apache.org
   ```



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
-  pullrequests: dev@community.apache.org
+  issues:   notificat...@community.apache.org

Review Comment:
   Typo (twice)
   
   ```suggestion
 issues:   notificati...@community.apache.org
   ```



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 few whys we might actually regroup the "red-flags" 
and have them groupped according to the `why` they are referring to - rather 
than link them individually - but taht migh be a refactor of the docs when we 
add 2nd or 3rd why as well.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 listed here, you must be an ASF member. If you are one, you can 
just
+open a PR to add yourself to this list. If you are listed here and you no 
longer want
+to be an advisor, please remove yourself with a PR.
+
+If you want to advise a PMC, please reach out to the PMC and ask if they would 
like to have you as an advisor

Review Comment:
   Updated, squashed and rebased.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 listed here, you must be an ASF member. If you are one, you can 
just
+open a PR to add yourself to this list. If you are listed here and you no 
longer want
+to be an advisor, please remove yourself with a PR.
+
+If you want to advise a PMC, please reach out to the PMC and ask if they would 
like to have you as an advisor

Review Comment:
   Link back to "How to initiate PMC <-> Advisor relationship?".



##
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 listed here, you must be an ASF member. If you are one, you can 
just

Review Comment:
   ```suggestion
   In order to be listed here, [you must be an ASF 
member](README.md#why-a-member). If you are one, you can just
   ```



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 GitHub, so I postponed the action.
   
   But now we have a similar patch at comdev-site so I'd suggest we apply to 
this repo also.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
 welcome to come participate in this effort. Join the 
 [ComDev mailing list], introduce yourself, and tell us what you'd like
-to work on.
+to work on.  If you're already a ComDev regular contributor, then 

Review Comment:
   Maybe we can unify the usage of `'` or `’`.
   
   I personally like `'` but the existing content seems prefer `’`.



##
wg-website/README.md:
##
@@ -6,9 +6,9 @@ website](https://community.apache.org/).
 
 This includes, but is not limited to:
 
-* Long-term maintenance of the site. This involves regular audits, 
implementing metrics, and perhaps other things
+* Long-term maintenance of the ComDev website. This involves regular audits, 
implementing metrics, and perhaps other things
 * Reorg - this is a short-term task that I’ve been just doing on my own, which 
ensures it will never get done, and if it did, there may be some disagreement 
about how I did it.
-* Deduplication - work closely with MarkPub to figure out the *right* place 
for certain information; work through the policy/best-practice dichotomy and 
ensure that we are *not* duplicating policy docs; Work on content on www.a.o 
 that is closely related to content on community.a.o - which 
one is authoritative? Ensure that we don’t duplicate, contradict, or confuse.
+* Deduplication - work closely with [VP, Marketing and 
Publicity](https://www.apache.org/press/) to figure out the *right* place for 
certain information; work through the policy/best-practice dichotomy and ensure 
that we are *not* duplicating policy docs; Work on content on www.a.o 
 that is closely related to content on community.a.o - which 
one is authoritative? Ensure that we don’t duplicate, contradict, or confuse.

Review Comment:
   ```suggestion
   * Deduplication - work closely with [VP, Marketing and 
Publicity](https://www.apache.org/press/) to figure out the *right* place for 
certain information; work through the policy/best-practice dichotomy and ensure 
that we are *not* duplicating policy docs; Work on content on 
[www.a.o](https://www.apache.org) that is closely related to content on 
[community.a.o](https://community.apache.org) - which one is authoritative? 
Ensure that we don’t duplicate, contradict, or confuse.
   ```



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
-  pullrequests: dev@community.apache.org
+  issues:   notificati...@community.apache.org
+  pullrequests: notificati...@community.apache.org

Review Comment:
   dev list should be for humans not for boots  



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
-  pullrequests: dev@community.apache.org
+  issues:   notificati...@community.apache.org
+  pullrequests: notificati...@community.apache.org

Review Comment:
   `notifications` list is present ... can be merged 
   https://lists.apache.org/list.html?notificati...@community.apache.org



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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
 ### Example first issues
 
 Here you can find some Apache projects with "Good First Issues":
-- [Apache Beam](https://github.com/apache/beam/contribute)
 - [Apache Airflow](https://github.com/apache/airflow/contribute)
-- [Apache Superset](https://github.com/apache/superset/contribute)
-- [Apache Iceberg](https://github.com/apache/iceberg/contribute)
+- [Apache Beam](https://github.com/apache/beam/contribute)
 - [Apache 
Cassandra](https://issues.apache.org/jira/browse/CASSANDRA-18868?jql=project%20%3D%20Cassandra%20AND%20(complexity%20%3D%20%22Low%20Hanging%20Fruit%22%20or%20labels%20%3D%20%22lhf%22)%20and%20assignee%20is%20Empty%20and%20status%20not%20in%20(Resolved%2C%20%22In%20Progress%22))
+- [Apache Iceberg](https://github.com/apache/iceberg/contribute)
+- [Apache Maven](https://s.apache.org/for-the-grabs_maven)
+- [Apache Superset](https://github.com/apache/superset/contribute)

Review Comment:
   add and sort  



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 will see what happens 
   
   Cool. For testing the RC - what works for us perfectly is that when we send 
an RC we generat this kind of issue:   
https://github.com/apache/airflow/issues/37648 - all the contributors who 
contributed to the release candidate are `@-mentioned` and invited to test 
their changes, and we have `checkmarks` that the release manager checks when 
someone confirms that a change/fix works as expected - we regularly have 
60%-80% changes tested and verified for pretty much all releases


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 will see what happens  


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 luck from me. 
   Sometime looking from outside on a project can open an eyes for a new ideas.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 on the private list.
 * Users' questions are going unanswered on the mailing list.
+* Users' reported issues are going uncommented and untouched.

Review Comment:
   Example from Airflow: We are using "collaborators" for that (AKA triage 
team) where we ask and encourage people to become members of the team and help 
to triage the issues/PR, we actively "recruit" people to the team (often those 
people become committers or stop being active so it's natural but also  from 
time to time we have a "call for collaborators" - which reminds people that 
there is something like "collaborators" and why.
   
   But it's far from perfect I would love to know how others are doing it :D 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 on the private list.
 * Users' questions are going unanswered on the mailing list.
+* Users' reported issues are going uncommented and untouched.

Review Comment:
   Example from Airflow: We are using "collaborators" for that (aka known as 
triage team) where we ask and encourage people to become members of the team 
and help to triage the issues/PR, we actively "recruit" people to the team 
(often those people become committers or stop being active so it's natural but 
also  from time to time we have a "call for collaborators" - which reminds 
people that there is something like "collaborators" and why.
   
   But it's far from perfect I would love to know how others are doing it :D 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 Advisors will also disseminate among other 
projects, is probably one of the biggest values of a group such as Advisors and 
we should state it explicitly that such collaboration is expected and 
encouraged.
   
   Also this might be one of the important incentives for Advisors to get 
engaged, and for PMCs to ask for Advisors when they know that whatever they do 
with Advisors is not only to apply "top-bottom" rules and principles, but also 
to be able to share their own practices and ideas and variations coming from 
different stages, size, stakeholder engagement they are in - and knowing that 
they can also shape the common understanding and interpretation of the rules 
and principles the ASF is built on.
   
   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.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 number of projects - those might be a great subject to discuss - how 
PMCs are dealing with those? how they dealt with it when things became too 
overwhelming? How they engaged wider community. I think `advisors` is a great 
platform to discuss it and bring those ideas in and disseminate it among other 
PMCs - that's the "Bi-directionality" I added yesterday, but I will also add a 
small chapter about this "platform" thingie.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 happening on the private list.
 * Users' questions are going unanswered on the mailing list.
+* Users' reported issues are going uncommented and untouched.

Review Comment:
   In PMCs like Maven we have many projects which are different and many times 
to do a PR review, comment issues  deeper knowledge is needed in a specific 
project ... but not all commiters good know all projects and so on ... 
   So helping from contributors can be very valuable.
   
   It can be very interesting how others projects deal with such cases ...



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 missing release votes
-* Has too many release candidates
+* Has too many release candidates: [why](why/why_release_process.md)

Review Comment:
   I tried to separate it, but indeed it seems better if it is combined in the 
release process. I just stressed how important it is to engage the dev 
community in the release/testing process and added a little description 
summarising why we are doing it. Should be explained now.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 

Review Comment:
   Added. Also split out the "non-negotiables". 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 
+
+## Are there variations for different projects?
+
+Not really. The process is the same for all projects.

Review Comment:
   I added a short description describing those variations - with the goal to 
make it clearer for both "purposes". I hope it's better now.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
+
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any

Review Comment:
   Yeah. I added a small paragraph stating that Advisor is not the "advised 
PMC" role but a ComDev role.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
+
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
 
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: dev@community.apache.org mailing 
+list to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: the
+dev@community.apache.org mailing list to give the opportunity for
+the interested Advisors to step up and volunteer to help the project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down and remove yourself from being advisor of
+the PMC (TODO: how) You do not need to provide any reason for stepping down,

Review Comment:
   Clarified that a bit - maybe without the example :). but should be pretty 
clear now how to do it.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?

Review Comment:
   I added a paragraph clarifying this, I hope it's ok. I also separated out a 
Board involvement. We've been discussing that with @rbowen a lot on how the 
Board <-> PMC <-> Advisors triangle relation should look like. I **think** I 
captured all the aspects of it in this iteration.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 Advisor?
+
+Just subscribe to dev@community.apache.org and (TODO: how) add yourself

Review Comment:
   Clarified and updated all these points in the new version.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Added a proposal for such a table.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 on the private list.
 * Users' questions are going unanswered on the mailing list.
+* Users' reported issues are going uncommented and untouched.

Review Comment:
   +1 on all of these. I think one of the big advisors roles might be to help 
to figure out how to deal with those oat different stages of the priojects (and 
here I see great opportunity to exchange learnings between projects - and 
advisors talking between themselves about some ideas to improve.
   
   For me - for example it was eye-opening that those do not have to be 
committers to respond - and finding ways to encourage users/contributors to 
respond to each other and review each other's code - also as a way to become a 
committer. 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 missing release votes
-* Has too many release candidates
+* Has too many release candidates: [why](why/why_release_process.md)

Review Comment:
   It's an interesting one. This is precisely the kind of discussions that I 
**hoped** the `why` document will start :)
   
   IMHO that one actually deserves a separate "why", as this red flag is (now 
that you explained it not really about software releases "per se" but about 
communication and process around the releases, and possibly about involving the 
community during the relase process and engaging them in testing  - whcih is a 
subtly different thing and possibly deserves another "why". I wil propose 
something soon :)



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 
+
+## Are there variations for different projects?
+
+Not really. The process is the same for all projects.

Review Comment:
   Yes. Worth mentioning the variations.
   
   But I think going into oo many details is not a good idea. It will be of 
coure always an art how "deep" we should describe it here, but the rule of 
thumb I think such document should not go into details where the linked 
document cover them, it should be a one-pager max and it should mostly focus on 
the most important "why's" - providing a very broad context that is otherwise 
distiributed among several documents, heads of people, discussions etc. etc. 
   
   I think it serves two purposes:
   
   * for the advisor - so that they can always come back here and immediately 
see - hey, why actually we are doing it ?  - a... here it is - and go into 
details if needed
   
   * for the advised ones - to be assured that what we are advising them is not 
a "cargo cult" and tha we have very good reason that you can read about it here 
why we are doing it - without having to go through all the piles of documents 
and discussions or asking others. 
   
   I will expand it a little bit soon.



##
wg-advisors/why/why_release_process.md:
##
@@ -0,0 +1,30 @@
+# Release process
+
+## Summary 
+
+ASF project release software following a well defined process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 

Review Comment:
   Yep. I will add it.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.

Review Comment:
   Good point. 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?

Review Comment:
   Yep. That's how I see it as well (and I think previous paragraphs describe 
it well) - that this is a group of peer ASF members that help other PMCs  and 
gathers information/exchanges knowledge how various PMC are interpreting and 
more importantly "executing" their vision of  "Apache Way" - and advise on 
making it as common as possible where needed **with** the open mind and 
accepting the fact that there are variations among projects.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 Advisor?
+
+Just subscribe to dev@community.apache.org and (TODO: how) add yourself

Review Comment:
   I agree, I think it should be enough to have a member to open a PR with this 
information here - we will keep a list/table of advisors with information. 
   
   It's a public pleace - not guarded by membership access (which is good) so 
no email addresses just maybe name, github id, apache id, and short paragraph 
about the Adviso should be enough,



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
+
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any

Review Comment:
   > become an Advisor
   
   I don't think we'd establish a formal Advisor role in the project. But any 
advisor comes with a certain issue/suggestion, or shout-out (of course) for the 
project.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
+
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)

Review Comment:
   ```suggestion
   start participating in the project's mailing lists (dev and/or private)
   ```
   
   nit



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
+
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
 
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: dev@community.apache.org mailing 
+list to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: the
+dev@community.apache.org mailing list to give the opportunity for
+the interested Advisors to step up and volunteer to help the project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down and remove yourself from being advisor of
+the PMC (TODO: how) You do not need to provide any reason for stepping down,

Review Comment:
   > how
   
   A NOTICE or request on the mailing list (dev@ or private@community should be 
OK IMO). Something like 
https://lists.apache.org/thread/1k116oyo1fc4kk3vdqg6hfz0x1bpxn21.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?

Review Comment:
   According to the original mailing list thread of this WG, it doesn't aim at 
creating a new office in the foundation.
   
   So I assume that there is no special relationship between the Advisor with 
other office at least at the "advising" level.
   
   Instead, the advisor WG working on the guidelines and generating knowledge. 
Every advisor WG member or anyone, as individuals, applying this guidelines to 
advice projects.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 Advisor?
+
+Just subscribe to dev@community.apache.org and (TODO: how) add yourself

Review Comment:
   > how
   
   As stated below that "An Advisor must be an ASF member", I think that add 
oneself to the list can be done with a lazy consensus.
   
   Or if we're confident that the advisor WG is active enough, 3 +1 from the WG.
   
   I personally trust a member and their "describe your experience, skill and 
interests. Introduce yourself as a prospect Advisor" would show enough 
motivation.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 missing release votes
-* Has too many release candidates
+* Has too many release candidates: [why](why/why_release_process.md)

Review Comment:
   The answer is not included in the new file. Do you expect elaborate it in 
the new file later, or we should create a dedicated answer.
   
   I remember that the original purpose of this "red flag" was to encourage RMs 
to waiting for more inputs instead of eagerly cancelling release candidates 
which increases the release burden.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 

Review Comment:
   ```suggestion
   The process is mandatory for all ASF projects. The process is the same for 
all projects.
   ```
   
   Typo.
   
   Also, I agree with Justin's comment that the process can be subtly 
different. Or you can elaborate a bit what "the same" part is that is mandatory.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 
+
+## Are there variations for different projects?
+
+Not really. The process is the same for all projects.

Review Comment:
   > some projects consider the RM as an implicit +1
   
   Here is a patch to explain no RM implicit +1 
https://github.com/apache/www-site/pull/338.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 defined process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.
+
+## Is it mandatory and what are conditions?
+
+The process is mandatory for all ASF projects. The process is the same for all 
projects. This 
+
+## Are there variations for different projects?
+
+Not really. The process is the same for all projects.

Review Comment:
   There is some variation: a few projects use super majority voting, some have 
voters sign releases, the length of time a vote is open often varies, some 
projects consider the RM as an implicit +1, not all projects announce releases, 
and there are probably a few things I've forgotten about.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 defined process involving PMC 
members voting on release
+candidates, publishing the artifacts in the ASF distribution system, and 
announcing the release to the
+community.
+
+## Links to relevant documents
+
+* [Release Policy](https://www.apache.org/dev/release.html) 
+* [Release Distribution 
Policy](https://www.apache.org/dev/release-distribution.html)
+
+## Why are we doing it?
+
+We are doing it because this is what the ASF is doing. ASF delivers "Software 
for the public good"
+and the act of releasing software is a key part of that. The process is 
designed to ensure that the
+software is properly vetted and that the community is aware of the release and 
that the process of
+releasing software is transparent, open and secure. Releasing the software is 
a Legal Act of the 
+Foundation and it has consequences for the Foundation as software released by 
the Foundation is
+the main way the Foundation interacts with the public and can be hold 
accountable for the software
+it releases.

Review Comment:
   I'd note it also gives the PMC and release manager some legal protection.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Something like that - absolutely. Nothong more complex. 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Perhaps, in the spirit of Minimal Viable Solution, a simple alpha-sorted 
list of projects, and the ApacheID of their Advisor, right here in this repo. 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   > Yeah, I like the idea of tracking this -- not least because it might 
discourage multiple Advisors "ganging up" on one project.
   
   Yep. We just need to figure out the most light-weight way of tracking it and 
keeping it up-to-date. It would be useful on many levels to keep track of who 
is an advisor to which project,



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   > Good point. I think maybe we should work out a way to just have a list of 
people who are advisors for PMC? Maybe in this repository ?
   
   Yeah, I like the idea of tracking this -- not least because it might 
discourage multiple Advisors "ganging up" on one project.
   



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Addressed it. Left TODO: on how to add youself as an advisor, but left the 
unsubsribe out.



##
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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Addressed it. Left TODO: on how to add youself as an advisor, but left the 
unsubscribe out.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)

Review Comment:
   I think I addressed it



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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. Especially in conjunction with the notion that we're also 
there to learn, and possibly improve the process/rules.
   
   100% agree. There is a huge value in something being publicly stated in 
"semi-official" way. Just writing things down and pointing to it as a link is 
enough to stop treating things as personal opinion but something that is 
"commonly understood". Also when we connect it with the gorup of advisors who 
are mostly a "group ASF members who actually care enough to spend their 
personal time on helping other projects" has additional benefit that it is not 
seen as something that is "top-> bottom" but more like "group of peers agreed 
this is how it is".


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Good point. I think maybe we should work out a way to just have a list of 
people who are advisors for PMC? Maybe in this repository ? 



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)

Review Comment:
   Fine with that as well. I think having it all on comdev list is great.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)
+to make the advisors aware of such a project (which might also initiate
+a voluntary Advisor to step up and offer their help). In general the PMC
+should be allowed to decide whether they want an Advisor, and who that
+Advisor could bem but if any Advisor is interested in a project, they
+are encouraged to reach out to the PMC and offer their help.
+
+In neither case, the Board is appointing an Advisor. The Board is only
+asking the PMC to consider inviting an Advisor, and cc: advisors mailing
+list to make the advisors aware of such a project.
+
+### How to stop being an Advisor?
+
+You may stop being an Advisor at any time. You should inform the PMC
+that you are stepping down, and then unsubscribe from the private@ list
+and devlist. You do not need to provide any reason for stepping down,

Review Comment:
   Any member can be subscribed to any project's dev@ or private@ list without 
giving justification for doing so. That's actually in the bylaws. We cannot 
mandate that a member unsub from these lists.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 nominated and elected by people that
 you, in turn, nominated and elected.
 
+### How to initiate PMC <-> Advisor relationship?
 
+There is no formal process for this. As an advisor, you may simply
+start participating in the project's mailing lists (dev and private)
+after introducing yourself and asking if this is fine for you to become
+an Advisor. The PMC must be allowed to say "no thank you" without providing any
+reason, and you must respect that decision, and not offer again unless
+invited.
+
+You can also be invited by the PMC to become an Advisor. When you become
+an Advisor, you should sign yourself up to the list of advisors in this
+repository (TODO: how) and describe your experience, skills and what
+you can bring as an Advisor (TODO: how).
+
+The ASF Board can also - during regular Board project review process - to
+identify a project that could benefit from an Advisor, and ask the PMC
+to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the 
list)

Review Comment:
   I am not persuaded that we need a new mailing list for this. I see this WG 
as one of the core functionalities of the ComDev PMC, and moving that 
discussion off to another list seems a way to remove it from view, with no 
particular benefit. I'd ask that we keep it in the main list until such time 
that people actually complain that there's too much noise, since I think we can 
all learn from these discussions.



-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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, and it describes the usual way it can 
happen, with focus put on the voluntary nature of being an Advisor and 
clarifies the role of Board in the process.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 in one direction, they should treat 
the opportunity of interacting with different PMCs as an opportunity to learn 
from the projects and discuss with other advisors whether the current 
incarnation of the rules we have is applicable in practice and whether maybe 
they should be adjusted and improved or maybe they should be updated to be 
better applicable to different projects - coming from various culturs, 
backgrounds, projects with different sizes, with different stakeholder 
engagement.
   
   Having the relation works in both directions is an opportunity to learn and 
adapt, and to exchange findings between the Advisors that might lead to better 
adaptability and better common understanding of the rules and policies we have, 
and more participatory role of both Advisors and PMCs that might get beter 
chance to shape the way how Foundation works on an ongoing way, as well as to 
give the board an opportunity to listen to the voices and better understand the 
varuious needs of various projects.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 to do their job. I would want to have Mark, and 
others on that committee, weigh in on whether they is actually helpful.
   
   Courious about your opinion @raboof @iamamoose  @pjfanning 
   


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 advise.
   
   I think we need something like that - also as a place where we
   - advisors - will be able to update and exchange our understanding on why 
there are certain rules and policies. Also to discuss future variations and 
changes to those rules, possibly resulting from interactions with multiple PMCs 
when we will learn from them how they are applying certain rules and policies 
in their environment.
   
   I gave an example of how I see such "why" captured information could look 
like - starting with the most familiar (for me) release process and I am 
curious what others think about it.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 their job. I would want to have Mark, and others on that 
committee, weigh in on whether they is actually helpful.


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 accidentally added and committed to the 
repository.
   
   Excluding .idea in .gitignore will prevent it from happening `


-- 
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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

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

[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 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: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org