I just want it clarified what will be the rules of adopting a new plugin or
extension. Likewise the rule for archiving/killing off dead ones.
And that is applied generically.
E.g.
At least one pmc member needs to sponsor (doesnt have to be the committer or
contributor)
Any
> All questions need to be same
@Michael Pearce perhaps it's my english as second language here, but
this to me sounded like "All your basis are belong to us" :)
Can you explain what you meant here?
I would start with a single repo for all the plugins we can add.
The way we are set now, a single git repo is a good way to start.
We can always revist and move a component out to its own repo later.
As for the day to day dev, discussions and adding components, this is
no different than what we
On Mon, 3 Jun 2019 at 14:24, Clebert Suconic wrote:
>
> The question was in regard to spin new components? do we need a new vote to
> start a new repository?
>
I dont believe we actually do need a vote, a lot of stuff doesn't,
just establishing consensus on what is being done. Votes are one way
What about the kafka plugin, or influx plugin...
All questions need to be same
Get Outlook for Android
On Mon, Jun 3, 2019 at 2:27 PM +0100, "Clebert Suconic"
wrote:
there's also another technical issue when we create / separate these components.
They will likely depend
there's also another technical issue when we create / separate these components.
They will likely depend on the broker...
And how are we going to consume these components on the broker? Have
the users picking them and installing them manually?
idea:
We could have the CLI doing such thing for
The question was in regard to spin new components? do we need a new vote to
start a new repository?
Regarding the releases... we could release them altogether. Say...
ActiveMQ-Artemis-plugin 1.0
Later on, when you add a new feature, you will have 1.1, 1.2... and
thereafter.
Say we changed
Its more that the download links for the previous release themselves
are broken thats the issue. The docs link is often incorrect too, but
it tends to at least somewhat 'work' when wrong (from pointing to
"latest" rather than the actual versions release docs).
I think the existing process needed
A vote would be required for each independently released thing, yes.
That is true whether they are in specific repos or in an single repo
but still released independently, so the only difference would come if
releasing all plugins in that single repo as 'one thing'. That
probably mean less
