Re: [PR] Add "why" for branding and licencing [comdev-working-groups]

[via GitHub]

potiuk commented on PR #43:
URL: 
https://github.com/apache/comdev-working-groups/pull/43#issuecomment-2185309451

   As the next "why" I proposed some "why" for branding/licencing in the 
"advisors" working group. This is my understanding on why licensing and 
branding and taking care about it is the most important thing from the legal 
point of view for all PMC members, but I woudl love to hear 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: notifications-unsubscr...@community.apache.org

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

[PR] Add "why" for branding and licencing [comdev-working-groups]

[via GitHub]

potiuk opened a new pull request, #43:
URL: https://github.com/apache/comdev-working-groups/pull/43

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

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

Re: [PR] Update README.md [comdev-working-groups]

[via GitHub]

clr-apache merged PR #41:
URL: https://github.com/apache/comdev-working-groups/pull/41


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

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

[PR] Update README.md [comdev-working-groups]

[via GitHub]

clr-apache opened a new pull request, #41:
URL: https://github.com/apache/comdev-working-groups/pull/41

   Suggest ways for PMCs/ podlings to adopt their Code of Conduct


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

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

[PR] Update code_of_conduct.md [comdev-working-groups]

[via GitHub]

clr-apache opened a new pull request, #40:
URL: https://github.com/apache/comdev-working-groups/pull/40

   Minor clarifications


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

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

Re: [PR] update status [comdev-working-groups]

[via GitHub]

rbowen merged PR #39:
URL: https://github.com/apache/comdev-working-groups/pull/39


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

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

