Re: [DISCUSSION] ComDev Event Participation for 2019
I'd like to volunteer to be a co-organizer for OSCON & Open Source Summit US & Mexico. On Tue, 22 Jan 2019 at 12:55, Sharan Foga wrote: > Hi Daniel > > I've already started to put together a wiki page > > https://s.apache.org/qz0d > > Once we have the main list, I think then we can then look at breaking it > down into various categories. At some events we have a track, at others we > have only a booth so we'll need to understand what we will get at each > event, and from there put a call out for volunteers. From the volunteers, > if we can identify lead co-ordinators for each event then that will help > share the work load. > > We will also need to think about budgeting too and how much to allocate to > spend for each event for stickers, swag etc because as with any budget - > there will be a limit. > > Anyway let's get the events logged and see what we can confirm, and then > take it from there. > > Thanks > Sharan > > > On 2019/01/22 14:52:12, Daniel Gruno wrote: > > On 1/22/19 1:52 PM, Griselda Cuevas wrote: > > > Hi all, I am revisiting the thread to confirm status and next steps.how > > > should we proceed? > > > > I think we need to get a document going where we can track both our > > options and confirmed engagements. This will lkely have to be linked to > > our fiscal years instead of calendar years. If no one beats me to it, I > > will set that up after FOSDEM. > > > > > > - > > 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: Swag inventory - what, where, how?
Hi Sharan - happy to discuss, how would you like to continue the convo? On Tue, 22 Jan 2019 at 13:06, Sharan Foga wrote: > Hi Gris > > I’ve been involved in ordering swag for various events. I'd be interested > in talking to you to understand more about what has been implemented for > Apache Beam. > > Thanks > Sharan > > On 2019/01/21 04:07:20, Griselda Cuevas wrote: > > Hi all, > > > > Reading through the convo it seems that we'll need to order some swag > soon > > and that we could benefit from inventory tracking. > > > > I'd like to suggest we talk with a vendor I use for Apache Beam swag, > they > > are called Pinnacle Branding, as part of the service they build a Shopify > > store and help us keep track of the inventory in a central instance. They > > also take care of the shipping when needed. They add options of approved > > swag and people request them when they need it. It would be a good way to > > centralize the process. > > > > If you think this would be interesting to explore de idea, I'm happy to > > make a proposal to the list and get things set up if this goes through. > > > > G > > > > On Sat, Jan 19, 2019, 10:02 AM Sharan Foga > > > > Hi Olivier > > > > > > I've updated the permissions so you should have access to edit the wiki > > > now. > > > > > > Thanks > > > Sharan > > > > > > On 2019/01/19 09:15:41, Olivier Heintz wrote: > > > > Sharan, > > > > > > > > Can you give me access for this page, I will update my inventory. > > > > > > > > Thanks > > > > Olivier > > > > > > > > Le 14/01/2019 à 20:15, Sharan Foga a écrit : > > > > > Hi > > > > > > > > > > The page Daniel R created is what I’ve been using and there > currently > > > isn’t really any inventory. The page does need updating so will do > that. > > > > > > > > > > Thanks > > > > > Sharan > > > > > > > > > > On 2019/01/14 13:35:09, Daniel Ruggeri > wrote: > > > > >> Hi, Daniel; > > > > >>While not as full featured as an inventory tracking system, I > did > > > start a cwiki page that a few people have participated in: > > > > >> > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=81789772 > > > > >> > > > > >> Does this help? > > > > >> -- > > > > >> Daniel Ruggeri > > > > >> > > > > >> On January 14, 2019 6:31:39 AM CST, Daniel Gruno < > > > humbed...@apache.org> wrote: > > > > >>> Hi folks, > > > > >>> this is just a generic query for starters; > > > > >>> > > > > >>> do we have any current way of keeping track of our inventory for > 3rd > > > > >>> party events, and if so where and how? > > > > >>> > > > > >>> If not, should we look into creating such a space? I'd probably > > > start > > > > >>> with some spreadsheets first and see if we can make do. Pierre > Smits > > > > >>> has > > > > >>> started some off-list conversations about an OFBiz instance for > > > > >>> tracking > > > > >>> things, but that would likely require a budget for the machine, > so > > > I'd > > > > >>> like to see if we can manage without it, or whether it makes the > most > > > > >>> sense. > > > > >>> > > > > >>> WDYT? > > > > >>> > > > > >>> With regards, > > > > >>> Daniel. > > > > >>> > > > > >>> > - > > > > >>> 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 > >
[jira] [Created] (COMDEV-308) GSoC - Allura - importers / sync for Bitbucket and Gitlab
Dave Brondsema created COMDEV-308: - Summary: GSoC - Allura - importers / sync for Bitbucket and Gitlab Key: COMDEV-308 URL: https://issues.apache.org/jira/browse/COMDEV-308 Project: Community Development Issue Type: Improvement Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura has a solid framework for doing imports, and has implemented this for services like GitHub, Google Code and Trac. It covers aspects from Git/Hg/SVN to tickets and wikis. It would be great to enhance this to support importing & converting data from Bitbucket and Gitlab. The level of integration & conversion may vary depending on the format and structure of the services. Beyond that, related improvements could be made in supporting ongoing synchronization of Git/Hg/SVN repositories (not just a one-time import). Or importers for JIRA, or improving importing of Allura's own formats. Everything in the ForgeImporters directory is our existing import system. The forgeimporters/base.py file has several base classes that provide common functionality for all importers to use. In the subdirectories "forge" "github" and "google" there are specific importers that can be good examples to reference. Importers can also be external packages, see these repos as more examples: [https://sourceforge.net/p/mediawikiimporter/git/ci/master/tree/] and [https://sourceforge.net/p/tracwikiimporter/git/ci/master/tree/] https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Proposed process for recognizing *Non-Technical* Contributions
Sally, this initiative is fantastic, thank you for articulating it and bringing it to life. This is a strong example that the ASF put community over code. re:Sharan's comments. I agree with the steps proposed, and here's how I'd like to contribute: 1) Drafting Guidelines and Process - Happy to contribute Guidelines for this, perhaps taking some of what I suggested for Beam [1]. I'm also interested in providing input for the process. Could we do this over a call or collaborative document? How should we proceed here? 2) Providing Support & Mentoring - I'm happy to become a mentor for new projects in the incubator and projects looking to expand their non-code contributors. Also happy to produce a slide deck on the importance of recognizing these contributions and how to build a process to do it. 3) Cleanup & Maintain Help Wanted - This is something I wasn't aware of and looks good! I'd love to help revamp this, it looks like a central-service repository for projects. I'd need to learn how to maintain it in the background and how we go about this. I agree with Sharan that we need to promote more the use of this and keep it clean and updated. I can help with this, but I won't have the bandwidth until March. >From this points - How should we move forward Sally? [1] https://lists.apache.org/thread.html/6a592632766d999d02922efab439348caa5c91da6e75eab2ab71f7ec@%3Cdev.beam.apache.org%3E On 2019/01/10 08:53:43, Sally Khudairi wrote: > Hello ComDev-ers! I hope you are all well and that your 2019 is looking > bright thus far. > > I wanted to share my proposal for recognizing non-technical contributions at > the ASF. Whilst some of us have spoken about this issue for many years, this > discussion formalized during ApacheCon Montreal (September 2018; select > excerpts at the end of this message) and moved onto the ASF Members list for > review and vetting. > > We have received both signoff from VP ComDev Sharan Foga, as well as careful > consideration and positive feedback from more than a dozen Members. > > Let's proceed! > > Proposed Contribution Process for Non-Technical tasks: > > 1) Contributions must be associated with an existing ASF project or > committee. For example: > > - Creating supporting graphics for ASF Marketing & Publicity > > - Providing marketing support for an Apache TLP > > - Onboarding new contributors to an Apache podling community > > - Developing a new Website for an existing project > > - Participating in Apache Community Development activities --staffing the > ASF booth, coordinating events, etc. > > - Writing project/process documentation > > - Helping with ASF Operations activities --legal/accounting support, etc. > > ...there are more ways folks can contribute. We just need to give them the > ability to do so. > > 2) The TLP/podling/committee involved must have at least one community member > (internal; e.g. PMC) to help provide guidance on the task/activity involved, > and at least three PMC Members who may be able to nominate the individual for > Committership, as per the ASF's established contributor > committer process > http://community.apache.org/contributors/index.html . > > 3) All project/committee participants are encouraged to sign an ASF ICLA in > order to have their contributions recognized. > > 4) Recognition must happen on-list. > > 5) All PMCs and podlings are encouraged to consider non-code contributions > and establish their own sub-processes for determining how to accept, > integrate, and recognize non-technical participation. > > 6) Recommend that a team of advisors for this process operate under ComDev, > and for any serious issues to be escalated to the ASF President and the > individuals identified in the ASF Code of Conduct who act as ombudspeople for > conflict resolution. > > 7) Recommend that all non-ASF-Member-confidential tasks/Requests for > Assistance be posted publicly on https://helpwanted.apache.org/ ...the form > makes it easy to do so! The related details on the tasks themselves may be > published on a project's JIRA, blog post, mailing list, Webpage, community > forum, Slack channel, etc. > > 8) Projects/committees are encouraged to share their initiatives with ASF > Marketing & Publicity for additional visibility across ASF > communication channels. > > ...as we build the program, I'm sure we'll be able to flesh out more details > and areas of activity. > > And to kick it off, ASF Marketing & Publicity have some graphics/creative > tasks that we will be leading as part of a "Central Services sub-group" under > our committee. We will be posting details on blogs.apache.org and promoted to > the greater community. Those who are creatively inclined and are able to help > are welcome to join us. > > I hope the proposed process will help encourage broader participation. In my > review with Sharan, she wrote: > > > ... this is just the sort of thing I think Comdev
[jira] [Created] (COMDEV-307) GSoC - Allura - responsive web pages
Dave Brondsema created COMDEV-307: - Summary: GSoC - Allura - responsive web pages Key: COMDEV-307 URL: https://issues.apache.org/jira/browse/COMDEV-307 Project: Community Development Issue Type: Improvement Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura's web frontend should be responsive. Initial prototyping work has begun using the Foundation framework: [https://foundation.zurb.com/sites/docs/] More initial work needs to be done to develop a reliable pattern, and then convert existing templates to use Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an intuitive way for all screen sizes. Interactivity via JS may need to be updated as well. Some more details are here [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-306) GSoC - Allura - Convert to python 3
[ https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Brondsema updated COMDEV-306: -- Component/s: GSoC/Mentoring ideas > GSoC - Allura - Convert to python 3 > --- > > Key: COMDEV-306 > URL: https://issues.apache.org/jira/browse/COMDEV-306 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2019, python > > Allura is a large mature codebase, and relies on many dependencies. The path > to python 3 will have many steps, but we need to start working on it. GSOC > work would include familiarizing with porting guides like > [https://docs.python.org/3/howto/pyporting.html] and > [https://portingguide.readthedocs.io/en/latest/] and > [http://python3porting.com/] and then working through steps like: > * upgrading dependencies, and updating code & tests to match > * removing or replacing dependencies where needed, and updating code > * running futurize or modernize, manual code changes where needed, cleanup, > etc > * testing > * documentation updates > * Docker updates > * more, probably :) > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-306) GSoC - Allura - Convert to python 3
Dave Brondsema created COMDEV-306: - Summary: GSoC - Allura - Convert to python 3 Key: COMDEV-306 URL: https://issues.apache.org/jira/browse/COMDEV-306 Project: Community Development Issue Type: Improvement Reporter: Dave Brondsema Allura is a large mature codebase, and relies on many dependencies. The path to python 3 will have many steps, but we need to start working on it. GSOC work would include familiarizing with porting guides like [https://docs.python.org/3/howto/pyporting.html] and [https://portingguide.readthedocs.io/en/latest/] and [http://python3porting.com/] and then working through steps like: * upgrading dependencies, and updating code & tests to match * removing or replacing dependencies where needed, and updating code * running futurize or modernize, manual code changes where needed, cleanup, etc * testing * documentation updates * Docker updates * more, probably :) https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755084#comment-16755084 ] Gimo commented on COMDEV-305: - Hi, I would like to work on this as my GSOC project. How should I get a head start? Thanks and Best Regards, Gimhana. > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755050#comment-16755050 ] Maxim Solodovnik commented on COMDEV-305: - sorry for the noise :( > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754938#comment-16754938 ] duheng commented on COMDEV-305: --- Sorry Maxim, RocketMQ's Jira has been closed :) > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754912#comment-16754912 ] duheng commented on COMDEV-305: --- Hi, Maxim, I created this issue according to the description in the email: Please use the COMDEV JIRA project for recording your ideas if your project doesn't use JIRA (e.g. httpd, ooo). > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754913#comment-16754913 ] Maxim Solodovnik commented on COMDEV-305: - [~duheng] There is [ROCKETMQ|https://issues.apache.org/jira/projects/ROCKETMQ] project in JIRA, this issue is also labeled RocketMQ, this is why I have asked > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng updated COMDEV-305: -- Labels: GSoc2019 RocketMQ (was: ) > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoc2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng updated COMDEV-305: -- Description: This is a project idea for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). We would like to extend the data replicator capabilities adding MongoDB / GridFS/Spark etc. as a new output connector for importing contents from one or more repositories supported by Apache RocketMQ. In this way, we will help developers on migrating contents from different data sources on different data system or computing system. You will be involved in the development of the following tasks, you will learn how to: * Write the RocketMQ connector implementation * Implement unit tests * Build all the integration tests for testing the connector inside the framework * Write the documentation for this connector Prospective GSOC mentor: vongosl...@apache.org was: This is a project idea for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). We would like to extend the data replicator capabilities adding MongoDB / GridFS/Spark etc. as a new output connector for importing contents from one or more repositories supported by Apache RocketMQ. In this way, we will help developers on migrating contents from different data sources on different data system or computing system. You will be involved in the development of the following tasks, you will learn how to: * Write the RocketMQ connector implementation * Implement unit tests * Build all the integration tests for testing the connector inside the framework * Write the documentation for this connector Prospective GSOC mentor: vongosl...@apache.org[|mailto:piergior...@apache.org] > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754905#comment-16754905 ] Maxim Solodovnik commented on COMDEV-305: - [~duheng] why are you creating COMDEV Jira and not [https://issues.apache.org/jira/projects/ROCKETMQ] ? > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng updated COMDEV-305: -- Description: This is a project idea for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). We would like to extend the data replicator capabilities adding MongoDB / GridFS/Spark etc. as a new output connector for importing contents from one or more repositories supported by Apache RocketMQ. In this way, we will help developers on migrating contents from different data sources on different data system or computing system. You will be involved in the development of the following tasks, you will learn how to: * Write the RocketMQ connector implementation * Implement unit tests * Build all the integration tests for testing the connector inside the framework * Write the documentation for this connector Prospective GSOC mentor: vongosl...@apache.org[|mailto:piergior...@apache.org] was: This is a project idea for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). We would like to extend the Content replicator capabilities adding MongoDB / GridFS/Spark etc. as a new output connector for importing contents from one or more repositories supported by Apache RocketMQ. In this way, we will help developers on migrating contents from different data sources on different data system or computing system. You will be involved in the development of the following tasks, you will learn how to: * Write the RocketMQ connector implementation * Implement unit tests * Build all the integration tests for testing the connector inside the framework * Write the documentation for this connector Prospective GSOC mentor: vongosling[@apache.org|mailto:piergior...@apache.org] > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org[|mailto:piergior...@apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
duheng created COMDEV-305: - Summary: GSoC2019 Apache RocketMQ Connector Project Key: COMDEV-305 URL: https://issues.apache.org/jira/browse/COMDEV-305 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng This is a project idea for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). We would like to extend the Content replicator capabilities adding MongoDB / GridFS/Spark etc. as a new output connector for importing contents from one or more repositories supported by Apache RocketMQ. In this way, we will help developers on migrating contents from different data sources on different data system or computing system. You will be involved in the development of the following tasks, you will learn how to: * Write the RocketMQ connector implementation * Implement unit tests * Build all the integration tests for testing the connector inside the framework * Write the documentation for this connector Prospective GSOC mentor: vongosling[@apache.org|mailto:piergior...@apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[ANNOUNCE] Apache Camel on Twitter
Hi all, I'd like to announce that the Apache Camel project now has an official Twitter account at @ApacheCamel (https://twitter.com/ApacheCamel). Please follow to receive news about the Camel project. On behalf of Apache Camel PMC, zoran -- Zoran Regvart - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Help with task: Ensure all Apache TLPs have Wikipedia pages
I would like to help out with the task listed at https://helpwanted.apache.org/task.html?0b349bee Im available call mick at 18168127179
