Re: Update Website Template (WAS: Help to get the Wayang project website in shape)
When a project uses the template, they can download the zip file from the branch they want to use. We may need to specify it in the main branch README. Willem Jiang On Wed, Feb 28, 2024 at 10:59 AM tison wrote: > > Yeah .. > > The pelican template is a repo template and has its own repo with a > asf-site branch while it may be able to preview .. > > I'd like to ask for a repo for the docu template but it ends up with > hosting in another branch in the apache-website-template repo :O > > Best, > tison. > > Dave Fisher 于2024年2月27日周二 22:42写道： > > > > Hi Shane, > > > > The Pelican ASF Template at https://github.com/apache/template-site is > > somewhat out of date as many contributors have contributed to ASF Pelican > > in the last two or three years. It would be good to revisit. I’m not sure I > > have the time or not, but that would great to update. One area in > > particular is as simple as adding updates to required privacy policies. > > > > Best, > > Dave > > > > > On Feb 26, 2024, at 7:15 AM, tison wrote: > > > > > > Hi Shane, > > > > > > It's under the list. See [1] and the referred thread. I'll try to > > > submit a patch this week to add this information, including the > > > pelican info. We'd later move the pelican template to this repo also > > > in a dedicated branch and make it "just work". > > > > > > Best, > > > tison. > > > > > > [1] https://github.com/apache/apache-website-template/issues/18 > > > > > > Shane Curcuru 于2024年2月26日周一 19:34写道： > > >> > > >> tison wrote on 2/4/24 10:16 AM: > > >>> Hi, > > >>> > > >>> I finally find some time to prepare a demo for the new website template > > >>> [1]. > > >> > > >> This is awesome; I love providing more default "just use this" templates > > >> in various themes like this. > > >> > > >> One question: why doesn't this also link (At least in the docs for each > > >> readme maybe?) to the Infra-supported pelican template? We should at > > >> least point to that, since infra supports it and it provides a > > >> python-managed template, in case people like that better than > > >> Jekyll/ruby. > > >> > > >> https://infra.apache.org/asf-pelican-gettingstarted.html > > >> > > >> -- > > >> - Shane > > >> Member > > >> The Apache Software Foundation > > >> > > >> > > >> - > > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > >> For additional commands, e-mail: dev-h...@community.apache.org > > >> > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update Website Template (WAS: Help to get the Wayang project website in shape)
Yeah .. The pelican template is a repo template and has its own repo with a asf-site branch while it may be able to preview .. I'd like to ask for a repo for the docu template but it ends up with hosting in another branch in the apache-website-template repo :O Best, tison. Dave Fisher 于2024年2月27日周二 22:42写道： > > Hi Shane, > > The Pelican ASF Template at https://github.com/apache/template-site is > somewhat out of date as many contributors have contributed to ASF Pelican in > the last two or three years. It would be good to revisit. I’m not sure I have > the time or not, but that would great to update. One area in particular is as > simple as adding updates to required privacy policies. > > Best, > Dave > > > On Feb 26, 2024, at 7:15 AM, tison wrote: > > > > Hi Shane, > > > > It's under the list. See [1] and the referred thread. I'll try to > > submit a patch this week to add this information, including the > > pelican info. We'd later move the pelican template to this repo also > > in a dedicated branch and make it "just work". > > > > Best, > > tison. > > > > [1] https://github.com/apache/apache-website-template/issues/18 > > > > Shane Curcuru 于2024年2月26日周一 19:34写道： > >> > >> tison wrote on 2/4/24 10:16 AM: > >>> Hi, > >>> > >>> I finally find some time to prepare a demo for the new website template > >>> [1]. > >> > >> This is awesome; I love providing more default "just use this" templates > >> in various themes like this. > >> > >> One question: why doesn't this also link (At least in the docs for each > >> readme maybe?) to the Infra-supported pelican template? We should at > >> least point to that, since infra supports it and it provides a > >> python-managed template, in case people like that better than Jekyll/ruby. > >> > >> https://infra.apache.org/asf-pelican-gettingstarted.html > >> > >> -- > >> - Shane > >> Member > >> The Apache Software Foundation > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Web site checker needs help
While reviewing some of the project reports for the board meeting, I use the tool https://whimsy.apache.org/site/ to help me understand the projects' conformance with policy. I noticed many "false negatives" and "false positives" that need attention. I believe that the tool is extremely useful but needs help. I have started to document and ask for feedback on some of the issues, but this is bigger than any one person can handle. Is it worth creating a new community-working-group-site-check to document the issues with the tool? Perhaps a better name would help... Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] chore: send notification to a separate list [comdev-working-groups]
tisonkun merged PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] chore: send notification to a separate list [comdev-working-groups]
tisonkun commented on PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#issuecomment-1966949988 @rbowen Different repo I think. The other days before is for comdev-site. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] chore: send notification to a separate list [comdev-working-groups]
tisonkun commented on code in PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#discussion_r1504555742 ## .asf.yaml: ## @@ -8,6 +8,6 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org - pullrequests: dev@community.apache.org + issues: notificat...@community.apache.org + pullrequests: notificat...@community.apache.org Review Comment: ```suggestion pullrequests: notificati...@community.apache.org ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] chore: send notification to a separate list [comdev-working-groups]
rlenferink commented on code in PR #22: URL: https://github.com/apache/comdev-working-groups/pull/22#discussion_r1504553366 ## .asf.yaml: ## @@ -8,6 +8,6 @@ github: notifications: commits: comm...@community.apache.org - issues: dev@community.apache.org - pullrequests: dev@community.apache.org + issues: notificat...@community.apache.org Review Comment: Typo (twice) ```suggestion issues: notificati...@community.apache.org ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [WG: Welcome] Proposal, a Welcome Working Group - onboarding too?
> On Feb 25, 2024, at 5:10 PM, Shane Curcuru wrote: > > Rich Bowen wrote on 2/7/24 11:53 AM: >> Proposed: A formal working group around how we welcome new folks in a >> consistent and helpful manner. >> We get people on this list (and on every dev@ and user@ list at the >> foundation) asking how to get engaged. We almost always give them unhelpful >> answers, and send them off to go figure it out on their own. >> The Welcome WG would write documentation, and process, around welcoming >> these new folks, and shepherding them towards engagement. This would >> include, but not be limited to: > ...snip... > Question: should the wg-welcome group include reviewing all onboarding > materials too, or does that deserve it's own group at some point? They are > closely related, but onboarding is a larger topic. > I could definitely see it as a separate WG. I don’t want to spend a lot of time creating a huge pile of WGs before anybody is actually committed to working on any of them, but if we have people show up to do this work, then splitting would make a lot of sense. They are, indeed, closely related but not the same thing. > "Welcoming" is about creating easy to re-use content to help answer simple > questions all around, and guiding newcomers - or existing contributors who > answer questions! - to the right kind of path, and in a friendly and > consistent way. > > "Onboarding" I see as reviewing and updating the actual emails, boilerplate, > and links that we send to anyone who is being welcomed to a new role at the > ASF - committer (on any project, or on an additional project), PMC member, > officer, Member, etc. > > I've already listed the majority of actual sources our tooling actually mails > or includes links to people in various places: > > https://cwiki.apache.org/confluence/display/COMDEV/Proposal%3A+Improving+Onboarding+Experiences > Yeah, that’s definitely a lot of work that we need to do, and looks like very actionable “where can I jump in” projects. Still struggling with the part of the process where we actually find people to *do* the work. > We need a focused group to start reviewing these, and updating them to be > consistent, friendly, and useful for newcomers. > > -- > - Shane > Member > The Apache Software Foundation > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
rbowen commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1966782830 I think, eventually, we'd want to move the list of advisors to a separate file, but I don't see that as a blocker to moving forward with this PR. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update Website Template (WAS: Help to get the Wayang project website in shape)
Hi Shane, The Pelican ASF Template at https://github.com/apache/template-site is somewhat out of date as many contributors have contributed to ASF Pelican in the last two or three years. It would be good to revisit. I’m not sure I have the time or not, but that would great to update. One area in particular is as simple as adding updates to required privacy policies. Best, Dave > On Feb 26, 2024, at 7:15 AM, tison wrote: > > Hi Shane, > > It's under the list. See [1] and the referred thread. I'll try to > submit a patch this week to add this information, including the > pelican info. We'd later move the pelican template to this repo also > in a dedicated branch and make it "just work". > > Best, > tison. > > [1] https://github.com/apache/apache-website-template/issues/18 > > Shane Curcuru 于2024年2月26日周一 19:34写道： >> >> tison wrote on 2/4/24 10:16 AM: >>> Hi, >>> >>> I finally find some time to prepare a demo for the new website template [1]. >> >> This is awesome; I love providing more default "just use this" templates >> in various themes like this. >> >> One question: why doesn't this also link (At least in the docs for each >> readme maybe?) to the Infra-supported pelican template? We should at >> least point to that, since infra supports it and it provides a >> python-managed template, in case people like that better than Jekyll/ruby. >> >> https://infra.apache.org/asf-pelican-gettingstarted.html >> >> -- >> - Shane >> Member >> The Apache Software Foundation >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
I agree the core idea behind the Asf is contribute in a committ mode Others should be added for different areas Who are redflagged should be re grouped Regards Koti On Tue, 27 Feb 2024, 20:04 koteswara Rao Gundapaneni, < koti.gundapan...@gmail.com> wrote: > > I totally agree the knowledge base is essential > > Regards > Koti > > > On Tue, 27 Feb 2024, 19:28 potiuk (via GitHub), wrote: > >> >> potiuk commented on PR #16: >> URL: >> https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 >> >>If there are no more comments. I'd love to get this one merged and >> then maybe others (I can do as well) add a bit more why`s for different >> areas. I think also - when we have a few whys we might actually regroup the >> "red-flags" and have them groupped according to the `why` they are >> referring to - rather than link them individually - but taht migh be a >> refactor of the docs when we add 2nd or 3rd why as well. >> >> >> -- >> This is an automated message from the Apache Git Service. >> To respond to the message, please log on to GitHub and use the >> URL above to go to the specific comment. >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> >> For queries about this service, please contact Infrastructure at: >> us...@infra.apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
I totally agree the knowledge base is essential Regards Koti On Tue, 27 Feb 2024, 19:28 potiuk (via GitHub), wrote: > > potiuk commented on PR #16: > URL: > https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 > >If there are no more comments. I'd love to get this one merged and then > maybe others (I can do as well) add a bit more why`s for different areas. I > think also - when we have a few whys we might actually regroup the > "red-flags" and have them groupped according to the `why` they are > referring to - rather than link them individually - but taht migh be a > refactor of the docs when we add 2nd or 3rd why as well. > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [PR] 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
rbowen merged PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
rbowen merged PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 If there are no more comments. I'd love to get this one merged and then maybe others (I can do as well) add a bit more why`s for different areas. I think also - when we have a few whys we might actually regroup the "red-flags" and have them groupped according to the `why` they are referring to - rather than link them individually - but taht migh be a refactor of the docs when we add 2nd or 3rd why as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1966593319 I hope it's ready for merge -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1504265776 ## wg-advisors/advisors.md: ## @@ -0,0 +1,14 @@ +Here you will find a list of advisors who signed up to be listed in this repository. + +In order to be listed here, you must be an ASF member. If you are one, you can just +open a PR to add yourself to this list. If you are listed here and you no longer want +to be an advisor, please remove yourself with a PR. + +If you want to advise a PMC, please reach out to the PMC and ask if they would like to have you as an advisor Review Comment: Updated, squashed and rebased. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Add social media todo item [comdev-working-groups]
rbowen merged PR #25: URL: https://github.com/apache/comdev-working-groups/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[PR] Add social media todo item [comdev-working-groups]
rbowen opened a new pull request, #25: URL: https://github.com/apache/comdev-working-groups/pull/25 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] working group content [comdev-working-groups]
rbowen merged PR #24: URL: https://github.com/apache/comdev-working-groups/pull/24 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[PR] working group content [comdev-working-groups]
rbowen opened a new pull request, #24: URL: https://github.com/apache/comdev-working-groups/pull/24 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] ToDo list for social media [comdev-working-groups]
rbowen merged PR #23: URL: https://github.com/apache/comdev-working-groups/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[PR] ToDo list for social media [comdev-working-groups]
rbowen opened a new pull request, #23: URL: https://github.com/apache/comdev-working-groups/pull/23 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
