+ OpenMQ-Dev list
Werner
I would use https://bugs.eclipse.org/bugs/
Product: community, Comp: GitHub but that may not be correct.
Looks like this can be done fairly easily, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=536052
If we want to do this generally, we could see about a bulk request,
but I suspect, teams may want to decide for themselves.
I don't think you need to have any special role in the project. If
you need a +1, we can check with Nigel.
-- Ed
On 8/28/2018 1:27 PM, Werner Keil
wrote:
Ed,
Setting up you mean the Waffle board? Well, it is a tool
just like Travis-CI that any project could use if they think
it helps IMO.
Some projects do, and others may not need it or prefer
built-in GitHub boards (which do not seem to require webhooks)
Not having web hooks makes some things a little less
intuitive, so hope someone with admin permission could add
that.
In my experience the two (Waffle and built-in project
feature) can be used perfectly fine side-by side, what Waffle
so far does not do is spread across multiple repositories,
maybe for that you need some professional license, but for
Waffle as such none is required, it does not cost anything at
the moment and does not shut itself down after some months
either (like e.g. Jenkins does if you don't license the
Enterprise version ;-)
Where would I file an issue to ask someone with admin
rights to OpenMQ (Wayne, Ivar or someone else) to activate the
web hook?
Werner,
Generally, the Eclipse Foundation administrators set this
kind of thing up. I don't know what the requirements for
making things like this happen. My impression is that they
want to know about the product. Maybe it's license and
things like that. I've asked Wayne. Feel free to go ahead
and file an issue. Perhaps it's easy and quick.
-- Ed
On
8/28/2018 12:51 PM, Werner Keil wrote:
Waffle would require someone with admin
rights to the subsequent repo.
Waffle needs an admin of eclipse-ee4j/openmq
to configure webhooks, to enable real time updates
from GitHub.
So that is the sort of admin required in Waffle's
case, whether Eclipse webmasters have it or others in
the PMC, I dont know, but each of them could help
creating the webhooks (everyone who has access to
OpenMQ in GitHub should also see everything in the
Waffle project)
I picked the advanced layout with "Inbox",
"Backlog", "In Progress", "Review" and "Done", which
seems most appropriate, e.g. for tasks that need
review by the PMC or somebody else ;-)
I don't see the PMC would ever care
about how the EE4J projects are managed
internally. If the GitHub extensions require some
sort of assistance/configuration by the Eclipse
Foundation Webmaster, they may have something to
say about it.
Ivar
--
Java Champion, JCP EC/EG Member,
EE4J PMC, JUG Leader
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
|
