[jira] [Resolved] (COMDEV-542) More public tone for sharpeners
[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen resolved COMDEV-542. --- Resolution: Fixed Patch applied > More public tone for sharpeners > --- > > Key: COMDEV-542 > URL: https://issues.apache.org/jira/browse/COMDEV-542 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: sharpeners.patch > > > Some suggested changes to Sharpeners README -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-542) More public tone for sharpeners
[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen closed COMDEV-542. - > More public tone for sharpeners > --- > > Key: COMDEV-542 > URL: https://issues.apache.org/jira/browse/COMDEV-542 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: sharpeners.patch > > > Some suggested changes to Sharpeners README -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-542) More public tone for sharpeners
[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816993#comment-17816993 ] Rich Bowen commented on COMDEV-542: --- Thanks. Applied in r1915769. > More public tone for sharpeners > --- > > Key: COMDEV-542 > URL: https://issues.apache.org/jira/browse/COMDEV-542 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: sharpeners.patch > > > Some suggested changes to Sharpeners README -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-543) Sharpeners use cases
[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen closed COMDEV-543. - Resolution: Fixed Thanks. Added in r1915770. > Sharpeners use cases > > > Key: COMDEV-543 > URL: https://issues.apache.org/jira/browse/COMDEV-543 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: use-cases.md > > > Brain dump of ideas for sharpeners use cases -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [WG: Sharpeners] Proposed - Sharpeners
Thanks, Phil. Patches applied. This is all good stuff. — Rich Bowen rbo...@rcbowen.com > On Feb 12, 2024, at 5:21 PM, Phil Steitz wrote: > > Sorry, last message got away from me. The point of the use cases is to get > a rough consensus of the kinds of things that a Sharpener will work on. > Ideally, these get a) fixed / better organized and b) fleshed out with > useful links, suggestions and scope of engagement statements. > > So for example, if "barriers to contribution" survives, we get into what is > / is not OK for a sharpener to suggest and when it is actually a problem. > More concretely, consider the case where "some people" think that project > Foo has an impossibly high bar for commit. How do you work out what that > means? How is it impacting the community? Both "not a problem" and "yes, > this is a problem" examples could be added, as well as some info on what > the Sharpener is allowed to question / how deeply they should engage in > tweaking internal PMC processes. > > Phil > > On Mon, Feb 12, 2024 at 3:08 PM Phil Steitz wrote: > >> OK, I added a brain dump on the use cases. This is in the spirit of "good >> ideas, bad code" ;)
Re: [WG: Welcome] Proposal, a Welcome Working Group
Hi Rich, This WG sounds excellent from a Diversity perspective. We can help newcomers to find their path. You can count with me in this WG. Em qui., 8 de fev. de 2024 às 17:27, Kristopher Traquair < writerbl...@apache.org> escreveu: > Hey Rich, > > This sounds like a great idea. I'm not sure in what capacity, but I'd love > to offer any assistance I can to help this WG. > > On 2024/02/07 16:53:01 Rich Bowen wrote: > > 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: > > > > * Guiding projects towards the incubator. This includes the “why would > you want to be at Apache? Why would you *NOT* fit at Apache?” documentation > that we really don’t have yet. > > * Guiding brand-new contributors towards how, and where, to contribute. > This may include working with some of our more welcoming projects to figure > out best practice, and our less-welcoming projects to figure out why they > are and help them fix that. > > * Working with second-time contributors to encourage best practice. (See > https://mikemcquaid.com/stop-mentoring-first-time-contributors/ for > thoughts on first- vs second-time contributors) > > * Crafting boilerplate answers to send to folks who show up asking for > help getting involved, so that we don’t continue this practice of unhelpful > “go figure it out on your own” responses. > > * Maybe work on some kind of a badging program (See > https://badges.fedoraproject.org/ if you don’t know what I mean by that) > to incentivize and gamify community engagement, for reasons that I would > love to talk much more about, but are beyond the scope of this proposal. > > > > What do y’all think? > > > > — > > Rich Bowen > > rbo...@rcbowen.com > > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- Gláucia Esppenchutz - Twitter: @lyuric19 Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312
Re: [WG: Sharpeners] Proposed - Sharpeners
Thanks, Rich. I hope others will jump in and improve the use cases, ideally illustrated with some publicly viewable links or summaries by people like @Niclas Hedhman and @Ted Dunning who have helped communities through challenges in the past. Phil On Tue, Feb 13, 2024 at 6:54 AM Rich Bowen wrote: > Thanks, Phil. Patches applied. This is all good stuff. > > — > Rich Bowen > rbo...@rcbowen.com > > > > > > On Feb 12, 2024, at 5:21 PM, Phil Steitz wrote: > > > > Sorry, last message got away from me. The point of the use cases is to > get > > a rough consensus of the kinds of things that a Sharpener will work on. > > Ideally, these get a) fixed / better organized and b) fleshed out with > > useful links, suggestions and scope of engagement statements. > > > > So for example, if "barriers to contribution" survives, we get into what > is > > / is not OK for a sharpener to suggest and when it is actually a problem. > > More concretely, consider the case where "some people" think that project > > Foo has an impossibly high bar for commit. How do you work out what that > > means? How is it impacting the community? Both "not a problem" and > "yes, > > this is a problem" examples could be added, as well as some info on what > > the Sharpener is allowed to question / how deeply they should engage in > > tweaking internal PMC processes. > > > > Phil > > > > On Mon, Feb 12, 2024 at 3:08 PM Phil Steitz > wrote: > > > >> OK, I added a brain dump on the use cases. This is in the spirit of > "good > >> ideas, bad code" ;) >
[WG] Workgroups repo moved to git
The workgroups repo has now moved to https://github.com/apache/comdev-working-groups Please adjust accordingly Zili, can you close the ticket you opened? I appear to not have permission to do so. — Rich Bowen rbo...@rcbowen.com
[PR] Fix repo location [comdev-working-groups]
rbowen opened a new pull request, #1: URL: https://github.com/apache/comdev-working-groups/pull/1 (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] Fix repo location [comdev-working-groups]
rbowen merged PR #1: URL: https://github.com/apache/comdev-working-groups/pull/1 -- This is an automated message from the Apache 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
Hi, I'll be glad to offer my help on such an idea. I've been a commiter on the Maven project since about 2 years and I remember my fistrs contributions and first challenges with it. So I'll be happy to help others with similar journeys. I think that not only the first wellcome is important but also the usual collaboration with contributors. śr., 7 lut 2024 o 17:53 Rich Bowen napisał(a): > 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: > > * Guiding projects towards the incubator. This includes the “why would you > want to be at Apache? Why would you *NOT* fit at Apache?” documentation > that we really don’t have yet. > * Guiding brand-new contributors towards how, and where, to contribute. > This may include working with some of our more welcoming projects to figure > out best practice, and our less-welcoming projects to figure out why they > are and help them fix that. > * Working with second-time contributors to encourage best practice. (See > https://mikemcquaid.com/stop-mentoring-first-time-contributors/ for > thoughts on first- vs second-time contributors) > * Crafting boilerplate answers to send to folks who show up asking for > help getting involved, so that we don’t continue this practice of unhelpful > “go figure it out on your own” responses. > * Maybe work on some kind of a badging program (See > https://badges.fedoraproject.org/ if you don’t know what I mean by that) > to incentivize and gamify community engagement, for reasons that I would > love to talk much more about, but are beyond the scope of this proposal. > > What do y’all think? > > — > Rich Bowen > rbo...@rcbowen.com > > > > > -- Sławomir Jaranowski
[jira] [Commented] (COMDEV-543) Sharpeners use cases
[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817176#comment-17817176 ] Justin Mclean commented on COMDEV-543: -- Here's a list I have if it helps - theres some overlap with teh use-cases doc added, but a few missing things I think. Is unsure when to recognise committers Is having online meetings that are not brought back to the mailing list. Has a website external to apache.org Is missing reports Is missing release votes Has too many release candidates Has author tags in the code Discussions are happening off-list. Too much talk is happening on the private list. Users' questions are going unanswered on the mailing list. There is little or no activity on the mailing list. There are many GitHub or version control notifications on the mailing list. Building the project is challenging. Getting the LICENSE and NOTICE correct is difficult. The PMC is making releases without voting on them. The PMC members are not looking after the project's name and brand. No PMC members have been elected for a while No committers have been elected for a while. The project is having trouble attracting contributors. PMC members are not signed up to the private mailing list. The project has a benevolent dictator. A single company is controlling the direction of the project. Releases are not being placed in the ASF distribution system. The project is voting on too many things. PMC members have a conflict of interest. Conversations on the mailing list mainly occur in a language other than English. Only a few core people from one company are contributing code. > Sharpeners use cases > > > Key: COMDEV-543 > URL: https://issues.apache.org/jira/browse/COMDEV-543 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: use-cases.md > > > Brain dump of ideas for sharpeners use cases -- This message was sent by Atlassian Jira (v8.20.10#820010) - 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)
docusaurus is a good start for most project website. Nice change! On Sun, Feb 4, 2024, at 23:16, tison wrote: > Hi, > > I finally find some time to prepare a demo for the new website template [1]. > > It may still open to be improved including a download page template > and a community page template, as well as some guides as its docs. But > I'd like to first collecting feedback and finding which PMC is > responsible for this repository [2]. > > The background is that our current template is quite old and not > updated for the past six years. Few people understand those techniques > and have a hard time to build their own site. Also, new policy > compliance and new techniques benefits can be included in the template > to help new projects (podlings) build a wonderful site. > > I'm glad to maintain this repo but I find myself has no permission > over this repo. So again, which PMC is responsible for this > repository? > > Best, > tison. > > [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus > [2] https://github.com/apache/apache-website-template/ > > Alex Porcelli 于2024年1月30日周二 04:53写道： >> >> Another shout-out for tison and the Apache Fury to provide such a nice >> starting point for new websites. >> >> I managed to put, for now, a simple placeholder website for Apache KIE >> (incubation). >> >> Thank you tison and the Apache Fury community! >> >> On Fri, Jan 26, 2024 at 4:10 AM Xuanwo wrote: >> > >> > > I managed to move our old website to Docusaurus in one day - using the >> > > template >> > > structure from Fury, if you don’t mind. >> > >> > Congrats! >> > >> > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote: >> > > Hey tison, >> > > >> > > Thank you for the head-up. I managed to move our old website to >> > > Docusaurus in one day - using the template structure from Fury, if you >> > > don’t mind. Awesome stuff, would love when we’d had a template for the >> > > podlings to setup a good looking, SEO friendly project page. That’s >> > > needed to grow the community! >> > > >> > > Cheers, thanks again, >> > > —Alex >> > > >> > >> On Jan 25, 2024, at 12:01, tison wrote: >> > >> >> > >> Hi Alexander, >> > >> >> > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be >> > >> straightforward to follow already. The most simple one now is >> > >> https://github.com/apache/incubator-fury-site. >> > >> >> > >> Also, Docu is well-documented https://docusaurus.io/docs. >> > >> >> > >> I'm thinking of updating the website template [1] with Docu but have >> > >> not yet had time and understand which PMC manages this project. >> > >> >> > >> Best, >> > >> tison. >> > >> >> > >> [1] https://github.com/apache/apache-website-template >> > >> >> > >> Alexander Alten-Lorenz 于2024年1月25日周四 18:20写道： >> > >>> >> > >>> Hi Xuanwo, >> > >>> >> > >>> Thank you, highly appreciated! Do you have any how-to for setting >> > >>> Docusaurus up? >> > >>> >> > >>> —Alex >> > >>> >> > On Jan 25, 2024, at 11:01, Xuanwo wrote: >> > >> > Hi, alexander >> > >> > > We aren't web designers and we would love to find helping hands to >> > > get >> > > the page in order, including re-organizing and rewriting. >> > >> > I'm with the OpenDAL Community, and we also lack web designers. Our >> > community >> > opted for Docusaurus[1], which we found easy to start with and set >> > up. It >> > offers a decent theme suitable for open-source projects. For >> > reference, you >> > can check out OpenDAL's homepage[2]. We hope our experience proves >> > useful. >> > >> > [1] https://docusaurus.io/ >> > [2] https://opendal.apache.org/ >> > >> > On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote: >> > > Hi incubator community, >> > > >> > > Would anyone be willing to help the Wayang project with our website? >> > > We aren't web designers and we would love to find helping hands to >> > > get >> > > the page in order, including re-organizing and rewriting. >> > > >> > > thank you, cheers, >> > > --alexander >> > >> > -- >> > Xuanwo >> > -- >> > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org -- Xuanwo - 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)
+1, thanks for proposing this. docusaurus is very easy to use as a website template! On Wed, 14 Feb 2024 at 10:07, Xuanwo wrote: > > docusaurus is a good start for most project website. Nice change! > > On Sun, Feb 4, 2024, at 23:16, tison wrote: > > Hi, > > > > I finally find some time to prepare a demo for the new website template [1]. > > > > It may still open to be improved including a download page template > > and a community page template, as well as some guides as its docs. But > > I'd like to first collecting feedback and finding which PMC is > > responsible for this repository [2]. > > > > The background is that our current template is quite old and not > > updated for the past six years. Few people understand those techniques > > and have a hard time to build their own site. Also, new policy > > compliance and new techniques benefits can be included in the template > > to help new projects (podlings) build a wonderful site. > > > > I'm glad to maintain this repo but I find myself has no permission > > over this repo. So again, which PMC is responsible for this > > repository? > > > > Best, > > tison. > > > > [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus > > [2] https://github.com/apache/apache-website-template/ > > > > Alex Porcelli 于2024年1月30日周二 04:53写道： > >> > >> Another shout-out for tison and the Apache Fury to provide such a nice > >> starting point for new websites. > >> > >> I managed to put, for now, a simple placeholder website for Apache KIE > >> (incubation). > >> > >> Thank you tison and the Apache Fury community! > >> > >> On Fri, Jan 26, 2024 at 4:10 AM Xuanwo wrote: > >> > > >> > > I managed to move our old website to Docusaurus in one day - using the > >> > > template > >> > > structure from Fury, if you don’t mind. > >> > > >> > Congrats! > >> > > >> > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote: > >> > > Hey tison, > >> > > > >> > > Thank you for the head-up. I managed to move our old website to > >> > > Docusaurus in one day - using the template structure from Fury, if you > >> > > don’t mind. Awesome stuff, would love when we’d had a template for the > >> > > podlings to setup a good looking, SEO friendly project page. That’s > >> > > needed to grow the community! > >> > > > >> > > Cheers, thanks again, > >> > > —Alex > >> > > > >> > >> On Jan 25, 2024, at 12:01, tison wrote: > >> > >> > >> > >> Hi Alexander, > >> > >> > >> > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be > >> > >> straightforward to follow already. The most simple one now is > >> > >> https://github.com/apache/incubator-fury-site. > >> > >> > >> > >> Also, Docu is well-documented https://docusaurus.io/docs. > >> > >> > >> > >> I'm thinking of updating the website template [1] with Docu but have > >> > >> not yet had time and understand which PMC manages this project. > >> > >> > >> > >> Best, > >> > >> tison. > >> > >> > >> > >> [1] https://github.com/apache/apache-website-template > >> > >> > >> > >> Alexander Alten-Lorenz 于2024年1月25日周四 > >> > >> 18:20写道： > >> > >>> > >> > >>> Hi Xuanwo, > >> > >>> > >> > >>> Thank you, highly appreciated! Do you have any how-to for setting > >> > >>> Docusaurus up? > >> > >>> > >> > >>> —Alex > >> > >>> > >> > On Jan 25, 2024, at 11:01, Xuanwo wrote: > >> > > >> > Hi, alexander > >> > > >> > > We aren't web designers and we would love to find helping hands to > >> > > get > >> > > the page in order, including re-organizing and rewriting. > >> > > >> > I'm with the OpenDAL Community, and we also lack web designers. Our > >> > community > >> > opted for Docusaurus[1], which we found easy to start with and set > >> > up. It > >> > offers a decent theme suitable for open-source projects. For > >> > reference, you > >> > can check out OpenDAL's homepage[2]. We hope our experience proves > >> > useful. > >> > > >> > [1] https://docusaurus.io/ > >> > [2] https://opendal.apache.org/ > >> > > >> > On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote: > >> > > Hi incubator community, > >> > > > >> > > Would anyone be willing to help the Wayang project with our > >> > > website? > >> > > We aren't web designers and we would love to find helping hands to > >> > > get > >> > > the page in order, including re-organizing and rewriting. > >> > > > >> > > thank you, cheers, > >> > > --alexander > >> > > >> > -- > >> > Xuanwo > >> > -- > >> > Xuanwo > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail
