[jira] [Commented] (COMDEV-451) Apache APISIX: Java Plugin Runner Improvement
[
https://issues.apache.org/jira/browse/COMDEV-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17517831#comment-17517831
]
Bobur Umurzokov commented on COMDEV-451:
[~erikiceliu] Hi Eric,
Sure, you are welcome to provide a project proposal until the 19th of April,
2022.
Thanks!
> Apache APISIX: Java Plugin Runner Improvement
> -
>
> Key: COMDEV-451
> URL: https://issues.apache.org/jira/browse/COMDEV-451
> Project: Community Development
> Issue Type: New Feature
> Components: GSoC/Mentoring ideas
>Reporter: Bobur Umurzokov
>Priority: Major
> Labels: APISIX, full-time, gsoc2022
>
> *Background:*
>
> At the moment, the Java runner plugin requires you to use an existing
> template project and change it according to one’s needs.
> *Task:*
> Improve developer experience on the existing Java plugin runner so that we
> can attract and increase the number of users from the Java community.
> *Limitations:*
> * The architecture doesn’t manage multiple plugins. All need to be set in
> the same project
> * The standard Java unit of deployment is the JAR.
> * The plugin doesn’t allow for other widespread JVM-based languages
> ({_}e.g.{_}, Scala, Kotlin, Clojure, Groovy). Though it would be technically
> feasible, we would need to change the template’s language
> *Requirements:*
> The new plugin runner:
> * MUST use the JAR as the unit of deployment
> * MUST not require the usage of a project template
> * MAY require the plugin to follow a certain class hierarchy ({_}i.e.{_},
> extends JavaPlugin)
> * MAY use a more specific format to enforce a structure
> * MUST allow multiple plugins to be deployed
> * MUST use isolated classloader for each plugin
> * MUST allow any JVM-compatible bytecode to run, whatever the language it
> was generated from
> * MAY allow hot reloading of Java plugins
> * MAY require a single JAR per plugin (to ease the classpath management of
> shared libraries)
> * MUST define a minimum JVM version
>
> *Difficulty:* Normal
> *Project size:* ~350 hours.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-451) Apache APISIX: Java Plugin Runner Improvement
[
https://issues.apache.org/jira/browse/COMDEV-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17517726#comment-17517726
]
Eric Liu commented on COMDEV-451:
-
[~bumurzokov] [~tzssangglass] Hi, I would like to work on this issue. I will
get started with drafting a project proposal. I'll share it when it is ready!
> Apache APISIX: Java Plugin Runner Improvement
> -
>
> Key: COMDEV-451
> URL: https://issues.apache.org/jira/browse/COMDEV-451
> Project: Community Development
> Issue Type: New Feature
> Components: GSoC/Mentoring ideas
>Reporter: Bobur Umurzokov
>Priority: Major
> Labels: APISIX, full-time, gsoc2022
>
> *Background:*
>
> At the moment, the Java runner plugin requires you to use an existing
> template project and change it according to one’s needs.
> *Task:*
> Improve developer experience on the existing Java plugin runner so that we
> can attract and increase the number of users from the Java community.
> *Limitations:*
> * The architecture doesn’t manage multiple plugins. All need to be set in
> the same project
> * The standard Java unit of deployment is the JAR.
> * The plugin doesn’t allow for other widespread JVM-based languages
> ({_}e.g.{_}, Scala, Kotlin, Clojure, Groovy). Though it would be technically
> feasible, we would need to change the template’s language
> *Requirements:*
> The new plugin runner:
> * MUST use the JAR as the unit of deployment
> * MUST not require the usage of a project template
> * MAY require the plugin to follow a certain class hierarchy ({_}i.e.{_},
> extends JavaPlugin)
> * MAY use a more specific format to enforce a structure
> * MUST allow multiple plugins to be deployed
> * MUST use isolated classloader for each plugin
> * MUST allow any JVM-compatible bytecode to run, whatever the language it
> was generated from
> * MAY allow hot reloading of Java plugins
> * MAY require a single JAR per plugin (to ease the classpath management of
> shared libraries)
> * MUST define a minimum JVM version
>
> *Difficulty:* Normal
> *Project size:* ~350 hours.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] (COMDEV-451) Apache APISIX: Java Plugin Runner Improvement
[ https://issues.apache.org/jira/browse/COMDEV-451 ]
Eric Liu deleted comment on COMDEV-451:
-
was (Author: JIRAUSER287639):
[~tzssangglass] [~bumurzokov] Hi, I would like to work on this issue as part of
GSOC 2022. Is it still up for grabs? Should I start working on a draft proposal
to share with you guys?
> Apache APISIX: Java Plugin Runner Improvement
> -
>
> Key: COMDEV-451
> URL: https://issues.apache.org/jira/browse/COMDEV-451
> Project: Community Development
> Issue Type: New Feature
> Components: GSoC/Mentoring ideas
>Reporter: Bobur Umurzokov
>Priority: Major
> Labels: APISIX, full-time, gsoc2022
>
> *Background:*
>
> At the moment, the Java runner plugin requires you to use an existing
> template project and change it according to one’s needs.
> *Task:*
> Improve developer experience on the existing Java plugin runner so that we
> can attract and increase the number of users from the Java community.
> *Limitations:*
> * The architecture doesn’t manage multiple plugins. All need to be set in
> the same project
> * The standard Java unit of deployment is the JAR.
> * The plugin doesn’t allow for other widespread JVM-based languages
> ({_}e.g.{_}, Scala, Kotlin, Clojure, Groovy). Though it would be technically
> feasible, we would need to change the template’s language
> *Requirements:*
> The new plugin runner:
> * MUST use the JAR as the unit of deployment
> * MUST not require the usage of a project template
> * MAY require the plugin to follow a certain class hierarchy ({_}i.e.{_},
> extends JavaPlugin)
> * MAY use a more specific format to enforce a structure
> * MUST allow multiple plugins to be deployed
> * MUST use isolated classloader for each plugin
> * MUST allow any JVM-compatible bytecode to run, whatever the language it
> was generated from
> * MAY allow hot reloading of Java plugins
> * MAY require a single JAR per plugin (to ease the classpath management of
> shared libraries)
> * MUST define a minimum JVM version
>
> *Difficulty:* Normal
> *Project size:* ~350 hours.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-451) Apache APISIX: Java Plugin Runner Improvement
[
https://issues.apache.org/jira/browse/COMDEV-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17517671#comment-17517671
]
Eric Liu commented on COMDEV-451:
-
[~tzssangglass] [~bumurzokov] Hi, I would like to work on this issue as part of
GSOC 2022. Is it still up for grabs? Should I start working on a draft proposal
to share with you guys?
> Apache APISIX: Java Plugin Runner Improvement
> -
>
> Key: COMDEV-451
> URL: https://issues.apache.org/jira/browse/COMDEV-451
> Project: Community Development
> Issue Type: New Feature
> Components: GSoC/Mentoring ideas
>Reporter: Bobur Umurzokov
>Priority: Major
> Labels: APISIX, full-time, gsoc2022
>
> *Background:*
>
> At the moment, the Java runner plugin requires you to use an existing
> template project and change it according to one’s needs.
> *Task:*
> Improve developer experience on the existing Java plugin runner so that we
> can attract and increase the number of users from the Java community.
> *Limitations:*
> * The architecture doesn’t manage multiple plugins. All need to be set in
> the same project
> * The standard Java unit of deployment is the JAR.
> * The plugin doesn’t allow for other widespread JVM-based languages
> ({_}e.g.{_}, Scala, Kotlin, Clojure, Groovy). Though it would be technically
> feasible, we would need to change the template’s language
> *Requirements:*
> The new plugin runner:
> * MUST use the JAR as the unit of deployment
> * MUST not require the usage of a project template
> * MAY require the plugin to follow a certain class hierarchy ({_}i.e.{_},
> extends JavaPlugin)
> * MAY use a more specific format to enforce a structure
> * MUST allow multiple plugins to be deployed
> * MUST use isolated classloader for each plugin
> * MUST allow any JVM-compatible bytecode to run, whatever the language it
> was generated from
> * MAY allow hot reloading of Java plugins
> * MAY require a single JAR per plugin (to ease the classpath management of
> shared libraries)
> * MUST define a minimum JVM version
>
> *Difficulty:* Normal
> *Project size:* ~350 hours.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Out of date GitHub mirror
The GitHub read-only mirror at https://github.com/apache/comdev-helpwanted is cracked (out of date), and cannot be fixed except by starting again [1] Do we really need it? I don't see the point of a read-only GH mirror, especially a broken one. I suggest Infra are asked to drop it before it confuses more people. Sebb [1] https://blogs.apache.org/infra/entry/subversion-to-git-service-git - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-466) json files contain references to git-wip-us.apache.org
Sebb created COMDEV-466: --- Summary: json files contain references to git-wip-us.apache.org Key: COMDEV-466 URL: https://issues.apache.org/jira/browse/COMDEV-466 Project: Community Development Issue Type: Bug Components: Projects Tool Reporter: Sebb The host git-wip-us.apache.org is no longer recognised, which means all URLs that reference it are broken. It currently appears in the following files: site/json/projects/commons-beanutils.json site/json/projects/reef.json site/json/projects/incubator-datafu.json site/json/projects/commons-math.json site/json/projects/phoenix.json site/json/projects/crunch.json site/json/projects/attic-stratos.json site/json/projects/tapestry.json site/json/projects/lucene-solr.json site/json/projects/helix.json site/json/projects/metamodel.json site/json/projects/jclouds.json site/json/projects/trafodion.json site/json/projects/attic-mrunit.json site/json/projects/oodt.json site/json/projects/attic-lucy.json site/json/projects/servicemix.json site/json/projects/logging-log4j_2.json site/json/projects/incubator-taverna.json site/json/projects/commons-scxml.json site/json/projects/parquet.json site/json/projects/attic-vxquery.json site/json/projects/lucene-core.json site/json/projects/ambari.json site/json/projects/deltaspike.json site/json/projects/attic-falcon.json site/json/projects/cassandra.json site/json/projects/cloudstack.json site/json/projects/clerezza.json site/json/projects/commons-lang.json site/json/projects/guacamole.json site/json/projects/bookkeeper.json site/json/projects/incubator-edgent.json site/json/projects/flex.json site/json/projects/storm.json site/json/projects/flume.json site/json/projects/brooklyn.json site/json/projects/bigtop.json site/json/projects/trafficserver-traffic_server.json site/json/projects/sqoop.json site/json/projects/vcl.json site/json/projects/attic-deltacloud.json site/json/projects/logging-log4net.json site/json/projects/any23.json site/json/projects/climate-open_workbench.json site/json/projects/zeppelin.json site/json/projects/attic-polygene.json site/json/projects/syncope.json site/json/projects/lens.json site/json/foundation/projects.json data/projects-override/crunch.rdf data/projects-override/ambari.rdf data/projects-override/falcon.rdf data/projects-override/climate.rdf data/projects-override/lens.rdf data/projects-override/sqoop.rdf data/projects-override/trafodion.rdf data/projects-override/vxquery.rdf -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer wrote: > > Created a starter with a few fun facts here: > https://cwiki.apache.org/confluence/x/0YyFD > > Feel free to add or take away as you see fit. THANK YOU! > - Josh - Sam Ruby > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby wrote: > > > Message has been posted. Next time it probably should be a pure plain > > text version. > > > > Anybody want to get started on May? Create the wiki page, put some > > content there, and then send it out the first week in May after others > > have been given the opportunity to contribute. > > > > - Sam Ruby > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen wrote: > > > > > > Problem: Members (and, more generally, committers) are less engaged with > > > the larger Foundation than at any point in our history. Meanwhile, the > > > mechanisms for getting more engaged (eg, the members mailing list) are a > > > firehose of unrelated content that is very frustrating to the casual > > > participant - even those who desire a deeper engagement - and, in > > > practice, are completely off-putting. Committers, meanwhile, have no > > > real avenue, outside of their project, for further engagement. > > > > > > I've been struggling with ways to address this for years, and they all > > > tend to founder on the rocks of "People should just be doing X!" which, > > > in each case, is true, but also dismissive and ultimately unhelpful. > > > > > > I would like to propose that we are more proactive about reaching out to > > > our community in tiny, consumable bites, that hint at a larger feast > > > that they're missing out on. > > > > > > Here's my proposal, but I cannot (and will not) tackle this alone, > > > because that guarantees failure, which guaranteed less participation the > > > next time we suggest something like this. > > > > > > Proposal/Brainstorming doc: https://hackmd.io/JaLaGy56T8qT3ODABLVswA > > > > > > It's an intentionally simple idea - a minimum viable idea, one might say. > > > > > > I want to know who's going to help make it a reality. Not particularly > > > interested in "that's a great idea", as much as "I will help make it > > > happen." > > > > > > This will involve engagement with Events, M, and Board, at a minimum, > > > but over time we'd hopefully engage everyone at the Foundation in > > > content creation. But, even then, I want to keep this tiny and > > > consumable - content that you can absorb in 2-5 minutes, always with a > > > "to get more engaged ..." call to action aspect to it. > > > > > > Come help me develop community. > > > > > > --Rich > > > > > > - > > > 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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Created a starter with a few fun facts here: https://cwiki.apache.org/confluence/x/0YyFD Feel free to add or take away as you see fit. - Josh On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby wrote: > Message has been posted. Next time it probably should be a pure plain > text version. > > Anybody want to get started on May? Create the wiki page, put some > content there, and then send it out the first week in May after others > have been given the opportunity to contribute. > > - Sam Ruby > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen wrote: > > > > Problem: Members (and, more generally, committers) are less engaged with > > the larger Foundation than at any point in our history. Meanwhile, the > > mechanisms for getting more engaged (eg, the members mailing list) are a > > firehose of unrelated content that is very frustrating to the casual > > participant - even those who desire a deeper engagement - and, in > > practice, are completely off-putting. Committers, meanwhile, have no > > real avenue, outside of their project, for further engagement. > > > > I've been struggling with ways to address this for years, and they all > > tend to founder on the rocks of "People should just be doing X!" which, > > in each case, is true, but also dismissive and ultimately unhelpful. > > > > I would like to propose that we are more proactive about reaching out to > > our community in tiny, consumable bites, that hint at a larger feast > > that they're missing out on. > > > > Here's my proposal, but I cannot (and will not) tackle this alone, > > because that guarantees failure, which guaranteed less participation the > > next time we suggest something like this. > > > > Proposal/Brainstorming doc: https://hackmd.io/JaLaGy56T8qT3ODABLVswA > > > > It's an intentionally simple idea - a minimum viable idea, one might say. > > > > I want to know who's going to help make it a reality. Not particularly > > interested in "that's a great idea", as much as "I will help make it > > happen." > > > > This will involve engagement with Events, M, and Board, at a minimum, > > but over time we'd hopefully engage everyone at the Foundation in > > content creation. But, even then, I want to keep this tiny and > > consumable - content that you can absorb in 2-5 minutes, always with a > > "to get more engaged ..." call to action aspect to it. > > > > Come help me develop community. > > > > --Rich > > > > - > > 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: Idea: Monthly Members Moment/Critical Committer Communications
Message has been posted. Next time it probably should be a pure plain text version. Anybody want to get started on May? Create the wiki page, put some content there, and then send it out the first week in May after others have been given the opportunity to contribute. - Sam Ruby On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen wrote: > > Problem: Members (and, more generally, committers) are less engaged with > the larger Foundation than at any point in our history. Meanwhile, the > mechanisms for getting more engaged (eg, the members mailing list) are a > firehose of unrelated content that is very frustrating to the casual > participant - even those who desire a deeper engagement - and, in > practice, are completely off-putting. Committers, meanwhile, have no > real avenue, outside of their project, for further engagement. > > I've been struggling with ways to address this for years, and they all > tend to founder on the rocks of "People should just be doing X!" which, > in each case, is true, but also dismissive and ultimately unhelpful. > > I would like to propose that we are more proactive about reaching out to > our community in tiny, consumable bites, that hint at a larger feast > that they're missing out on. > > Here's my proposal, but I cannot (and will not) tackle this alone, > because that guarantees failure, which guaranteed less participation the > next time we suggest something like this. > > Proposal/Brainstorming doc: https://hackmd.io/JaLaGy56T8qT3ODABLVswA > > It's an intentionally simple idea - a minimum viable idea, one might say. > > I want to know who's going to help make it a reality. Not particularly > interested in "that's a great idea", as much as "I will help make it > happen." > > This will involve engagement with Events, M, and Board, at a minimum, > but over time we'd hopefully engage everyone at the Foundation in > content creation. But, even then, I want to keep this tiny and > consumable - content that you can absorb in 2-5 minutes, always with a > "to get more engaged ..." call to action aspect to it. > > Come help me develop community. > > --Rich > > - > 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: Idea: Monthly Members Moment/Critical Committer Communications
Hi, Le mar. 5 avr. 2022 à 15:21, Rich Bowen a écrit : > ...AFAIK, while there are a few things in the current draft > that are not open to the public (ie, board meeting for example) there's > no harm in informing the public - they just cannot participate... I agree in principle, but we should clarify whether we are ok with publishing private URLs. Those are protected and there's already a good number of them out there, but I think it's good to define, as a general principle, whether we are ok with publishing URLs that only ASF members have access to. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
On Tue, 2022-04-05 at 08:44 +0200, Bertrand Delacretaz wrote: > Le lun. 4 avr. 2022 à 19:16, Priya Sharma > a écrit : > > > > I am also not able to view those pages (perhaps only ASF members > > have > > access)... > > That's correct, the ASFP wiki space is restricted to ASF members. > > It's not fantastic that we're discussing here and not letting people > see that draft - OTOH that's more motivation to create a public > version of those news, which would be a good thing. We might just > send > the public version here. My initial proposal was to have a members version (with member- confidential info) and a more general committers version for public consumption. AFAIK, while there are a few things in the current draft that are not open to the public (ie, board meeting for example) there's no harm in informing the public - they just cannot participate. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Le lun. 4 avr. 2022 à 19:16, Priya Sharma a écrit : > > I am also not able to view those pages (perhaps only ASF members have > access)... That's correct, the ASFP wiki space is restricted to ASF members. It's not fantastic that we're discussing here and not letting people see that draft - OTOH that's more motivation to create a public version of those news, which would be a good thing. We might just send the public version here. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Is https://reporter.apache.org down?
On 05/04/2022 04.55, shang xinli wrote: It shows 'loading base data..' and never comes to the page. Whimsy took a tumble yesterday, which brought down reporter as well. They should both be back up now. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