[PR] update status [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #39:
URL: https://github.com/apache/comdev-working-groups/pull/39

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

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

Re: [PR] Initial code and README [comdev-working-groups]

[via GitHub]

rbowen merged PR #38:
URL: https://github.com/apache/comdev-working-groups/pull/38


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

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

[PR] Initial code and README [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #38:
URL: https://github.com/apache/comdev-working-groups/pull/38

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

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

Re: [PR] Proposal for "Community building" why description [comdev-working-groups]

[via GitHub]

potiuk commented on PR #35:
URL: 
https://github.com/apache/comdev-working-groups/pull/35#issuecomment-2146679421

   Any more comments here ? I've been caught up with other things and have not 
been following up with it, but maybe other peoople interested in getting 
advisors idea to proceed would also like to step-up and join the efforts here. 
I am not in a position of leading the effort and taking the reigns (I am mostly 
focusing on Airflow 3 and Security area, but I really think advisors is a good 
idea and it could be very interesting change for the ASF. 
   
   Maybe someone would like to take a lead on that at the CoC EU ? 


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

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

Re: [PR] Update community-growth.md [comdev-site]

[via GitHub]

Pilot-Pirx commented on PR #182:
URL: https://github.com/apache/comdev-site/pull/182#issuecomment-2145791545

   Hehe, I often feel like Pirx on a test flight... ;-)


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

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

Re: [PR] Update community-growth.md [comdev-site]

[via GitHub]

rbowen commented on PR #182:
URL: https://github.com/apache/comdev-site/pull/182#issuecomment-2144016702

   Thank you! Also, love the username! 


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

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

Re: [PR] Update community-growth.md [comdev-site]

[via GitHub]

rbowen merged PR #182:
URL: https://github.com/apache/comdev-site/pull/182


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

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

[PR] Update community-growth.md [comdev-site]

[via GitHub]

Pilot-Pirx opened a new pull request, #182:
URL: https://github.com/apache/comdev-site/pull/182

   Fixed typo


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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

rbowen merged PR #180:
URL: https://github.com/apache/comdev-site/pull/180


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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

rbowen commented on PR #180:
URL: https://github.com/apache/comdev-site/pull/180#issuecomment-2143738969

   > I think we can implement a plan to modify all current Apache websites, 
improving areas with recognition issues or those that are hard for visually 
impaired individuals to see. What do you think? I feel it's a really cool idea.
   
   This must be run through the M (Marketing and Press) team, and cannot be 
decided here, as that's a global ASF branding question, and not something we 
have the right to address.


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

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

Re: [PR] link to trademark responsibilities site [comdev-site]

[via GitHub]

rbowen merged PR #181:
URL: https://github.com/apache/comdev-site/pull/181


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

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

[PR] link to trademark responsibilities site [comdev-site]

[via GitHub]

rbowen opened a new pull request, #181:
URL: https://github.com/apache/comdev-site/pull/181

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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

clr-apache commented on PR #180:
URL: https://github.com/apache/comdev-site/pull/180#issuecomment-2123085547

   I think it will be good to start with this one. Update all pages to improve 
the experience for everyone? Great follow-on idea.
   
   Craig
   
   > On May 21, 2024, at 06:34, iepn ***@***.***> wrote:
   > 
   > 
   > I think we can implement a plan to modify all current Apache websites, 
improving areas with recognition issues or those that are hard for visually 
impaired individuals to see. What do you think? I feel it's a really cool idea.
   > 
   > —
   > Reply to this email directly, view it on GitHub 
, or 
unsubscribe 
.
   > You are receiving this because you commented.
   > 
   
   Craig L Russell
   ***@***.***
   
   


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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

iepn commented on PR #180:
URL: https://github.com/apache/comdev-site/pull/180#issuecomment-2122653472

   I think we can implement a plan to modify all current Apache websites, 
improving areas with recognition issues or those that are hard for visually 
impaired individuals to see. What do you think? I feel it's a really cool idea.
   


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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

clr-apache commented on PR #180:
URL: https://github.com/apache/comdev-site/pull/180#issuecomment-2122613952

   LGTM.
   Craig
   
   > On May 21, 2024, at 04:44, Rich Bowen ***@***.***> wrote:
   > 
   > 
   > No objections from me. Anyone else have a chance to verify?
   > 
   > —
   > Reply to this email directly, view it on GitHub 
, or 
unsubscribe 
.
   > You are receiving this because you are subscribed to this thread.
   > 
   
   Craig L Russell
   ***@***.***
   
   


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

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

Re: [PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

rbowen commented on PR #180:
URL: https://github.com/apache/comdev-site/pull/180#issuecomment-2122446680

   No objections from me. Anyone else have a chance to verify? 


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

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

[PR] fix: home navbar backgroun error logo invisibility [comdev-site]

[via GitHub]

iepn opened a new pull request, #180:
URL: https://github.com/apache/comdev-site/pull/180

   I'm a colorblind user, and I really want to see the Apache logo clearly 
because it holds great sentimental value for me. This is also my first PR since 
following Apache.
   
   This PR mainly enhances the recognizability of the navbar logo. Below is the 
difference between the two:
   
   ### Error navbar logo
   
   
![afa6adf3177aa57da2d2e1088a6fbe7f](https://github.com/apache/comdev-site/assets/57232813/f20b65fa-7cb1-4555-96f6-4a0d18053b01)
   
   ### New navbar logo
   
   
![d04591f96a8ca592346fa328c1a0d2d1](https://github.com/apache/comdev-site/assets/57232813/94d74a7d-cc6f-4d9d-abfa-c3f92b7a2aa0)
   
   To my surprise, I can now see the Apache logo clearly, including the details 
like "Software Foundation."


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

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

Re: [PR] [GSOC] Added past GSoC program details for year 2023 and 2022 [comdev-site]

[via GitHub]

rbowen merged PR #178:
URL: https://github.com/apache/comdev-site/pull/178


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

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

Re: [PR] Add tison as one of volunteer mentors & speakers [comdev-site]

[via GitHub]

tisonkun merged PR #179:
URL: https://github.com/apache/comdev-site/pull/179


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

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

Re: [PR] Add tison as one of volunteer mentors & speakers [comdev-site]

[via GitHub]

tisonkun commented on PR #179:
URL: https://github.com/apache/comdev-site/pull/179#issuecomment-2109629591

   CTR. Merging ...


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

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

[PR] Add tison as one of volunteer mentors & speakers [comdev-site]

[via GitHub]

tisonkun opened a new pull request, #179:
URL: https://github.com/apache/comdev-site/pull/179

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

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

Re: [PR] [GSOC] Added past GSoC program details for year 2023 and 2022 [comdev-site]

[via GitHub]

priyasharma1 commented on PR #178:
URL: https://github.com/apache/comdev-site/pull/178#issuecomment-2079331517

   This is how the change would look
   
   
![Apache-Community-Development-Apache-in-GSoC](https://github.com/apache/comdev-site/assets/14103632/8b6a1fdf-2ed9-4ab4-a571-7a141ce66505)
   ![Screenshot from 2024-04-26 
18-21-39](https://github.com/apache/comdev-site/assets/14103632/13467d85-b45f-4870-beeb-ff36a8f1a005)


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

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

[PR] [GSOC] Added past GSoC program details for year 2023 and 2022 [comdev-site]

[via GitHub]

priyasharma1 opened a new pull request, #178:
URL: https://github.com/apache/comdev-site/pull/178

   - Create a new folder for experiences only
   - Moved the experiences main file into new folder


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

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

[PR] make the hyphen optional [comdev-site]

[via GitHub]

rbowen opened a new pull request, #177:
URL: https://github.com/apache/comdev-site/pull/177

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

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

Re: [PR] make the hyphen optional [comdev-site]

[via GitHub]

rbowen merged PR #177:
URL: https://github.com/apache/comdev-site/pull/177


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

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

Re: [PR] COMDEV-544 Improve comdev website navigation to GSoC mentor resources [comdev-site]

[via GitHub]

rbowen merged PR #176:
URL: https://github.com/apache/comdev-site/pull/176


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

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

[PR] COMDEV-544 Improve comdev website navigation to GSoC mentor resources [comdev-site]

[via GitHub]

lewismc opened a new pull request, #176:
URL: https://github.com/apache/comdev-site/pull/176

   PR for https://issues.apache.org/jira/browse/COMDEV-544


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

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

[PR] Add Glaucia's email and include in the WG Social Media [comdev-working-groups]

[via GitHub]

glauesppen opened a new pull request, #37:
URL: https://github.com/apache/comdev-working-groups/pull/37

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

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

[PR] Add useful links; suggest coordinating with incubator docs too [comdev-working-groups]

[via GitHub]

ShaneCurcuru opened a new pull request, #36:
URL: https://github.com/apache/comdev-working-groups/pull/36

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

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

[PR] feat: polish breadcrumb to display page title [comdev-site]

[via GitHub]

suyanhanx opened a new pull request, #175:
URL: https://github.com/apache/comdev-site/pull/175

   Signed-off-by: suyanhanx 
   
   I noticed that the breadcrumb on our comdev site is generated by 
capitalizing the first letter of the fragment of the URL.
   This may be wrong some of the time, such as GSoC:
   
![image](https://github.com/apache/comdev-site/assets/24221472/59e48bf0-5fff-498d-a28c-0ad4f8b466e7)
   
   I polished this breadcrumb. 
   
   After:
   
![image](https://github.com/apache/comdev-site/assets/24221472/6132523c-9bfe-4ca6-b0cd-4c9efd3fcb6d)
   
   Now it looks better.


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

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

rbowen merged PR #174:
URL: https://github.com/apache/comdev-site/pull/174


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

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

rbowen commented on PR #174:
URL: https://github.com/apache/comdev-site/pull/174#issuecomment-2032478054

   Merging as a first draft. Please do feel free to make further edits/updates. 
Thanks for the input, friends.
   


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

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

justinmclean commented on code in PR #174:
URL: https://github.com/apache/comdev-site/pull/174#discussion_r1547094290


##
source/pmc/community-growth.md:
##
@@ -0,0 +1,90 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a roadmap
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+It can be very challenging to keep a roadmap current. Having a mechanism
+for tagging open issues with `proposal` or `roadmap` and
+automatimatically extracting that into a web page can help with this.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open
+issues. Sending this to the dev@ list reminds people that there are
+things to work on, and gives them permission, and encouragement, to do
+so.
+
+Consider creating [good first
+issues](/committers/good-first-issues.html) as a place for new
+contributors to get started.
+
+## Clearly document contribution processes
+
+Double-check that your "how to contribute / build / test / submit PR"
+documentation is super clear and easy to follow.  Long-time committers
+on a project often forget all the institutional knowledge they just
+"know", so ensuring the "getting started" document actually works
+for newcomers is always worth looking at.
+
+Encourage newcomers to talk about, and document, their pain points
+during their first contributions, and work towards fixing, or at least
+documenting, those things.
+
+## Publish your contributor ladder
+
+A [contributor ladder](/contributor-ladder.html) is a description of
+various levels of access and responsibility a contributor can progress
+through in your project. This is typically the path from contributor, to
+committer, to PMC member.
+
+Explicitly publish your requirements for each step. For example, if you
+require ten non-trivial patches accepted, or perhaps 3 months of
+involvement, document this on your website so that people don't feel
+that it's random, or that they are driving in the dark.
+
+Consider lowering your bar to entry. Remember that while the risk of
+inviting someone "too early" is that they'll break something, that's why
+you have version control - so you can revert those changes. However, the
+risk of inviting someone too late is that they'll give up and go away
+forever.
+
+## Engage with big users
+
+If you are aware of companies that rely on your project, encourage them
+to think about what they would do if the project retired. This often
+leads to those companies realizing the value they get "for free", and
+starting to contribute in some way.

Review Comment:
   Perhaps also list ways companies to help out by providing in-kind 
contributions e.g. testing infrastructure), developer time or help with 
marketing/website?



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

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

justinmclean commented on code in PR #174:
URL: https://github.com/apache/comdev-site/pull/174#discussion_r1547092975


##
source/pmc/community-growth.md:
##
@@ -0,0 +1,90 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a roadmap
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+It can be very challenging to keep a roadmap current. Having a mechanism
+for tagging open issues with `proposal` or `roadmap` and
+automatimatically extracting that into a web page can help with this.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open
+issues. Sending this to the dev@ list reminds people that there are
+things to work on, and gives them permission, and encouragement, to do
+so.
+
+Consider creating [good first
+issues](/committers/good-first-issues.html) as a place for new
+contributors to get started.

Review Comment:
   GitHub automatically does this for you 
https://github.com/apache/pekko/contribute just substitute pekko for any Apache 
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: notifications-unsubscr...@community.apache.org

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

justinmclean commented on code in PR #174:
URL: https://github.com/apache/comdev-site/pull/174#discussion_r1547092975


##
source/pmc/community-growth.md:
##
@@ -0,0 +1,90 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a roadmap
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+It can be very challenging to keep a roadmap current. Having a mechanism
+for tagging open issues with `proposal` or `roadmap` and
+automatimatically extracting that into a web page can help with this.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open
+issues. Sending this to the dev@ list reminds people that there are
+things to work on, and gives them permission, and encouragement, to do
+so.
+
+Consider creating [good first
+issues](/committers/good-first-issues.html) as a place for new
+contributors to get started.

Review Comment:
   GitHub automatically does this for you 
https://github.com/apache/pekko/contribute just substitute peeks for any Apache 
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: notifications-unsubscr...@community.apache.org

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

[PR] Another one - proposal for "Community building" why description [comdev-working-groups]

[via GitHub]

potiuk opened a new pull request, #35:
URL: https://github.com/apache/comdev-working-groups/pull/35

   Continuuation from the previous whys - this one also inspired by some of the 
recent discussions on the authors/original authors and generally explaining the 
red-flags listed already.
   
   Looking forward to comments.


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

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

Re: [PR] Adds practical community building advice. [comdev-site]

[via GitHub]

jbonofre commented on code in PR #174:
URL: https://github.com/apache/comdev-site/pull/174#discussion_r1544702478


##
source/pmc/community-growth.md:
##
@@ -0,0 +1,82 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a road map
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open

Review Comment:
   I would also to propose:
   1. Tag some issues as "low hanging fruits" allowing new contributor to ramp 
up
   2. For PR and issue, I would propose to send reminder to PRs/issues not 
recently updated (to avoid stale ones)
   3. A good idea is also default assignee that can provide a first answer and 
add other people to help the contributor (mentoring process).



##
source/pmc/community-growth.md:
##
@@ -0,0 +1,82 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a road map
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.

Review Comment:
   Concretely, it's challenging to maintain a roadmap page on website.
   
   I would propose to "tag" issues with `proposal` or `roadmap` and 
extract/link this on website.
   That's probably the best approach to keep this up to date and accurate.



##
source/pmc/community-growth.md:
##
@@ -0,0 +1,82 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a road map
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open
+issues. Sending this to the dev@ list reminds people that there are
+things to work on, and gives them permission, and encouragement, to do
+so.
+
+## Clearly document contribution processes
+
+Double-check that your "how to contribute / build / test / submit PR"
+documentation is super clear and easy to follow.  Long-time committers
+on a project often forget all the institutional knowledge they just
+"know", so ensuring the "getting started" document actually works
+for newcomers is always worth looking at.
+
+Encourage newcomers to talk about, and document, their pain points

Review Comment:
   I would also mention the proposal process: how to submit new ideas ? how to 
be sure no proposal is lost or stale for too long ? how to track the proposals 
under discussion ?



##
source/pmc/community-growth.md:
##
@@ -0,0 +1,82 @@
+---
+title: Community Growth
+tags: ["pmc","committers","community"]
+---
+
+Growing your project community takes work. This document makes practical
+suggestions of how to encourage people to get involved in your project.
+
+## Publish a road map
+
+Volunteers can work on whatever they want, and so we have a tendency to
+not want to tell them what to work on. However, publishing a roadmap, or
+even a wishlist of features or improvements that are desired, can give
+people an idea of where they might be able to get involved.
+
+This also gives a clear sense that the project has ambitions, and is
+going somewhere, rather than that it is stagnating.
+
+## Periodically publish the open issue list
+
+Your ticket tracker allows you to periodically summarize the open
+issues. Sending this to the dev@ list reminds people that there are
+things to work on, and gives them permission, and encouragement, to do
+so.
+
+## Clearly document contribution 

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

rbowen merged PR #29:
URL: https://github.com/apache/comdev-working-groups/pull/29


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

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

Re: [PR] Adding the “The Apache Way of Open Source” slides from re:publica 2018 [comdev-site]

[via GitHub]

rbowen merged PR #173:
URL: https://github.com/apache/comdev-site/pull/173


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

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

[PR] Adds practical community building advice. [comdev-site]

[via GitHub]

rbowen opened a new pull request, #174:
URL: https://github.com/apache/comdev-site/pull/174

   Adds a new document, inspired by conversations with one of our projects in 
this situation, suggesting practical steps that a project can take to attract 
new contributors.


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

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

[PR] Proposed template to answer an offer to contribute to a project [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #34:
URL: https://github.com/apache/comdev-working-groups/pull/34

   This is taken from a response just sent to a dev list, and made more generic.


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

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

Re: [PR] Proposed template to answer an offer to contribute to a project [comdev-working-groups]

[via GitHub]

rbowen merged PR #34:
URL: https://github.com/apache/comdev-working-groups/pull/34


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

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

[PR] Adding the “The Apache Way of Open Source” slides from re:publica 2018 [comdev-site]

[via GitHub]

jogep opened a new pull request, #173:
URL: https://github.com/apache/comdev-site/pull/173

   Adding the “The Apache Way of Open Source” slides from re:publica 2018 
Berlin presentation to the list.
   


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

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

Re: [PR] Update mentee-ranking-process.md [comdev-site]

[via GitHub]

bdelacretaz merged PR #169:
URL: https://github.com/apache/comdev-site/pull/169


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

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

Re: [PR] Adding glauesppen in the volunteers [comdev-site]

[via GitHub]

bdelacretaz merged PR #172:
URL: https://github.com/apache/comdev-site/pull/172


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

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

Re: [PR] Volunteer as speaker [comdev-site]

[via GitHub]

bdelacretaz merged PR #171:
URL: https://github.com/apache/comdev-site/pull/171


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

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

[PR] Adding glauesppen in the volunteers [comdev-site]

[via GitHub]

glauesppen opened a new pull request, #172:
URL: https://github.com/apache/comdev-site/pull/172

   Adding glauesppen as volunteer


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

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

[PR] Volunteer as speaker [comdev-site]

[via GitHub]

aaltay opened a new pull request, #171:
URL: https://github.com/apache/comdev-site/pull/171

   Volunteer as speaker.


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

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

Re: [PR] doc: remove usage of CoPDoC [comdev-site]

[via GitHub]

bdelacretaz commented on PR #170:
URL: https://github.com/apache/comdev-site/pull/170#issuecomment-2014750121

   Thanks for this, Less Acronyms Are Better ! (LAAB ?)
   
   I'll just change "Apache strives..." to "The ASF strives..." as that's 
currently the preferred form.


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

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

Re: [PR] doc: remove usage of CoPDoC [comdev-site]

[via GitHub]

bdelacretaz merged PR #170:
URL: https://github.com/apache/comdev-site/pull/170


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

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

[PR] doc: remove usage of CoPDoC [comdev-site]

[via GitHub]

erisu opened a new pull request, #170:
URL: https://github.com/apache/comdev-site/pull/170

   Took me a while to figure out what "CoPDoC" stood for.
   
   I had to search for this acronym and found its meaning from other Apache 
projects, such as:
   
   - 
https://streampark.apache.org/community/contribution_guide/become_committer/
   - 
https://github.com/apache/ignite-3/blob/main/CONTRIBUTING.md#needed-contributions
   - https://www.mail-archive.com/dev@servicecomb.apache.org/msg04675.html
   - https://kyuubi.apache.org/become_pmc_member.html
   
   I was going to submit a PR to add the meaning of the acronym to this page, 
but then I noticed the last commit on this file actually removed it, about 10 
months ago.
   
   - https://github.com/apache/comdev-site/pull/118
   
   If we are removing the acronym's definition, I think we should also remove 
its usage.
   
   In my opinion, I didn't see anything wrong with the acronym, but perhaps the 
"Contributing A Project - CoPDoC" section could have been merged with the 
"Anyone Can Become A Committer" section at the point it's first used.
   
   It seems the acronym was added by SorraTheOrc in 2011 and mentioned a few 
times in the mailing list, but I couldn't find a discussion thread about its 
creation.
   
   The primary reason I encountered this acronym is because I am seeking to 
enhance the contributing documentation for the project I am involved with. I 
aimed to clearly communicate that anyone could contribute to various aspects of 
the project, including Project (CI, team communication, task flow, etc.), 
Community (supporting users in how to use the project or responding to 
tickets), Documentation, and Code. Not limited to code only.


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

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

[PR] Update mentee-ranking-process.md [comdev-site]

[via GitHub]

WillemJiang opened a new pull request, #169:
URL: https://github.com/apache/comdev-site/pull/169

   Fixed the formate issue.


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

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

Re: [PR] Add jbonofre as asf-volunteers [comdev-site]

[via GitHub]

bdelacretaz merged PR #168:
URL: https://github.com/apache/comdev-site/pull/168


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

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

Re: [PR] Add jbonofre as asf-volunteers [comdev-site]

[via GitHub]

jbonofre commented on PR #168:
URL: https://github.com/apache/comdev-site/pull/168#issuecomment-2012419056

   @bdelacretaz if you don't mind to review and merge :) 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: notifications-unsubscr...@community.apache.org

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

[PR] Add jbonofre as asf-volunteers [comdev-site]

[via GitHub]

jbonofre opened a new pull request, #168:
URL: https://github.com/apache/comdev-site/pull/168

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

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

Re: [PR] Added the volunteers information of ningjiang [comdev-site]

[via GitHub]

bdelacretaz merged PR #167:
URL: https://github.com/apache/comdev-site/pull/167


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

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

[PR] Added the volunteers information of ningjiang [comdev-site]

[via GitHub]

WillemJiang opened a new pull request, #167:
URL: https://github.com/apache/comdev-site/pull/167

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

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

Re: [PR] Volunteer as speaker; no mentoring this year though [comdev-site]

[via GitHub]

bdelacretaz merged PR #166:
URL: https://github.com/apache/comdev-site/pull/166


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

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

[PR] Volunteer as speaker; no mentoring this year though [comdev-site]

[via GitHub]

dirkx opened a new pull request, #166:
URL: https://github.com/apache/comdev-site/pull/166

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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

potiuk commented on PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#issuecomment-2007133213

   > I don't see point two mentioned
   
   There was a paragraph on that already:
   
   > The mailing list provide a permanent record of the discussions and 
decisions and the Apache Software Foundation
   Infrastructure team makes sure that the archives are preserved and available 
for the future, including the
   ability to search and browse the archives, as well as permanently link to 
the discussions and decisions so
   that they can be always referred to in the future.
   
   But I added a one sentence summary at the top and updated the paragraph to 
stress importance of it. The description indeed becomes a bit long to read it 
in it's entirety and get the quick grasp of what's in, so having a summarizing 
one line at the beginning is a good idea.


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

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

Re: [PR] Prepare updated speakers info for disabling community.zones.a.o [comdev-site]

[via GitHub]

bdelacretaz merged PR #160:
URL: https://github.com/apache/comdev-site/pull/160


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

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

Re: [PR] New "ASF volunteers" page to replace the community.zones.a.o apps [comdev-site]

[via GitHub]

bdelacretaz merged PR #146:
URL: https://github.com/apache/comdev-site/pull/146


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

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

[PR] Nav link to ALC [comdev-site]

[via GitHub]

rbowen opened a new pull request, #165:
URL: https://github.com/apache/comdev-site/pull/165

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

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

Re: [PR] Nav link to ALC [comdev-site]

[via GitHub]

rbowen merged PR #165:
URL: https://github.com/apache/comdev-site/pull/165


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

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

Re: [PR] Add Calvin Kirs(kirs) to advisor list [comdev-working-groups]

[via GitHub]

rbowen merged PR #30:
URL: https://github.com/apache/comdev-working-groups/pull/30


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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

rbowen commented on PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#issuecomment-2004203521

   There are two primary reasons we use mailing lists: 1) Accessibility and 2) 
Archive. That is, 1) ensuring that everyone in the world, regardless of 
language, timezone, or quality of network, can participate; and 2) ensuring 
that we have a permanent record of the discussion for later reference.
   
   We didn't invent mailing lists, or even have any discussion about how it was 
to be done. That's just how things were done in 1994, and had been done that 
way for a decade leading up to that. We were standing on the shoulders of 
giants, and recognizing the already-acknowledged benefits. 
   
   I don't see point two mentioned, but what you have written is fine. +1 to 
merging what you have. Possibly a mention of the archival nature of mailing 
lists would be warranted.
   


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

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

Re: [PR] Link to badging [comdev-working-groups]

[via GitHub]

rbowen merged PR #33:
URL: https://github.com/apache/comdev-working-groups/pull/33


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

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

Re: [PR] Add Justin Mclean to advisor list [comdev-working-groups]

[via GitHub]

rbowen merged PR #31:
URL: https://github.com/apache/comdev-working-groups/pull/31


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

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

[PR] Link to badging [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #33:
URL: https://github.com/apache/comdev-working-groups/pull/33

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

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

Re: [PR] Converted site from CMS style to Hugo [comdev-site]

[via GitHub]

hhjbbarhadi commented on PR #5:
URL: https://github.com/apache/comdev-site/pull/5#issuecomment-2002279092

   این برنامه دانلود نمئ شود 


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

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

Re: [PR] link to social media channels [comdev-working-groups]

[via GitHub]

rbowen merged PR #32:
URL: https://github.com/apache/comdev-working-groups/pull/32


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

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

[PR] link to social media channels [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #32:
URL: https://github.com/apache/comdev-working-groups/pull/32

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

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

Re: [PR] Slight reorg: Removes duplication and renames a few links [comdev-site]

[via GitHub]

rbowen merged PR #164:
URL: https://github.com/apache/comdev-site/pull/164


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

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

[PR] Slight reorg: Removes duplication and renames a few links [comdev-site]

[via GitHub]

rbowen opened a new pull request, #164:
URL: https://github.com/apache/comdev-site/pull/164

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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

potiuk commented on PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#issuecomment-1992264772

   Added some updates based on @justinmclean's comment. I really would love to 
hear from others, mainly about "using other tools as well". I think there are a 
number of "let's only use devlist" or "bring all the communication to the 
devlist automaticallly" - but as stated in the current version - there is a 
balance between "low signal-to-noise" on one end and "decisions made outside of 
the list" - which is I think the `gist` of the whole `why`. Too much in one 
direction is bad, too much in the other is also bad for other reasons. 
   
   I wonder if the way described now is good in describing 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: notifications-unsubscr...@community.apache.org

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

potiuk commented on code in PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#discussion_r1521914018


##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.

Review Comment:
   I like the "informatoin density" particaularly (and agree). I added a small 
chapter stressing the properties you mentioned 



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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

potiuk commented on code in PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#discussion_r1521901040


##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.
+
+Why the time passed and technology evolved, the mailing list still keep a lot 
of the properties that made it
+the primary communication channel for the project. It is still the most 
inclusive and accessible channel for
+all community members, they allow for asynchronous communication and do not 
require from the community members
+to be online at the same time and to setup accounts with particular external 
services.
+
+They also provide a permanent record of the discussions and decisions and the 
Apache Software Foundation
+Infrastructure team makes sure that the archives are preserved and available 
for the future, including the
+ability to search and browse the archives, as well as permanently link to the 
discussions and decisions so
+that they can be always referred to in the future.
+
+The communication on mailing list happens in English, which is the language of 
the Foundation,
+and the language of the majority of the Foundation's community members. 
+
+An important aspect of using the mailing list is that it allows anyone 
(including PMC members, committers,
+contributors, and users, but also people from outside - Board members, other 
PMCs, non-ASF folks) to take
+a look at the way how decisions are made and even participate in the 
discussions and decisions, and to
+peek into the PMC status. This is important for the Foundation's transparency 
and for the community building
+process.
+
+PMCs have at least two lists: dev@ and private@ - but it is important to 
mention that the private@ list should
+only be used for discussions that are absolutely not suitable for public 
consumption, such as discussions
+about security vulnerabilities, or discussions about individuals that are not 
suitable for public consumption
+and should be kept private. The private@ list should not be used for 
discussions about the project's direction,
+releases, or other important decisions.

Review Comment:
   Yep. Added.



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

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

Re: [PR] Add links to wg git repos [comdev-site]

[via GitHub]

rbowen merged PR #163:
URL: https://github.com/apache/comdev-site/pull/163


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

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

[PR] Add links to wg git repos [comdev-site]

[via GitHub]

rbowen opened a new pull request, #163:
URL: https://github.com/apache/comdev-site/pull/163

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

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

Re: [PR] New "ASF volunteers" page to replace the community.zones.a.o apps [comdev-site]

[via GitHub]

rbowen commented on PR #146:
URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1991876154

   +1 to all of this, and to go ahead and merge. I am content to fix problems 
as they come up, rather than demanding perfection before merging. Thanks for 
all of this work!


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

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

Re: [PR] Adds 'workinggroups' web content, and links to that content [comdev-site]

[via GitHub]

rbowen merged PR #162:
URL: https://github.com/apache/comdev-site/pull/162


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

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

[PR] Adds 'workinggroups' web content, and links to that content [comdev-site]

[via GitHub]

rbowen opened a new pull request, #162:
URL: https://github.com/apache/comdev-site/pull/162

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

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

[PR] Add justinmclean to advisor list [comdev-working-groups]

[via GitHub]

justinmclean opened a new pull request, #31:
URL: https://github.com/apache/comdev-working-groups/pull/31

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

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

[PR] Add Calvin Kirs(kirs) to advisor list [comdev-working-groups]

[via GitHub]

CalvinKirs opened a new pull request, #30:
URL: https://github.com/apache/comdev-working-groups/pull/30

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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

justinmclean commented on code in PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#discussion_r1520601586


##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.

Review Comment:
   Also filtered or grouped by rules.



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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

sebbASF commented on code in PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#discussion_r1520598309


##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.

Review Comment:
   Most mail clients also allow emails to be easily categorised



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

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

Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

justinmclean commented on code in PR #29:
URL: 
https://github.com/apache/comdev-working-groups/pull/29#discussion_r1520571314


##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.
+
+Why the time passed and technology evolved, the mailing list still keep a lot 
of the properties that made it
+the primary communication channel for the project. It is still the most 
inclusive and accessible channel for
+all community members, they allow for asynchronous communication and do not 
require from the community members
+to be online at the same time and to setup accounts with particular external 
services.
+
+They also provide a permanent record of the discussions and decisions and the 
Apache Software Foundation
+Infrastructure team makes sure that the archives are preserved and available 
for the future, including the
+ability to search and browse the archives, as well as permanently link to the 
discussions and decisions so
+that they can be always referred to in the future.
+
+The communication on mailing list happens in English, which is the language of 
the Foundation,
+and the language of the majority of the Foundation's community members. 
+
+An important aspect of using the mailing list is that it allows anyone 
(including PMC members, committers,
+contributors, and users, but also people from outside - Board members, other 
PMCs, non-ASF folks) to take
+a look at the way how decisions are made and even participate in the 
discussions and decisions, and to
+peek into the PMC status. This is important for the Foundation's transparency 
and for the community building
+process.
+
+PMCs have at least two lists: dev@ and private@ - but it is important to 
mention that the private@ list should
+only be used for discussions that are absolutely not suitable for public 
consumption, such as discussions
+about security vulnerabilities, or discussions about individuals that are not 
suitable for public consumption
+and should be kept private. The private@ list should not be used for 
discussions about the project's direction,
+releases, or other important decisions.

Review Comment:
   One possible exception is discussing/voting on a release with a security 
issue.



##
wg-advisors/why/why_discussions_and_decisions.md:
##
@@ -1,13 +1,77 @@
 # Why discussion and decision making had to happen on the mailing list
 
-TODO:
-
 ## Summary 
 
+Discussions and decision making should happen on the mailing list to ensure 
that the project is
+transparent and that all decisions are made in the open. This is important to 
ensure that all
+community members have the opportunity to participate in the decision making 
process.
+
 ## Links to relevant documents
 
+* [The Apache Way](https://www.apache.org/theapacheway/)
+* [Mailing list 
guidelines](https://www.apache.org/foundation/mailinglists.html)
+
 ## Why are we doing it?
 
+Mailing list the primary communication channel for the project. It has been 
chosen - at the dawn of the
+Foundation as the primary communication channel because it was the most 
inclusive and accessible channel
+for all community members, allowing for asynchronous communication and 
ensuring that all community members
+have the opportunity to participate. All the important decisions and 
discussions happens there - including
+the decision to invite new committers and PMC members, the decisions to 
release software, and the decisions
+to change the project's direction.

Review Comment:
   Other good reasons for using mailing lists are that they are accessible to 
everyone in any country, can be archived, are easily searchable, and are 
asynchronous, so anyone can take part no matter their time zone/day job/other 
responsibilities. I can see They also have far more information density than 
online chat or 

[PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]

[via GitHub]

potiuk opened a new pull request, #29:
URL: https://github.com/apache/comdev-working-groups/pull/29

   This change is a proposal on how we could describe the next "why" that I 
consider as very important - discussions and decision making.
   
   I tried to map all the red-flags we had for it into a coherent description 
of the "why" and linked to the two important places in the ASF "rules" that 
best describe some of the aspects of it.
   
   I think the part of the variations might be contentious, and I hope that in 
the advisors "leaders" group we can discuss it and get to a consensus that
   
   a) there are good reasons why the mailing lists were chosen in the
  long past
   
   b) the reasons for that are still valid today and mailing list shoud
  remoain the most important place for discussions and decision making
   
   while c) with the current set of technologies in many cases it is not the 
only way, but as long as PMC actively makes sure that the important discussions 
and decisions (and generally only those in more active projects) are brought to 
the list and where list is active and used for all the voting, super important 
decisions, this is all cool
   
   Looking forward to discussion 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: notifications-unsubscr...@community.apache.org

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

Re: [PR] typos, and add tenet statements [comdev-working-groups]

[via GitHub]

rbowen merged PR #28:
URL: https://github.com/apache/comdev-working-groups/pull/28


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

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

[PR] typos, and add tenet statements [comdev-working-groups]

[via GitHub]

rbowen opened a new pull request, #28:
URL: https://github.com/apache/comdev-working-groups/pull/28

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

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

Re: [PR] Restructure the red flags and add placeholders for more whys [comdev-working-groups]

[via GitHub]

rbowen merged PR #27:
URL: https://github.com/apache/comdev-working-groups/pull/27


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

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

Re: [PR] fix: defensively access filepath [comdev-site]

[via GitHub]

tisonkun commented on PR #161:
URL: https://github.com/apache/comdev-site/pull/161#issuecomment-1987528896

   Make sense. Will do :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: notifications-unsubscr...@community.apache.org

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

Re: [PR] fix: defensively access filepath [comdev-site]

[via GitHub]

sebbASF commented on PR #161:
URL: https://github.com/apache/comdev-site/pull/161#issuecomment-1987157420

   In future, please try to fix one issue at a time.
   Makes it easier to follow, as well as easier to revert should that be 
necessary.
   Also the log history should mention all changes.


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

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

Re: [PR] fix: defensively access filepath [comdev-site]

[via GitHub]

tisonkun merged PR #161:
URL: https://github.com/apache/comdev-site/pull/161


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

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