Re: Regarding contribution
Hi Simran, Welcome to the community! The first thing you can do is find a project for yourself. In general, you can identify a project which interests you, - Go through its documentation/website - Then pick some newbie issues from Jira or GitHub - For any help, you can reach out to the respective project community. Project’s mailing list is the way to go. The list of projects is mentioned here: https://projects.apache.org/projects.html Do check out the below link on how to get involved: https://www.apache.org/foundation/getinvolved.html Hope that helps!!! On Thu, 9 Feb 2023 at 12:22, Simran Saini wrote: > > Greetings of the day, > I am interested to be a part of your organization . Can you please suggest > me some good first issues. > Simran - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] sebbASF commented on a diff in pull request #82: Update newcommitter.md
sebbASF commented on code in PR #82: URL: https://github.com/apache/comdev-site/pull/82#discussion_r1101225078 ## source/newcommitter.md: ## @@ -227,83 +237,50 @@ sent after a positive result from the vote for a new committer. Of course, you can decline and instead remain as a contributor, participating as you do now. -A. This personal invitation is a chance for you to -accept or decline in private. Either way, please -let us know in reply to the private@[PROJECT].apache.org -address only. +This personal invitation is a chance for you to accept or decline in private. +Please let us know in reply to this message whether you accept or decline. + +A. If you accept, you will need an Apache account (id) with privileges. Review Comment: The placing of the A. prefix does not really correspond with the sentence at B. -- 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: FOSDEM 2023 Update
On Tue, Feb 7, 2023 at 7:31 PM sharanf wrote: > > Hi Everyone > > I am back and still in the process of recovering from FOSDEM last > weekend so wanted to post a quick update. After two years of being an > online conference due to the pandemic it was great to get back to an in > person event...and FOSDEM excels at being an in person event. I can't > begin to describe how great it felt to be back behind the booth talking > to people about the foundation and our projects. I saw so many familiar > faces of people who keep coming back to say Hello! One guy showed me an > ASF branded USB extender that I gave him a few years ago at FOSDEM for > helping me out with a Kibble demo...:-) > > Now normally it rains in February. If there's one thing that seems > assured - it's rain at FOSDEM... well this time it was a little > different. I won't say it didn't rain (because it did) but not that > much. And even more unexpected was the sunshine ..Maybe the city > Brussels was happy to have an in person FOSDEM again too so put on some > good weather for us:-) > > Our booth has usually been on the first floor of K block right at the > top of the stairs but this time we were given a new location. We were on > the ground floor on the left hand side along by the windows. We were > also near to one the entry / exit doors. Our position meant that people > had to pass by us to get in or out - so we got a lot of foot traffic. > The FOSDEM team grouped foundations linked to Community Advocacy > together so we were alongside OpenUK, FOSSASIA, Software Freedom > Conservancy. FSFE, FOSSASIA, Ecliipse Foundation etc. > > On Saturday I arrived with the bag of swag to find a few people ready > and waiting to help out with setup. We quickly put up the banner (it > definitely needed two people!), blew up some balloons and got the booth > table covered in stickers (So much so that during the event people came > to take photos of our display). We kept telling people that this was > only a small selection of ASF projects. Even so - we did have requests > for stickers we didn't have (so they are on my list for next time). Also > we ran out of the HTTP Server stickers (everyone wanted a sticker of the > first ASF project). We ran out of stickers for Apache Maven, Apache > Kafka this time. > > As well as stickers we gave away some balloons for the children (and > some adults too), cleaning cloths for glasses and screens, mugs, head > tubes, pens, small cable bags, key rings and mask extenders (as there > were a few people with masks). The cleaning cloths were very popular - > everyone wearing glasses seemed to want one. > > For the things that we had limited supply of - we told people that to > get one would cost 'a good conversation' :-) So we had some really good > conversations - about projects, technology and I think even open source > software for space technology! This is one of the reasons that having a > booth presence is so good for outreach and general community building. > > People also came to talk to us about other open source events that were > being organised that they hoped we or our communities might be > interested in participating in. One of these was the Open System Days > Croation Linux Users Conference who have a CFP open > https://www.dorscluc.org/call-for-speakers/. We also offered a free > meeting room for community meetups for any developers based in and > around Portugal. > > We had people from different projects spend some time on the booth - so > special shoutout and huge thanks to Claude Warren, Matthew de > Detrich, Arnout Engelen, Myrle Krantz, Jarek Potiuk, Gilles Sadowski, > Johan Corveleyn, Jean-Frederic Clere, Herve Boutemy for helping out on > the booth. Thanks also to everyone that dropped by to say Hi and chat > -it was all fun. > > There were rumours of 1 attending people but nothing concrete. > Usually FOSDEM attracts over 8000 developers. Whatever the number there > seemed to be an endless stream of people, there were lots of people at > the foodcarts, on the first and second floors, walking to and from the > other buildings and going in and out of the talks. I understand that > many of the talks have been recorded so if you didn't make it then you > will still get a chance to see it. If you have never experienced FOSDEM > then I would encourage you to keep it on your radar and see if you can > make it to the next one. > > Once again I would like to sincerely thank everyone that was involved in > helping out to make our participation at FOSDEM a success. Am already > looking forward to doing it all again next year if we get the chance. > > Please feel free to respond with any of your FOSDEM experiences, > feedback, thoughts or general comments! > > Thanks > Sharan Thanks a lot Sharan for all your hard work and dedication. It was my first time at FOSDEM so I was a little overwhelmed by the busy and rather chaotic flow, but it was a lot of fun :-). Especially at the ASF booth! Although I'm an ASF
[jira] [Updated] (COMDEV-439) GSOC: Varnish Cache support in Apache Traffic Control
[ https://issues.apache.org/jira/browse/COMDEV-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Friedrich updated COMDEV-439: -- Labels: TrafficControl full-time gsoc2023 mentor (was: TrafficControl full-time gsoc2022 mentor) > GSOC: Varnish Cache support in Apache Traffic Control > - > > Key: COMDEV-439 > URL: https://issues.apache.org/jira/browse/COMDEV-439 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Eric Friedrich >Priority: Major > Labels: TrafficControl, full-time, gsoc2023, mentor > > *Background* > Apache Traffic Control is a Content Delivery Network (CDN) control plane for > large scale content distribution. > Traffic Control currently requires Apache Traffic Server as the underlying > cache. Help us expand the scope by integrating with the very popular Varnish > Cache. > There are multiple aspects to this project: > - Configuration Generation: Write software to build Varnish configuration > files (VCL). This code will be implemented in our Traffic Ops and cache > client side utilities, both written in Go. > - Health Monitoring: Implement monitoring of the Varnish cache health and > performance. This code will run both in the Traffic Monitor component and > within Varnish. Traffic Monitor is written in Go and Varnish is written in C. > - Testing: Adding automated tests for new code > *Skills:* > - Proficiency in Go is required > - A basic knowledge of HTTP and caching is preferred, but not required for > this project. -- 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] [Created] (COMDEV-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
Nicolás Vázquez created COMDEV-483: -- Summary: CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor Key: COMDEV-483 URL: https://issues.apache.org/jira/browse/COMDEV-483 Project: Community Development Issue Type: New Feature Reporter: Nicolás Vázquez Github issue: [https://github.com/apache/cloudstack/issues/7127] Description: The Import-Export functionality is only allowed for the Vmware hypervisor. The functionality is developed within a VM ingestion framework that allows the extension to other hypervisors. The Import-Export functionality consists on few APIs and the UI to interact with them: * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in CloudStack but existing on the hypervisor side) * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this implies populating the database with the corresponding data) * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it on the hypervisor side The complexity on KVM should be parsing the existing XML domains into different resources and map them in CloudStack to populate the database correctly. -- 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] [Updated] (COMDEV-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
[ https://issues.apache.org/jira/browse/COMDEV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolás Vázquez updated COMDEV-483: --- Component/s: GSoC/Mentoring ideas > CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor > --- > > Key: COMDEV-483 > URL: https://issues.apache.org/jira/browse/COMDEV-483 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Nicolás Vázquez >Priority: Major > Labels: gsoc2023 > > Github issue: [https://github.com/apache/cloudstack/issues/7127] > > Description: > The Import-Export functionality is only allowed for the Vmware hypervisor. > The functionality is developed within a VM ingestion framework that allows > the extension to other hypervisors. The Import-Export functionality consists > on few APIs and the UI to interact with them: > * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in > CloudStack but existing on the hypervisor side) > * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this > implies populating the database with the corresponding data) > * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it > on the hypervisor side > The complexity on KVM should be parsing the existing XML domains into > different resources and map them in CloudStack to populate the database > correctly. -- 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-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
[ https://issues.apache.org/jira/browse/COMDEV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolás Vázquez closed COMDEV-483. -- Resolution: Invalid > CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor > --- > > Key: COMDEV-483 > URL: https://issues.apache.org/jira/browse/COMDEV-483 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Nicolás Vázquez >Priority: Major > Labels: gsoc2023 > > Github issue: [https://github.com/apache/cloudstack/issues/7127] > > Description: > The Import-Export functionality is only allowed for the Vmware hypervisor. > The functionality is developed within a VM ingestion framework that allows > the extension to other hypervisors. The Import-Export functionality consists > on few APIs and the UI to interact with them: > * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in > CloudStack but existing on the hypervisor side) > * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this > implies populating the database with the corresponding data) > * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it > on the hypervisor side > The complexity on KVM should be parsing the existing XML domains into > different resources and map them in CloudStack to populate the database > correctly. -- 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
[GitHub] [comdev-site] clr-apache commented on a diff in pull request #82: Update newcommitter.md
clr-apache commented on code in PR #82: URL: https://github.com/apache/comdev-site/pull/82#discussion_r1101679831 ## source/newcommitter.md: ## @@ -227,83 +237,50 @@ sent after a positive result from the vote for a new committer. Of course, you can decline and instead remain as a contributor, participating as you do now. -A. This personal invitation is a chance for you to -accept or decline in private. Either way, please -let us know in reply to the private@[PROJECT].apache.org -address only. +This personal invitation is a chance for you to accept or decline in private. +Please let us know in reply to this message whether you accept or decline. + +A. If you accept, you will need an Apache account (id) with privileges. Review Comment: Yes, I've updated the instructions. A is if you have an ICLA on file. B is if you need to file an ICLA. Thanks for the comments. -- 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
[jira] [Commented] (COMDEV-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
[ https://issues.apache.org/jira/browse/COMDEV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686622#comment-17686622 ] Maxim Solodovnik commented on COMDEV-483: - [~nvazquez] why this JIRA is closed? :))) > CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor > --- > > Key: COMDEV-483 > URL: https://issues.apache.org/jira/browse/COMDEV-483 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Nicolás Vázquez >Priority: Major > Labels: gsoc2023 > > Github issue: [https://github.com/apache/cloudstack/issues/7127] > > Description: > The Import-Export functionality is only allowed for the Vmware hypervisor. > The functionality is developed within a VM ingestion framework that allows > the extension to other hypervisors. The Import-Export functionality consists > on few APIs and the UI to interact with them: > * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in > CloudStack but existing on the hypervisor side) > * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this > implies populating the database with the corresponding data) > * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it > on the hypervisor side > The complexity on KVM should be parsing the existing XML domains into > different resources and map them in CloudStack to populate the database > correctly. -- 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-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
[ https://issues.apache.org/jira/browse/COMDEV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1768#comment-1768 ] Nicolás Vázquez commented on COMDEV-483: HI [~solomax] I had initially created under the Comdev project instead of CloudStack, closed it in favour of: https://issues.apache.org/jira/browse/CLOUDSTACK-10456 > CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor > --- > > Key: COMDEV-483 > URL: https://issues.apache.org/jira/browse/COMDEV-483 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Nicolás Vázquez >Priority: Major > Labels: gsoc2023 > > Github issue: [https://github.com/apache/cloudstack/issues/7127] > > Description: > The Import-Export functionality is only allowed for the Vmware hypervisor. > The functionality is developed within a VM ingestion framework that allows > the extension to other hypervisors. The Import-Export functionality consists > on few APIs and the UI to interact with them: > * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in > CloudStack but existing on the hypervisor side) > * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this > implies populating the database with the corresponding data) > * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it > on the hypervisor side > The complexity on KVM should be parsing the existing XML domains into > different resources and map them in CloudStack to populate the database > correctly. -- 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: Regarding contribution
What do you mean my friend? Sent from my Galaxy Original message From: Simran Saini Date: 9/2/23 4:52 pm (GMT+10:00) To: dev@community.apache.org Subject: Regarding contribution Greetings of the day, I am interested to be a part of your organization . Can you please suggest me some good first issues. Simran
[jira] [Created] (COMDEV-484) [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the Apache Beam SDKs
Pablo Estrada created COMDEV-484: Summary: [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the Apache Beam SDKs Key: COMDEV-484 URL: https://issues.apache.org/jira/browse/COMDEV-484 Project: Community Development Issue Type: Task Components: GSoC/Mentoring ideas Reporter: Pablo Estrada Beam library developers and Beam users would appreciate this : ) -- 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] [Updated] (COMDEV-484) [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the Apache Beam SDKs
[ https://issues.apache.org/jira/browse/COMDEV-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pablo Estrada updated COMDEV-484: - Description: Beam library developers and Beam users would appreciate this : ) This project involves prototyping a few different solutions, so it will be large. was:Beam library developers and Beam users would appreciate this : ) Labels: gsoc gsoc2023 large (was: gsoc gsoc2023) > [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the > Apache Beam SDKs > - > > Key: COMDEV-484 > URL: https://issues.apache.org/jira/browse/COMDEV-484 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Pablo Estrada >Priority: Major > Labels: gsoc, gsoc2023, large > > Beam library developers and Beam users would appreciate this : ) > > This project involves prototyping a few different solutions, so it will be > large. -- 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] [Updated] (COMDEV-484) [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the Apache Beam SDKs
[ https://issues.apache.org/jira/browse/COMDEV-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-484: Labels: Beam full-time gsoc gsoc2023 (was: gsoc gsoc2023 large) > [GSoC][Beam] An IntelliJ plugin to develop Apache Beam pipelines and the > Apache Beam SDKs > - > > Key: COMDEV-484 > URL: https://issues.apache.org/jira/browse/COMDEV-484 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Pablo Estrada >Priority: Major > Labels: Beam, full-time, gsoc, gsoc2023 > > Beam library developers and Beam users would appreciate this : ) > > This project involves prototyping a few different solutions, so it will be > large. -- 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-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
[ https://issues.apache.org/jira/browse/COMDEV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686860#comment-17686860 ] Maxim Solodovnik commented on COMDEV-483: - Understood :) Thanks for clarifications [~nvazquez], Ideas page is updated :)) > CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor > --- > > Key: COMDEV-483 > URL: https://issues.apache.org/jira/browse/COMDEV-483 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Nicolás Vázquez >Priority: Major > Labels: gsoc2023 > > Github issue: [https://github.com/apache/cloudstack/issues/7127] > > Description: > The Import-Export functionality is only allowed for the Vmware hypervisor. > The functionality is developed within a VM ingestion framework that allows > the extension to other hypervisors. The Import-Export functionality consists > on few APIs and the UI to interact with them: > * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in > CloudStack but existing on the hypervisor side) > * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this > implies populating the database with the corresponding data) > * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it > on the hypervisor side > The complexity on KVM should be parsing the existing XML domains into > different resources and map them in CloudStack to populate the database > correctly. -- 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
