Re: [QUESTION] What should community do in GSoC timeline?
Thank you for the response! I now have a clearer understanding of how to participate in GSoC. On Wed, Mar 13, 2024, at 22:56, Lewis John McGibbney wrote: > Hi Xuanwo, > It’s been a few years since I participated in GSoC as a mentor… but > this year I intend to. Let me see if I can provide answers to some of > your questions. > > On 2024/03/11 03:07:29 Xuanwo wrote: >> >> 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? > > Mailing list is great however I don’t think there are any hard rules. > This period is really just for attracting interest in the initiative > (if it was created by the PMC/Committership) or convincing a PMC to > take on your initiative (if it was created by a potential GSoC student). > >> Q: Should student-submitted ideas/proposals be added to Jira? > > Yes absolutely. Make sure the JIRA issue is labeled with “gsoc2024” as > well. That way it will show up in the filter at > https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2024. > >> >> 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? >> > > > In short yes but really it is down to the mentor(s). It is always good > to have a backup mentor as well in-case the mentor is unable to see the > project through. > > HTH > lewismc > > ----- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org -- Xuanwo - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[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
Self Introduction - Xuanwo
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
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: [DISCUSS] How about hosting discourse as an alternative way for mailing list?
I did some research on discourse and found that it doesn't work as it described. Alought it can receive and create new topics from mailing list, but it can't send mails to mailing list when posts or replies created at discourse. This will make it a possible read-only archives of our mailing list, or just another platforms for discussion. So: **For read-only archives** The read-only archives will be like: https://rubytalk.org/. Users need to reply by email instead. **For another new platform** I don't think another new platform is a good idea. Personally, I'd rather not have to monitor an additional platform beyond the mailing list, GitHub, and Discord. **Other solutions?** We could also consider hosting a modern frontend for our mailing list, similar to Hyperkitty. For instance, take a look at: https://ml.ruby-lang.org/mailman3/hyperkitty/list/ruby-t...@ml.ruby-lang.org/ **Or just keep AS-IS** We can stick to our current communication methods if other options don't offer significant benefits. On Wed, Dec 20, 2023, at 00:31, Dinesh Joshi wrote: > Open an INFRA ticket on Jira. Thats one of the best ways to get answers. > > The infra user list doesn’t appear to be private. It requires a > subscription like most mailing lists to post. See > https://infra.apache.org/contact.html > > >> >> On Dec 19, 2023, at 5:38 AM, tison wrote: >> >> Hi Bowen, >> >> Thanks for your advice! I want to involve INFRA in the first place, >> but IIRC user@infra.a.o is private. >> >> Shall we invite INFRA members to this thread, or we start a new thread >> on user@infra.a.o? >> >> Best, >> tison. >> >> 于2023年12月19日周二 21:28写道： >>>> On Tue, 2023-12-19 at 19:23 +0800, tison wrote: >>>> +cc comdev >>>> Maybe you will be intested in this new type communication. >>> I would encourage you to take this up with Infra. I am certain that >>> this has come up before, and that Infra has already done some research >>> into Discourse, not only in terms of hosting it for projects, but for >>> the Foundation as a whole, and have thoughts about the sustainability >>> of doing this in individual VMs vs some kind of service provider. I >>> don't know what their advice will be, but they are definitely the right >>> folks to ask for that advice. >>>> Xuanwo 于2023年12月19日周二 19:15写道： >>>>>> Discourse will provide us an incoming email address. All email >>>>>> sent to >>>>>> this address will become a post in discourse. We need to add this >>>>>> address into the dev@o.a.o's subcriber list. >>>>> This is talking about Discourse SaaS which cost about $100 ($50 if >>>>> we have non-profit discount). >>>>> If we can request a vm from ASF Infra, we will need: >>>>> - VM with 4C8G >>>>> - Postgresql >>>>> - A SMTP account to send mails >>>>> - A domain like discuss.opendal.apache.org >>>>> On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote: >>>>>>> Does it need any configuration from the mailing list part, >>>>>>> i.e., >>>>>>> involve INFRA setup? >>>>>> Discourse will provide us an incoming email address. All email >>>>>> sent to >>>>>> this address will become a post in discourse. We need to add this >>>>>> address into the dev@o.a.o's subcriber list. >>>>>> No another setup needed, AFAIK. >>>>>> We need some test and demo to make sure everything works as >>>>>> expected. >>>>>> At the time of writing, I don't know how to do that. >>>>>> On Tue, Dec 19, 2023, at 18:19, tison wrote: >>>>>>>> called mailing list mode >>>>>>> Does it need any configuration from the mailing list part, >>>>>>> i.e., >>>>>>> involve INFRA setup? >>>>>>> I don't know how this happen but as long as we have a readable >>>>>>> copy on >>>>>>> the dev@ mailing list, other integration as view can be OK. >>>>>>> Best, >>>>>>> tison. >>>>>>> Jun Ouyang 于2023年12月19日周二 18:16写道： >>>>>>>> Hi xuanwo: >>>>>>>> That’s great! I strongly agree with this change. But I have a >>>>>>>> concern about >>>>>>>> markdown support sync to Maillist, It seems will cause more >>>>>>>> bad experiences >>>>>&
