Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

bdelacretaz commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2688046519 FYI `calendar.json` is now renamed to `calendar-DO-NOT-EDIT.json` and the README is updated (thanks @rbowen) to explain how calendar updates work. -- This is an automated me

Re: [PR] Rename calendar.json to prevent unwanted edits [comdev-events-site]

bdelacretaz merged PR #21: URL: https://github.com/apache/comdev-events-site/pull/21 -- 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...@com

Re: [PR] Rename calendar.json to prevent unwanted edits [comdev-events-site]

sebbASF commented on PR #21: URL: https://github.com/apache/comdev-events-site/pull/21#issuecomment-2688004952 Sorry, did not notice that. LGTM. -- 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 t

Re: [PR] Rename calendar.json to prevent unwanted edits [comdev-events-site]

bdelacretaz commented on PR #21: URL: https://github.com/apache/comdev-events-site/pull/21#issuecomment-2687988940 > Also rename the file itself [commit #b6cd41d4](https://github.com/apache/comdev-events-site/pull/21/commits/b6cd41d421347f9959a01e976562445413c4fe77) does include

Re: [PR] Rename calendar.json to prevent unwanted edits [comdev-events-site]

sebbASF commented on PR #21: URL: https://github.com/apache/comdev-events-site/pull/21#issuecomment-2687797603 The file needs to be renamed 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 t

[PR] Rename calendar.json to prevent unwanted edits [comdev-events-site]

bdelacretaz opened a new pull request, #21: URL: https://github.com/apache/comdev-events-site/pull/21 If this is merged we'll need to verify that `static/js/calendar.json` is correctly deleted after running the updated version of `.github/workflows/getcalendar.yml` that this PR provides.

Re: [PR] Update instructions for manual triggering of getcalendar workflow [comdev-events-site]

rbowen commented on PR #20: URL: https://github.com/apache/comdev-events-site/pull/20#issuecomment-2685809971 Thanks. I had no idea that was a thing. -- 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

Re: [PR] Update instructions for manual triggering of getcalendar workflow [comdev-events-site]

sebbASF merged PR #20: URL: https://github.com/apache/comdev-events-site/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...@communi

[PR] Update instructions for manual triggering of getcalendar workflow [comdev-events-site]

rlenferink opened a new pull request, #20: URL: https://github.com/apache/comdev-events-site/pull/20 It might be useful to include a direct link with the step which button(s) to click. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

rbowen commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684982426 Based on what happened yesterday (I updated the Google Calendar, and 20-30 minutes later the site updated) I would encourage people NOT to directly edit calendar.json, but, rather,

Re: [PR] Update getcalendar.yml workflow [comdev-events-site]

sebbASF merged PR #19: URL: https://github.com/apache/comdev-events-site/pull/19 -- 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...@communi

[PR] Update getcalendar.yml workflow [comdev-events-site]

rlenferink opened a new pull request, #19: URL: https://github.com/apache/comdev-events-site/pull/19 (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 unsubsc

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

bdelacretaz commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684424393 Would it make sense to change the names as follows for clarity? - `calendar.json` -> `calendar-imported-DO-NOT-EDIT.json` - `Community Developers` -> `Comdev - getcalendar

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

sebbASF commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684405174 There is a GH workflow getcalendar.yml [1]. It runs every day at 9:50 and pulls the current calendar into calendar.json, which is committed (if changed) using the 'Community Deve

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

rlenferink commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684334319 > It's `static/js/calendar.json`. Yes, but who/what updates that file? Apparently it is updated 15 hours ago by `Community Developers `. Who pushed that commit? -- Thi

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

tisonkun commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684297040 It's `static/js/calendar.json`. -- 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 th

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

rlenferink commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684248428 @bproffitt at least in the top level README it is described that changes should be made to the `main` branch and that updates to the `asf-site` branch are automated: https://g

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

tisonkun commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684174634 I saw that the main branch was updated at https://github.com/apache/comdev-events-site/commit/cc68177be66e7927c541391738efe2eb9b6d20ff and I wonder how the anonymous updates made

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

bproffitt commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2684133702 Well, since Conferences is still not clear on what the actual updating procedure is, (and no, the link provided in planners@ is not helpful), I am beginning to wonder if we shou

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

sebbASF commented on PR #18: URL: https://github.com/apache/comdev-events-site/pull/18#issuecomment-2682704111 Changes to asf-site need to be made to the main branch, otherwise they will be overwritten the next time the site is re-built. -- This is an automated message from the Apache Gi

[PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

suehle opened a new pull request, #18: URL: https://github.com/apache/comdev-events-site/pull/18 (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

Re: [PR] Change Denver to Minneapolis in calendar.json [comdev-events-site]

bproffitt merged PR #18: URL: https://github.com/apache/comdev-events-site/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...@commu

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

OnlyAviv closed pull request #13: [#12] Redesign - Styles + Nav URL: https://github.com/apache/comdev-events-site/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 uns

[PR] Link to the events policy [comdev-events-site]

rbowen opened a new pull request, #17: URL: https://github.com/apache/comdev-events-site/pull/17 (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

Re: [PR] Link to the events policy [comdev-events-site]

rbowen merged PR #17: URL: https://github.com/apache/comdev-events-site/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...@communit

Re: [PR] Link to current event promotion tool [comdev-events-site]

rbowen merged PR #16: URL: https://github.com/apache/comdev-events-site/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...@communit

[PR] Link to current event promotion tool [comdev-events-site]

rbowen opened a new pull request, #16: URL: https://github.com/apache/comdev-events-site/pull/16 (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

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

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...@communit

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

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

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

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...@communi

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

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 unsubscrib

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

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 res

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

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 commen

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

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

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

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 ch

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

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

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

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

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

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 th

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

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 leas

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

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/conco

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

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...@com

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

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 o

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

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 - pullre

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

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 - pull

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

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 automat

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

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 t

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

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...@commu

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

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...@commu

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

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 f

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

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 s

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

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 liste

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

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...@commu

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

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 unsubscr

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

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...@commu

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

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 unsubscr

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

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...@commu

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

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 unsubscr

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

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 lis

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

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...@com

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

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 GitH

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

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 we

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

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 un

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

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

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

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 - pullreq

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

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 - pullreq

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

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 unsubs

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

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

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

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

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

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 unsubs

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

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 w

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

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 w

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

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 lu

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

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

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

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

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

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 Adviso

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

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 num

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

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 ha

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

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

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

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 mis

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

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 proc

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

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 proc

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

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

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

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 nomin

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

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 nomin

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

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 nomin

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

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?

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

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 nomin

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

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

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

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 mis

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

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 fro

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

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 proc

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

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 proc

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

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 nomin

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

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?

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

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 nom

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

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 nom

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

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 nom

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

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 nom

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

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 Adviso

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

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 m

  1   2   3   4   5   6   >