[QUESTION] What should community do in GSoC timeline?
Hello, everyone This is the first year that both I and the OpenDAL community are participating in GSoC. I'm somewhat confused about when and how our community fits into the GSoC timeline. I'll ask questions throughout the timeline, collect them into an FAQ, and submit a PR to the GSoC site if others have similar questions. 2024-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations Q: Should those ideas/proposals been posted to mailing list? Or just discuss with mentors? Q: Should student-submitted ideas/proposals be added to Jira? 2024-04-15: Proposals to ASF projects must be reviewed roughly and have a potential mentor so that we know how many slots to request. Q: Who will review/rank/score those proposals? The corresponding community's PMC? Xuanwo - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: How to build the community page?
Yep, it is a version issue. We need to fix it for the latest hugo version
and we just downgrade the version in GitHub Actions to make the website
built successfully.
On Sun, Mar 10, 2024 at 2:04 PM tison wrote:
> Locate and fix - https://github.com/apache/comdev-site/pull/161
>
> Best,
> tison.
>
>
> tison 于2024年3月10日周日 00:05写道：
>
> > Hi,
> >
> > The README file writes: run `hugo` to get the static content.
> >
> > I got:
> >
> > $ hugo
> > Start building sites …
> > hugo v0.123.8-5fed9c591b694f314e5939548e11cc3dcb79a79c+extended
> > darwin/arm64 BuildDate=2024-03-07T13:14:42Z VendorInfo=brew
> >
> > ERROR render of "section" failed:
> > "/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
> > execute of template failed: template: _default/list.html:87:13: executing
> > "_default/list.html" at : error calling
> > partial:
> >
> "/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
> > execute of template failed: template: partials/website-source.html:5:86:
> > executing "partials/website-source.html" at <.Page.File.Path>: error
> > calling Path: runtime error: invalid memory address or nil pointer
> > dereference
> > Total in 77 ms
> > Error: error building site: render: failed to render pages: render of
> > "section" failed:
> > "/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
> > execute of template failed: template: _default/list.html:87:13: executing
> > "_default/list.html" – File is nil; wrap it in if or with: {{ with
> partial
> > "website-source.html" .>: error calling partial:
> >
> "/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
> > execute of template failed: template: partials/website-source.html:5:86:
> > executing "partials/website-source.html" at <.Page.File }}{{ .Path }}{{
> end
> > }}
> >
> > Is the version the issue or I miss some steps?
> >
> > Best,
> > tison.
> >
>
Re: Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52
My mistake, thanks for the tip! Okay, great, glad to hear it's expected behavior. Best, Dan On Sun, Mar 10, 2024 at 7:35 PM Daniel Gruno wrote: > On 3/10/24 21:02, Dan Liebner wrote: > > This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 > > according to my audit log. It goes away when apache2 is stopped. It > > originally showed up in a rkhunter scan. I can't find any information > about > > it online except for similar reports. Is this likely a legitimate file > > created by apache or possibly malware of some kind? > > > > Thanks, > > Dan > > > > Hi, Dan, > > You should probably contact us...@httpd.apache.org if you have httpd > related questions in the future. For what it's worth, SHM refers to > "shared memory", and /dev/shm/ is used for storing pointers to memory > that is to be shared between two applications (in this case, between the > various root/worker processes in httpd) > > With regards, > Daniel. >
Re: Self Introduction - Xuanwo
Hi Xuanwo， Welcome to join the ComDev community. I'm looking forward to working with you :) Cheers, Willem Jiang On Sun, Mar 10, 2024 at 1:21 PM Xuanwo wrote: > > Hello, everyone > > I'm Xuanwo, and I'm following the "Contribute" guide in > comdev-working-groups[1] to introduce myself and kickstart my contributions :) > > My personal vision is "Empowering freely data access from ANY storage service > in ANY method". Open source is definitely an important part of achieving my > vision. > > - I'm the PMC Chair for Apache OpenDAL [2], a project that graduated in > January 2024, aimed at enabling free data access. > - I work at Databend Labs [3], focusing on cost-effective data analysis. > - I'm also contributing to Apache Iceberg [4] to simplify reading SQL tables. > > My current interest lies in open source sustainability. I want to learn how > to ensure a project's sustainability and foster community growth. I'm here to > explore how I can contribute to expanding the ASF community. > > Pleased to meet you here; I'm looking forward to working together with you. > > [1]: https://github.com/apache/comdev-working-groups > [2]: https://github.com/apache/opendal > [3]: https://github.com/datafuselabs/databend/ > [4]: https://github.com/apache/iceberg-rust > > Xuanwo > > - > 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: Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52
On 3/10/24 21:02, Dan Liebner wrote: This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 according to my audit log. It goes away when apache2 is stopped. It originally showed up in a rkhunter scan. I can't find any information about it online except for similar reports. Is this likely a legitimate file created by apache or possibly malware of some kind? Thanks, Dan Hi, Dan, You should probably contact us...@httpd.apache.org if you have httpd related questions in the future. For what it's worth, SHM refers to "shared memory", and /dev/shm/ is used for storing pointers to memory that is to be shared between two applications (in this case, between the various root/worker processes in httpd) With regards, Daniel. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52
This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 according to my audit log. It goes away when apache2 is stopped. It originally showed up in a rkhunter scan. I can't find any information about it online except for similar reports. Is this likely a legitimate file created by apache or possibly malware of some kind? Thanks, Dan
Re: [WG: Badging] Tooling
Apologies Paulo if that was. I have indeed missed that this is a public list. But - for my excuse - I should have taken Airflow as an example because we discussed it in public lists (and I had not realized it should have been secret) So let me re-cast my considerations here: * Astronomer runs https://www.astronomer.io/champions/ "The Astronomer Champions Program for Apache Airflow" - with all the trademarks reviews, and nominative use of Airflow as expected by Trademarks and our policies, * It's run by Astronomer and it's cool for the community, it has no PMC involvement at all (besides that we know about it) - to avoid the feeling that it's a "PMC" thing - some of the people are already posting blogs and having talks at our "Monthly Town Hall meetings" This is all cool and great, but we can't make it a PMC "badging" program as it is not run by the PMC. Having said that - it would be cool if we have (providing it's "ASF recognized" - similar badging program for Airflow. That's the gist of what I wanted to say - and yes, the Airflow example here is much better as a context for this discussion. J. On Sun, Mar 10, 2024 at 3:47 PM Paulo Motta wrote: > As a member of the Cassandra community I did not appreciate internal > project matters being brought to a public mailing list without prior > consent. This does not help re-establishing trust of the project with ASF > leadership to work on common projects. Please start a new thread with > priv...@cassandra.apache.org if you would like to continue this > discussion. > > Going back to the main topic of the working group, I do not think badges > should exist for ASF members, committers or PMCs for two reasons: > 1) This will create confusion with ASF roles. > 2) Badges should celebrate achievements and not roles. > > I'm OK with an Advisor badge if they are associated with a concrete > achievement, and not to indicate a role. > > On Sat, Mar 9, 2024 at 6:27 PM Paulo Motta wrote: > > > Hi Jarek, > > > > You raised interesting discussion points but I would prefer not to > discuss > > specific examples in a public mailing list, since they may spark > > unnecessary controversy and derail from the focus of the working group. > > > > Do you mind summarizing your key considerations without mentioning > > specific projects or vendors ? > > > > Thanks! > > > > Paulo > > On Sat, 9 Mar 2024 at 10:35 Jarek Potiuk wrote: > > > >> I like the idea of having "A" badging system that is seen as "ASF > >> accepted" that any PMC (at PMC level) or any person (at ASF level) > >> might opt-in to use > >> > >> I think such badging system - providing that it's "ASF generally > >> accepted" concept that is defined well - possibly adopted from others > >> like Fedora has this nice property that it will potentially disarm > >> attempts by the vendors to define their own "badging system" that > >> might have some properties that are unwanted by the ASF. > >> > >> Without judging the intentions - we had this drama about Cassandra MVP > >> - which was no more, no less - Cassandra driven badging system that > >> they defined and PMC wanted to adopt it. IMHO this is what it really > >> was about. Putting a "label" on people following some process and > >> conditions, so that those people (and the community) can attach some > >> value to. That's what the badging system is, and that's what the MVP > >> program of Cassandra essentially was. > >> > >> Again - absolutely without judging the intentions that happened in > >> Cassandra's case. If we had our own "ASF recognised" badging system, > >> we could very easily funnel any kind of attempts to do similar badging > >> program into "Here is the badging system we use in ASF - take this one > >> and use it, maybe adapt it a bit - within the limits it provides and > >> you are done". If any stakeholder wants to run their own program - > >> (say Datastax MVP program for Cassandra) -they can still do it, no > >> problem. > >> > >> But if the PMC wants to do something like that, using something that > >> is not only recognised in ASF but also potentially can bring some. > >> synergies (ASF level badges on top of PMC-level ones for example). > >> > >> There are really interesting synergies possible. For example - one > >> could come up with an "ASF Advisor" badge as a way to recognise people > >> who take part in the other comdev working group initiative - Advisors. > >> Or even plain and simple "ASF member" badge. Having a few badges on > >> the ASF level mixed with those on PMC level in a single place > >> (providing that PMC will start using their own labels) might also be a > >> way how to bring the PMCs closer to the ASF on more-or-less daily > >> interactions. > >> > >> I imagine for example a new contributor asking such a question: "Hey I > >> see on top of being the ' mentor' label, you have the 'ASF > >> Advisor' and 'ASF member' - can you explain what it means?" - If such > >> labels would be visible, and promoted by the PMC in
Re: [WG: Badging] Tooling
As a member of the Cassandra community I did not appreciate internal project matters being brought to a public mailing list without prior consent. This does not help re-establishing trust of the project with ASF leadership to work on common projects. Please start a new thread with priv...@cassandra.apache.org if you would like to continue this discussion. Going back to the main topic of the working group, I do not think badges should exist for ASF members, committers or PMCs for two reasons: 1) This will create confusion with ASF roles. 2) Badges should celebrate achievements and not roles. I'm OK with an Advisor badge if they are associated with a concrete achievement, and not to indicate a role. On Sat, Mar 9, 2024 at 6:27 PM Paulo Motta wrote: > Hi Jarek, > > You raised interesting discussion points but I would prefer not to discuss > specific examples in a public mailing list, since they may spark > unnecessary controversy and derail from the focus of the working group. > > Do you mind summarizing your key considerations without mentioning > specific projects or vendors ? > > Thanks! > > Paulo > On Sat, 9 Mar 2024 at 10:35 Jarek Potiuk wrote: > >> I like the idea of having "A" badging system that is seen as "ASF >> accepted" that any PMC (at PMC level) or any person (at ASF level) >> might opt-in to use >> >> I think such badging system - providing that it's "ASF generally >> accepted" concept that is defined well - possibly adopted from others >> like Fedora has this nice property that it will potentially disarm >> attempts by the vendors to define their own "badging system" that >> might have some properties that are unwanted by the ASF. >> >> Without judging the intentions - we had this drama about Cassandra MVP >> - which was no more, no less - Cassandra driven badging system that >> they defined and PMC wanted to adopt it. IMHO this is what it really >> was about. Putting a "label" on people following some process and >> conditions, so that those people (and the community) can attach some >> value to. That's what the badging system is, and that's what the MVP >> program of Cassandra essentially was. >> >> Again - absolutely without judging the intentions that happened in >> Cassandra's case. If we had our own "ASF recognised" badging system, >> we could very easily funnel any kind of attempts to do similar badging >> program into "Here is the badging system we use in ASF - take this one >> and use it, maybe adapt it a bit - within the limits it provides and >> you are done". If any stakeholder wants to run their own program - >> (say Datastax MVP program for Cassandra) -they can still do it, no >> problem. >> >> But if the PMC wants to do something like that, using something that >> is not only recognised in ASF but also potentially can bring some. >> synergies (ASF level badges on top of PMC-level ones for example). >> >> There are really interesting synergies possible. For example - one >> could come up with an "ASF Advisor" badge as a way to recognise people >> who take part in the other comdev working group initiative - Advisors. >> Or even plain and simple "ASF member" badge. Having a few badges on >> the ASF level mixed with those on PMC level in a single place >> (providing that PMC will start using their own labels) might also be a >> way how to bring the PMCs closer to the ASF on more-or-less daily >> interactions. >> >> I imagine for example a new contributor asking such a question: "Hey I >> see on top of being the ' mentor' label, you have the 'ASF >> Advisor' and 'ASF member' - can you explain what it means?" - If such >> labels would be visible, and promoted by the PMC in their >> communication, newsletters, it would be a great opportunity to "bind" >> the ASF community together. >> >> Of course it won't happen overnight, but starting with "choosing" the >> right badging system and making it easy for PMCs and persons to opt in >> is absolutely necessary to try it out. >> >> J. >> >> On Sat, Mar 9, 2024 at 2:35 PM Andrew Wetmore >> wrote: >> > >> > Can I have the 'not badging' badge? >> > >> > On Sat, Mar 9, 2024 at 9:16 AM Gary Gregory >> wrote: >> > >> > > Here is a hopefully entertaining story about gaming a system: >> > > >> > > A long time ago (not in a galaxy far away), I worked for a company >> that >> > > created an internal $ bug bounty as a major release of our flagship >> product >> > > neared. Someone in QA found a bug that caused the language runtime to >> > > incorrectly print to the console integers. That person created one >> ticket >> > > for each of the numbers affected, 1, 2 and so forth until it >> obviously all >> > > went very sideways for that person. Fun! >> > > >> > > Gary >> > > >> > > On Sat, Mar 9, 2024, 7:17 AM Paulo Motta wrote: >> > > >> > > > Apologies if the previous message sounded snarky - it was late and I >> > > > impulsively cherry-picked some excerpts to comment without much >> second >> > > > thought. :-) >> > > > >> > > > A more
