GSoC 2017: UPS and Apache Kafka
by Matthias Wessendorf
Hi,
for this years project, we are now beyond community bonding, and coding on
the project, and required research do start.
In last meeting w/ our students we discussed a bit the basics for the next
week or so.
The initial POC/spike should be this JIRA:
https://issues.jboss.org/browse/AGPUSH-2098
Note, all work should be done on the "GSOC_2017_kafka" branch:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/GSOC_2017_kafka
For starters, I've sent a first basic PR against the branch:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/835
Besides the initial epic, we are going to create more and more JIRAs, in
AGPUSH, with the "gsoc_2017" label. Here is a public filter for those
tagged JIRA tickets:
https://issues.jboss.org/issues/?filter=12332273
We should also create a JIRA board for sprint planing and our backlog, on
the GSoC project.
Cheers!
Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
9 years
Jenkins Java client - fork?
by Ali Ok
Hi,
In order to make our Digger Java client working as we like, we needed to
make changes in the underlying Jenkins Java client [1].
We sent a PR, but we don't know when the project owner will merge it. So,
for testing purposes of our own, we would like to release our fork of
Jenkins Java client in a snapshot repository.
What do you say? Any other and better approach?
Where can we publish the snapshots of our fork?
Note: The project owner is a kind guy and will perhaps publish a snapshot
release for us after merging our PR, but we cannot rely on that workflow
for long time for other needed changes.
--
ALI OK
SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
Red Hat
<https://www.redhat.com/>
<https://red.ht/sig>
9 years
