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
|